3 ms·
Most of the new language features have been in the form of simple, predictable mechanical transforms that can be replaced with hand-written code in cases where
by kevingadd 14y ago
Most of the new language features have been in the form of simple, predictable mechanical transforms that can be replaced with hand-written code in cases where you don't like them: enumerator functions, linq, and now async.
What don't you like about that? It's the perfect compromise: People who want syntactic sugar get it, but people who don't want the sugar are still free to utilize features that are designed for the sugar and interoperate with code that uses the features.
- eckyptang 14y agoI don't like how the semantic boundary of the framework is creeping into the language. The language is complex as it stands and it's rather hard to get people who understand the entire language and framework and know when to use features and when not to. The primary case is when people use the features they shouldn't do, which happens a lot on large codebases like ours regardless of the skill set of the people you employ. If the language was extensible (as per LISP derivatives), I'd have less of a problem but it's a monolithic compiler. Too much sugar is bad for your programmers.