2 ms·
You say "overly sweetened" as a pejorative but I'm curious what is wrong with a language being "too sweet"? Is it because it becomes too complex, too hard to le
by zmmmmm 8y ago
You say "overly sweetened" as a pejorative but I'm curious what is wrong with a language being "too sweet"? Is it because it becomes too complex, too hard to learn? This is definitely what I feel with Groovy, which looks simple on the surface but is actually quite hard to teach to people because there is so much implicit behavior. But then, we're not in kindergarten here, every tool I use is a long term investment so I don't mind that too much if there is payback in the long run.
- BoorishBears 8y agoTwo sweet means it tries to do too much to feel “nice” to write. If you’re removing the cognitive lid from the person writing and dumping it on the person reading you’re not only not reducing the overall cognitive load required for your code, you’re increasing it exponentially. Code generally is written once and read multiple times. Shoving bundles of syntactical sugar so that there are 5 ways to do any given thing just so that you can always choose the (Grooviest/Kotliniest) way in a given context must feel great to write with but now every reader must be aware of those 5 ways to do things. We’re not in school period, investing time inanguages that are almost masturbatory over how “sweet” their syntax is isn’t generating revenue. I can’t name one company that succeeded because they used Groovy, but every single one would immediately cut out access to a large pool of talented individuals who are wizards of the JVM, also that what? They can have 5? forms of string literals?