News for hackers. Stuff that matters.
Re:Some were meant for C [pdf] by tourmalinetaco on Thursday June 22, 2023 @01:33AM (#36428337)
Because working slowly and rewriting code typically leads to better code. By taking it slowly you grow more familiar with what you want, it gives you more time to think, and its generally more enjoyable.

This culture of “fast coding” is a major reason software ends up so flawed. People are so enamored with quantity they completely forget quality along the way. And that means everyone suffers.

Re:Some were meant for C [pdf] by antonvs on Thursday June 22, 2023 @02:37AM (#36428695)
You didn’t actually address the point I raised about why C is hard to justify for that reason.

Besides, a strong type system also forces you to think about the design of your code, and demonstrably leads to more reliable results, on an industry-wide basis.

Re:Some were meant for C [pdf] by JohnFen on Thursday June 22, 2023 @10:43AM (#36432905)
> a strong type system also forces you to think about the design of your code

True. And so does using a language like C.

Re:Some were meant for C [pdf] by antonvs on Thursday June 22, 2023 @11:46AM (#36433972)
Except the forcing function in C occurs because if you make a mistake, you can have serious problems at runtime. With a strong type system, if you make a mistake, your program won't compile. It's a big difference, and it's hard to justify the C approach for reliable systems development in a modern context. No-one in this thread even seems to be trying.

If you want to use it for hobby projects because you enjoy it, knock yourself out. But advocating its use for anything important hasn't been viable for decades except for legacy reasons.

Re:Some were meant for C [pdf] by JohnFen on Thursday June 22, 2023 @12:39PM (#36434846)
> It's a big difference

It is! And there is absolutely a role for strongly typed languages.

> But advocating its use for anything important hasn't been viable for decades except for legacy reasons.

We entirely disagree here.

The big benefit of more stringent languages is that they require less effort on the part of the programmer to ensure safety and correctness. This is of great value -- perhaps even indispensable -- in certain contexts. For instance, if the programming team is large, or if the company wants to hire less experienced developers, or if the company wants to keep up a very high velocity.

But those are economic arguments. It's different than asserting that a given language is simple too dangerous to use under any circumstance. I think that assertion is entirely unsupportable.

Re:Some were meant for C [pdf] by jjgreen on Thursday June 22, 2023 @04:22AM (#36429381)
This is so true, I've pointedly never learnt to touch type since I don't want to be able to write faster than I can think.