4 ms·
>Languages which impose weird restrictions tend to do so because it allows them to offer (nearly) ironclad guarantees about something else. Yes, but oftentimes
by coldtea 5y ago
>Languages which impose weird restrictions tend to do so because it allows them to offer (nearly) ironclad guarantees about something else.
Yes, but oftentimes this is more like:
"If we tie you to this bed, you will never have a car accident! You'll also never get lost! This also makes it easier to stay healthy as we'll be feeding you the best food!"
Sure, but I'll also miss all kind of activities I could be doing outside on my own. I'll also get bed sores. And I often want a steak or ice cream, even if it's not ideal, but you insist bringing me this organic gourmet vegan crap.
- tux3 5y agoI think that point of view assumes bad faith. No one sets out to create programming languages that tie people to their beds. If people add restrictions, it's not to make users miserable. It's fine if you like being unrestricted, I like that too. However, when you see people going out of their ways to add barriers to their own work, you should assume they reap a benefit that you're not fully appreciating, not that they hate fun and want to outlaw ice cream.
- myfavoritedog 5y ago"Bad faith" is too strong a term, but if you've spent much time in the Elm language sphere, you really will get what the original poster is getting at. https://elm-lang.org/ https://elm-lang.org/
- coldtea 5y ago>No one sets out to create programming languages that tie people to their beds. People can still end up designing such languages, even if they didn't set out with that specific goal. (Kind of like how you can bring war and division, even if your goal is to bring some religious peace on Earth or "the revolution"). >If people add restrictions, it's not to make users miserable. That's already explicit in my comment though. They didn't tie the person to his bed to make him miserable but to spare them from car accidents, to help them never get lost, and other such niceties! The misery is a by-product, not a design goal.
- throwaway17_17 5y agoI don’t think it takes bad faith to come to GP’s conclusion. Further, it implies a great deal of superiority for you to assume that someone who does not like/enjoy the restrictions of a language does not ‘fully [appreciate]’ the supposed benefits of those restrictions. I, for one, do not enjoy or value the restrictions (or underlying semantic concept) of ownership in Rust. It just means that I don’t enjoy it, I understand the benefits which are claimed to exist for adopting the Rust-centric view of programming. I just don’t think they are worthwhile for me. I’m not really disagreeing with the point you make about language designers intention, I doubt they set out to inflict misery on users, but your assumption about not understanding some alleged benefit is a bridge too far.
- hackerfromthefu 5y agoThe point is not whether they are worthwhile to you, but to the problem space the program solves. Further that includes the context of the organisation/developer that will own it going forward.
- AnimalMuppet 5y agoThere's a reason they were called "bondage and discipline languages". They created barriers for what they assumed to be your own good. But as Edward Abbey said, "When I see someone coming to do me good, I reach for my revolver." That is, when someone wants to make decisions for my good, they're deciding for me; that is, they're taking the decision away from me, because they don't think I can be trusted to choose the "right" thing. And then I'm supposed to feel grateful for the help instead of resentful for being treated like an idiot or a child! They mean well. Fine. I still don't have to like it, and I don't have to accept it.
- kaba0 5y agoAnd frankly, in case of a complex program, you can’t be trusted to choose the right thing, as the human brain simply doesn’t scale with program complexity. We need help from the computer to avoid bugs for anything non-trivial. For example, as have been shown for example countless times, C programmers are unable to properly free allocated memory so solutions were made (GC, or rust’s ownerships). It is egoistical to think
- AnimalMuppet 5y agoBut they can't be trusted to choose the right thing either. Wirth, sitting in his office at a university in Switzerland, has no idea whatsoever what problems I'm facing trying to use un-extended Pascal in an embedded system with memory-mapped I/O. (No, it wasn't my choice to use Pascal without extensions in that environment.) The point is, you don't have enough information to choose for me. You can't do it. Even if you can absolutely, 100% correctly decide what the "right thing" is in any given situation, you don't know all the situations. (And if you'd say "the right thing is to not use Pascal in that situation", I'd agree with you. But as a language designer, your language will get used in places where even you may think it's not a great fit.)
- swsieber 5y agoI'd probably liken it traffic controls, like lanes w/lines, stop-lights, stop-signs and other formalized rules of driving. Yeah, it might suck that you can get a ticket for treating a red-light like a stop-sign at 6am in the middle of no-where. Though this is me speaking from a "likes rust" perspective.
- rtpg 5y agoCould you please describe a case where this is actually happening in the languages people tend to imply this is happening in? Rust has unsafe, Haskell has unsafePerformIO. You might not like how verbose some of the stuff is but all these languages give you a foot gun if you really want it.
- pjmlp 5y agoThat is the usual cowboy programming sentiment that fueled the same critic against Modula-2 and Pascal. A well known article, written in bad faith, is "Why Pascal is Not My Favorite Programming Language". http://www.cs.virginia.edu/~evans/cs655/readings/bwk-on-pascal.html http://www.cs.virginia.edu/~evans/cs655/readings/bwk-on-pasc... Why bad faith? Most of the critic he makes against Pascal was sorted out by Pascal dialects. Which one can consider doesn't count as dialects aren't the main language, yet by 1981, C was mostly available in K&R dialects outside UNIX, like Small C. And besides those Pascal dialects, Modula-2 standard was released in 1978, while Mesa was powering XDE and Bravo at Xerox.
- thewakalix 5y ago> Why bad faith? Most of the critic he makes against Pascal was sorted out by Pascal dialects. That reminds me of Yes, We Have Noticed The Skulls [0]. [0] https://slatestarcodex.com/2017/04/07/yes-we-have-noticed-the-skulls/ https://slatestarcodex.com/2017/04/07/yes-we-have-noticed-th...
- pjmlp 5y agoGreat read, thanks for sharing.
- tialaramex 5y agoHowever, the author assumes that it follows if you've Noticed The Skulls you would choose to do it differently next time. That's not necessarily so. Arthur Laffer is an economist. Laffer has helped provide advice to numerous Republicans and Republican projects which of course didn't achieve their stated goals (e.g. Trump's massive tax cuts for the wealthy which Laffer claimed would grow the US economy by 6%). I'm confident Laffer has Noticed The Skulls, but why should he care? Advice that destroys the US economy but further enriches those who already have more than enough worked out great for Laffer.
- pjc50 5y agoThis is a purely emotive metaphor with no technical content?
- coldtea 5y agoYes, and as such perfectly isomorphic to the resistance the programmer feels when working e.g. to satisfy the borrow checker or strict type systems. This is not about some "technical" impossibility - language still have an escape hatch like unsafe and "non-idiomatic" ways of coding. But to focus on the technical and ignore programmer experience ("feelz") in that area, is like equating Idris and Forth because "they're all turing complete and it all ends up as binary code anyway".
- pjmlp 5y agoIt is more like, if you were an helmet, a seatbelt, metal gloves, you will survive to tell the story.
- coldtea 5y agoNot really, as a helmet, seatbelt, and gloves are passive objects you just wear and continue as previously, engaging their protection only in case of accident. Whereas working with the borrow checker, or a Haskell-like type system, changes the experience and the method of programming itself, forces certain patterns, and so on.
- bmn__ 5y agoProgramming is for all kinds of people. If you felt despair when you read the metaphor of totalitarianism and just want to get away from languages that want to grind an axe on you, and Lisp is not your cup of tea, then Raku and Perl welcome you.