2 ms·
It has two major flaws: * When you move code around, you have to pay a lot of attention to the "ant turd tokens": ; , and . or the lack of one in the right pla
by davidw 14y ago
It has two major flaws:
* When you move code around, you have to pay a lot of attention to the "ant turd tokens": ; , and . or the lack of one in the right places. That is very annoying.
* It's very repetitive at times. Redundancy is great for servers, not so much for code you have to modify. Take this as an example:
https://github.com/erlang/otp/blob/master/lib/stdlib/src/filename.erl https://github.com/erlang/otp/blob/master/lib/stdlib/src/fil...
It's got a lot of things repeated, and you have to play "spot the difference" to read the code and figure out what's going on. That's a fun game for my four year old, not so much when you're working. I like pattern matching, and it seems that with some tweaks, you could extract common bits of code and end up with something more succinct, so that you only write code that regards the actual differences between two code paths, rather than also having to write the same boilerplate over and over. I have been spoiled by Ruby's "don't repeat yourself" mentality.