The core idea behind the project is "Code over configuration".
It’s explicit and predictable.
Site’s structure is easy to manage when it is obvious from a single glance.
The best way to get a feel for using Lightweight is to take a look at an example.
Long time Pythoneer Tim Peters succinctly channels the BDFL's guiding principles for Python's design into 20 aphorisms, only 19 of which have been written down.
Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!
I love these rules. Despite the fact they come from the Java world, they read like poetry to me.
All programmers are API designers.
Good programs are modular,
and intermodular boundaries define APIs.
Good modules get reused.
Hurray! Lightweights first blog post! 🐣
Make sure to read Using Lightweigh.