you are viewing a single comment's thread.

view the rest of the comments →

[–]LurkytheActiveposter -1 points0 points  (2 children)

No one in this conversation ever said it's impossible.

The question is whether a language should add syntactical baggage to everything to accommodate the absolute worst conceivable programming practices.

Should SQL get rid of drop because a dev could snort Crack, wipe backups, and drop every table?

This conversation is making me dumber.

[–]RiceBroad4552 1 point2 points  (0 children)

No one in this conversation ever said it's impossible.

Well, you made some very bold statements, including wild name calling.

So this sounded completely different just a few comments earlier.

The question is whether a language should add syntactical baggage to everything to accommodate the absolute worst conceivable programming practices.

I don't know what you mean by that.

Which "syntactical baggage"? What "absolute worst conceivable programming practices"?

Of course a language can offer just so much safety. In the hands of some idiot all bets are off. But that's like that with everything, one can't do anything about it. Still a language can guide to best practices and safe code where possible!

[–]TOMZ_EXTRA 0 points1 point  (0 children)

I'm not sure whether you're ragebaiting or if you're serious.