Re:Why Elixir? A Rebuttal to Common Misconceptions
by throwawaymaths on Wednesday July 23, 2025 @03:33PM
(#44663066)
sure, a few years behind typescript/mypy isnt really so bad for a language without a microsoft or a google behind it, is all im saying.
Re:Why Elixir? A Rebuttal to Common Misconceptions
by tossandthrow on Wednesday July 23, 2025 @04:02PM
(#44663359)
> isnt really so bad for a language without a microsoft or a google behind it, is all im saying
What? Elm was literally the result of a single grad students side project - elm incorporates both a sound type system and FRP.
This has nothing to do with time. It was a decision not to support it.
Re:Why Elixir? A Rebuttal to Common Misconceptions
by throwawaymaths on Wednesday July 23, 2025 @07:28PM
(#44665154)
sure part of the decision is that you can't really soundly type (in a developer sanity preserving way) across a cluster that runs multiple versions of software (which is a real use case that the authors absolutely needed to support as part of the core business). but they let dialyzer in to the core so it's not like the team was actively hostile to typing.
Re:Why Elixir? A Rebuttal to Common Misconceptions
by tossandthrow on Thursday July 24, 2025 @04:53AM
(#44668537)
These are some weird sentences thrown into this thread.
What you are describing is a runtime concern that has nothing to do with types.
These issues are neither amplified nor alleviated by using types.
I see this story on an on: some hacker makes a language, they hate types because they want to express themselves. The languages gets traction. Now enterprise application and applications with several devs use it and typing gets essential - types will then gradually be added.