2 ms·

> The presumption that every type of project should fundamentally begin with adherence to patterns guaranteeing high resource usage of correctness is a bad type

by hu3 7y ago

> The presumption that every type of project should fundamentally begin with adherence to patterns guaranteeing high resource usage of correctness is a bad type of premature optimization / premature abstraction. Yes. Devs are often found on the four corners of the internet screaming things that could be extrapolated to: "Undefined Behavior is unacceptable regardless of the project!" "Garbage Collection is the devil!" "How dare you code in a language with nulls?" "Can you even sleep knowing your code might have race conditions?" Sure, I'd love to code in a stable language without nulls, no GC, no UB and no race conditions while still being easy to learn and quick to onboard to the average dev as C#/Java/Go/Python and having a large community with tons of libraries available. No such languages exist yet so tradeoffs have to be made.

perl4ever 7y ago
"Undefined Behavior is unacceptable regardless of the project!" This is an ambiguous statement as to whether it is about avoiding officially defined "undefined behavior" or about not programming in a language that has it. I agree that the former is impractical, but I think the latter is good advice. If a language defines something as undefined, and if we agree that permits nasal demons, then undefined behavior is unthinkable, intolerable, yet inevitable. It's a spiral into insanity, because this philosophy is self-contradictory and those who claim to believe in it do not believe in it at the same time. But if a language simply doesn't define everything, then nasal demons are off the table and we can all assume that we are reasonable people who are part of an advanced civilization that deals with exceptions and the unexpected on an adhoc basis.
- notzuck 7y ago
  Don't listen to this guy - he wants you to move your kids to another city because you have to be the only [insert minority here] on a team.

by hu3 7y ago

perl4ever 7y ago

"Undefined Behavior is unacceptable regardless of the project!" This is an ambiguous statement as to whether it is about avoiding officially defined "undefined behavior" or about not programming in a language that has it. I agree that the former is impractical, but I think the latter is good advice. If a language defines something as undefined, and if we agree that permits nasal demons, then undefined behavior is unthinkable, intolerable, yet inevitable. It's a spiral into insanity, because this philosophy is self-contradictory and those who claim to believe in it do not believe in it at the same time. But if a language simply doesn't define everything, then nasal demons are off the table and we can all assume that we are reasonable people who are part of an advanced civilization that deals with exceptions and the unexpected on an adhoc basis.

notzuck 7y ago
Don't listen to this guy - he wants you to move your kids to another city because you have to be the only [insert minority here] on a team.