# thinking-together


04/11/2023, 8:58 AM
Brooks said in the Mythical Man Month. Fail. Fail again. Succeed. You want to find a way to fail-fast the first two times. Using type-checked, bloatware languages ain’t the way to fail-fast.
I would, further, modify this to 1. Fail. 2. Fail again. 3. Succeed. 4. Productize. Using type-checked, bloatware languages ain’t the way to perform steps 1-3. Architecture ≡ 1-3 Engineering ≡ 3 Coding ≡ 4 Production Engineering ≡ 4 Q/A ≡ 4 ...

Joakim Ahnfelt-Rønne

04/11/2023, 4:01 PM
Type checking allows you to detect failure even before you run the code. It's a way to fail even faster.

Andrew F

04/11/2023, 5:04 PM
Just don't conflate "type checked" and "bloatware". It's definitely bad to have both, but they're not the same. I really wish OCaml would take off. I really really wish 1ML would take off, but last I heard that's still a research prototype, so... :( I guess we're relying on Rust and Swift to carry the torch of nice types into the mainstream. (I like Rust, but everyone would be better served by it being a niche language for when GC is unaffordable.)

Ulysses Popple

04/16/2023, 10:52 AM
Ocaml is used by jane st. Idk if that's taking off necessarily, but by dollar effect it might rank fairly high in languages.
Typescript types aren't too bad. There's definitely some bloat though.

Andrew F

04/17/2023, 1:42 PM
I'd prefer that it was an officially supported app development language on a mainstream OS. :-/

Alex Cruise

04/19/2023, 5:19 PM
Unfortunately, the prototype always ships to production

João Araújo

04/22/2023, 2:53 PM
just adding my voice to types != bloatware, and type inference has come a long way and made it much easier to use static typed languages while still getting its benefits