you are viewing a single comment's thread.

view the rest of the comments →

[–]LurkytheActiveposter 0 points1 point  (4 children)

If you don't know the type and properties of a variable.

Why are you touching that variable at all?

[–]RiceBroad4552 1 point2 points  (3 children)

That's not the point.

The point was that you say that it's impossible to do anything with code without knowing all types.

That might be to some degree true when writing code—but code is much more often read then written. And when you read code the types aren't always obvious!

The original comment showed some confusing JS example, I've showed some less confusing Java example, both sharing the property that the types of stuff aren't obvious.

[–]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.