“The days of using untyped languages on non-trivial projects are over.”
1–10 of 117 posts
Re: “The days of using untyped languages on non-trivial projects are over.”
#2I always wonder why inference a la Hindley-Milner isn't what people push as the best of both worlds.
Re: “The days of using untyped languages on non-trivial projects are over.”
#3I hate TypeScript so much it's unreal. A MS trojan horse to try and own the full stack, I hope you'll all be happy when we won't be able to use any of our tools without complying to corporate linguistic standards and watching the mandatory 20m of commercials per code scope.
Re: “The days of using untyped languages on non-trivial projects are over.”
#4It’s disappointing that a lot of arguments for typing fail to explore why untyped languages became popular to begin with and how those benefits can be maintained throughout the migration process through partial typing To complete typing.
When typing is applied gradually throughout a codebase it can sometimes manifest as the worst of both world and a complete argument should at least acknowledge that as well as the impact of bad typing on codebases.
Re: “The days of using untyped languages on non-trivial projects are over.”
#5The days of sweeping declarations regarding obviously periodic trends have never arrived.
I've been around long enough that "safe" gave way to "productivity" and back to "safe". There's kind of a nascent ethos of being "better" in each new generation that just results in these pendulum effects.
The overall effect seems to be enormously positive. I can now bounce between several completely valid build environments, ecosystems, and languages for a given project depending on what is required. But make no mistake. Our kids will probably look at us like we're crazy as they embrace the 2040 equivalent of JavaScript and Python again.
Re: “The days of using untyped languages on non-trivial projects are over.”
#6Typescript propaganda.
Instead of worrying about types, why not worry about the actual code quality?
Half of all typescript I've seen uses "any", not to mention the fact that it obsfuscates what's actually running in the browser and forces an unnecessary build step for things that aren't "web apps".
Re: “The days of using untyped languages on non-trivial projects are over.”
#7It’s disappointing that a lot of arguments for typing fail to explore why untyped languages became popular to begin with and how those benefits can be maintained throughout the migration process through partial typing To complete typing. When typing is applied gradually throughout a codebase it can sometimes manifest as the worst of both world and a complete argument should at least acknowledge that as well as the im…
> why untyped languages became popular to begin with
because for a long time there were no mainstream languages with a good enough type system.
Re: “The days of using untyped languages on non-trivial projects are over.”
#8It’s disappointing that a lot of arguments for typing fail to explore why untyped languages became popular to begin with and how those benefits can be maintained throughout the migration process through partial typing To complete typing. When typing is applied gradually throughout a codebase it can sometimes manifest as the worst of both world and a complete argument should at least acknowledge that as well as the im…
What are the downsides of gradual typing on a codebase? I've never worked with it, but watched some talks on it and it really sounds promising. I understand the downsides for compiler complexity and for performance, but not on the codebase itself.
Re: “The days of using untyped languages on non-trivial projects are over.”
#9Gradual typing is not the best of both worlds.
On a large project, a lot of discipline is needed to make sure typing gets used everywhere.
Even worse, when you have a prototype that morphs into a large enterprise application, someone needs to go back and fill in all the types. This can be a struggle if everyone is gone.
basically this just kicks technical debt down the road.
Re: “The days of using untyped languages on non-trivial projects are over.”
#10this would be nice, but no, not going to happen.
JavaScript, Python, PHP, Ruby etc fill a niche. Personally I love strongly typed languages, but I get why people don't want to deal with it. I am old school and do not use an IDE, so for me strong typing is a must.