3 ms·
Holy smoke, that's a long article. I'm not even sure what the point is. I mean, the author starts off by saying that once you've seen "good design" you're ruine
by bediger4000 5y ago
Holy smoke, that's a long article. I'm not even sure what the point is. I mean, the author starts off by saying that once you've seen "good design" you're ruined for life every time you see bad design, and I guess the author does actually end up back at that point, sort of, by writing that You Should Learn Rust, It Will Make You A Better Person.
I guess the good design was the friends we made along the way.
- wqweto 5y agoThere is no short article from fasterthanlime. These have to be worth their money I guess but anyway I always like everything by him.
- ithkuil 5y ago"I didn't have time to write a short text so I wrote a long one instead", or something like that
- i_hate_pigeons 5y agoit's mostly lots of code fragments and incrementally building on whatever he's trying to convey, is not like he put a brain dump or a wall of text as per when that phrase is used. So your comment doesn't ring true in this case imo
- pixelrevision 5y agoLol well the length of the article gives a good idea of what you are in for picking something like rust (or any other language really) over go. Every single thing in go from the tooling to the standard library is so relentlessly simple and to the point. It also changes very methodically and doesn’t break things. I really wish more languages would adopt this level of “good design”.
- chousuke 5y agoThe article makes a pretty clear point that the go interfaces it talks about aren't as simple as they seem. The limitations of the language result in interfaces that are pretty easy to misuse due to unenforceable invariants, and not in theoretical ways either, which I think is the opposite of simple.