4 ms·
As someone that used Coffeescript a bunch, the problem is it's designed to make it very easy to write code, but has very little thought given to being able to u
by lexicality 1y ago
As someone that used Coffeescript a bunch, the problem is it's designed to make it very easy to write code, but has very little thought given to being able to understand that code again in 6 months time.
This means it's very easy to knock out an entire project in record time, but subsequently very difficult to debug/maintain/update the same project when you come back to it. It's essentially a technical debt generator.
- johnisgood 1y agoThis is why I have DEVELOPER.md. It explains why I chose X over Y, among many other things. Someone wrote a nice list: https://news.ycombinator.com/item?id=44581069 https://news.ycombinator.com/item?id=44581069.
- lexicality 1y agoThat's a nice idea, but the problem more comes from using a language designed to help you get ideas from your head into production using the fewest possible characters results in extremely terse code. You can say all sorts of things around "write better documentation" and so on, but step 1 really is "don't use a code golfing language"
- johnisgood 1y agoI do not disagree. In DEVELOPER.md you are not supposed to have an intro to the language you picked.