-
Website
http://phildawes.net/blog/ -
Original page
http://www.phildawes.net/blog/2007/01/11/low-simplicity-and-high-simplicity/ -
Subscribe
All Comments -
Community
-
Top Commenters
-
danja
4 comments · 4 points
-
phildawes
5 comments · 1 points
-
Dominic Sayers
1 comment · 1 points
-
David W.
2 comments · 1 points
-
ryantm
1 comment · 1 points
-
-
Popular Threads
-
Phil Dawes Stuff >> Idea for a global interpreter lock optimized for low contention
2 weeks ago · 3 comments
-
Phil Dawes Stuff >> Idea for a global interpreter lock optimized for low contention
For example, is it simple in terms of writting the original code, or in terms of someone else trying to understand and maintain it? The two are not necessarily the same.
It also makes a difference in terms of whether the code is standalone (e.g. the miles/kilometer example in the original article) of if it is working with another construct/language. For example, code (e.g. in PHP) used to interact with a database (e.g. MySQL). If the underlying concepts and constructs of the code language reflect that of the database, it is much easier to understand than if they are different.
My point is that the discussion of low/high simplicity is more meaningful within a context.