2 ms·
"But I disagree that it's the responsibility of the language to keep potentially dangerous tools out of the hands of developers." That is pretty much entirely
by jimbokun 8y ago
"But I disagree that it's the responsibility of the language to keep potentially dangerous tools out of the hands of developers."
That is pretty much entirely the point of higher level programming languages.
Like preventing you from allocating and freeing memory on your own, because you might screw it up.
Or removing pointer arithmetic.
Or reducing the scope of mutability.
Or preventing access to "private" object variables.
Many programming language features are basically guards to make it less likely you cut your hand off.
- yebyen 8y agoThose are all scary indeed. Ways you can cut your hand off. Has a nice ring to it, sounds like something to worry about more than "ways you can write unreadable garbage code that not even the author can still parse for themselves in their head." Nobody is arguing that there aren't ways to misuse this new feature. There obviously are! But I can tell you we have plenty of time to call the ways out and warn everyone not to do those things, before ruby-2.7 will be affecting any legacy codebases. If you feel strongly about this, the time to argue about it is definitely now, not after the first 2.7 release is already cut. It makes the list of un-googlable idiomatic syntaxes that you must learn and keep in a list, in order to guarantee you won't ever find a bit of Ruby code that you can't understand, marginally longer. There are several such features planned in the ruby-2.7-head now. Is this really the worst of them?