4 ms·
effective vs. good I see 'effective vs. good' as an opportunity to satisfice. http://en.wikipedia.org/wiki/The_Paradox_of_Choice http://en.wikipedia.org/wiki/
by stcredzero 17y ago
effective vs. good
I see 'effective vs. good' as an opportunity to satisfice.
http://en.wikipedia.org/wiki/The_Paradox_of_Choice http://en.wikipedia.org/wiki/The_Paradox_of_Choice
Let's take the notion of satisficing and apply old 80-20 rule. About 80% of your life is not going to matter that much in 5 years. Your choice of toothpaste, the car you drive, which couch you buy -- these can be complex decisions, but they aren't going to have as big an influence on your life as the town you live in, the jobs you take, or your closest friends. It's a minority of decisions you make which will matter the most, so spend your maximum effort optimizing those. For the rest, let's just find something that will do the job.
I think the Go team decided that compilation time, efficient execution, conciseness, and concurrency were the areas that mattered the most for a systems programming language. Most of the programming world understands "Algol-derived" syntax, so why not stick with that? In fact, given that the majority understands that sort of syntax, this should also be considered an optimization -- one which is aimed at achieving as large a user base as possible.
(I wonder if one can consider Python to be an 80-20 satisficed language?)
- pvg 17y agoIf you haven't got around to it yet, google 'worse is better'.
- stcredzero 17y agoI've also responded to 'worse is better" numerous times on HN. I don't think people are aware that what they want is satisficing in most of their design so that they can spend more effort on the the most important 20%.