News for hackers. Stuff that matters.
Re:Python Is Easy. Go Is Simple. Simple != Easy by throwawa14223 on Monday November 27, 2023 @02:07PM (#38436712)
Conversely I could go longer between compiles if the type system caught more.
Re:Python Is Easy. Go Is Simple. Simple != Easy by arp242 on Monday November 27, 2023 @02:49PM (#38437241)
Most of the times when I really care about quick feedback cycles is when I'm experimenting to see what approach does and doesn't work well in the first place.

I care a lot less about it for "simple" errors like typing errors, typos, or whatnot. This is mostly trivial stuff compared to "is this entire approach good or not?"

Re:Python Is Easy. Go Is Simple. Simple != Easy by throwawa14223 on Tuesday November 28, 2023 @06:31PM (#38453147)
I think I agree with you, but in trivial projects even the infamous slow compilers are fine. Toy Rust projects and small Java projects get compiled very fast.
Re:Python Is Easy. Go Is Simple. Simple != Easy by Cthulhu_ on Thursday November 30, 2023 @07:10AM (#38472521)
It doesn't even have to affect compile times per se, it could be a linter/checker task running separately from the main compiler; most type errors are only relevant during development in my experience. Said experience lately is a lot of Typescript, where all type information is no longer relevant at runtime because it's compiled out or just bluntly removed to make it valid JS (I dunno how the TS compiler works).