4 ms·
Yeah, I get your point. Poor programmers need to be kept on a leash, so off you go with dumbed-down languages.
by pif 4y ago
Yeah, I get your point. Poor programmers need to be kept on a leash, so off you go with dumbed-down languages.
- quic5 4y agoHonestly most bad abstraction come from authors thinking they're geniuses (in that moment)
- pif 4y agoSure, as well as the right abstractions come from professionals who are not treated like stupid kids.
- kristoff_it 4y agoYep, just like a professional barber's razor is dumbed down because it only has one blade instead of 6, a swiveling head and a battery-powered vibration function. :^)
- pif 4y agoWrong! A barber's razor is the perfect tool for the trade, together with a sharpening stone. The Go equivalent would be a blade with two dull sides.
- intelVISA 4y agoThe Go equivalent also mocks you in an effete tone and claims "everybody shaves with a dull blade these days so why don't you?"
- HopenHeyHi 4y agoMy beard keeps my face warm in winter?
- timeon 4y agoMETA: analogies are double-edged swords.
- rrampage 4y agoNow that Go has generics (finally), this analogy seems a tad too harsh.
- alpaca128 4y agoA professional barber's razor is flexible through its simplicity. Zig's errors are not flexible due to their separate syntax rules, which seems like the opposite of one sharp blade that handles anything.
- rootlocus 4y agoIf you want total control over your hardware, you're free to use machine code. Is a type system a leash? I mean surely you want to interpret memory however you want without the language getting in the way of forcing you to use methods. Are unique/shared pointers a leash? Or the borrow checker? They restrict what you can do with your objects because you're a poor programmer who can't code correctly. No true developer needs memory safety. Are calling conventions a leash? Surely you know better how to manage the stack and registers and everyone else should listen to you and do it the way you prefer.
- pif 4y agoIt's not me calling Go users idiots: it's one of the Go designers! “The key point here is our programmers are Googlers, they’re not researchers. They’re typically, fairly young, fresh out of school, probably learned Java, maybe learned C or C++, probably learned Python. They’re not capable of understanding a brilliant language, but we want to use them to build good software. So, the language that we give them has to be easy for them to understand and easy to adopt.” -- Rob Pike