131–140 of 152 posts
Earlier quoted context omitted.
I have the opposite experience. Even in production builds, I get Elixir stacktraces, and they're exceptionally helpful. Macros only save me time and LoC, I think maybe once I've struggled with a macro-caused issue (and it was immediately apparent that macros were the issue). ExUnit has been hands down the most impressive testing library I've ever worked with, and the debugging, profiling, analytics, introspection, ob…
When you say "above any language I've ever seen", can you be more explicit? Do you have an example? I have a lot of respect for the community behind it but the experience is still not there.
The progressive introduction of automated type checking in Elixir should serve as a reference on how to improve a programming language gracefully without breaking changes. So many examples of programming languages have huge breaking changes between versions that end up creating a split in the ecosystem that takes years to resolve. Thankfully José has been very clear about Elixir being done since at least 2018. The la…
Earlier quoted context omitted.
Don't know about Scala alternative, but the language I've found most enjoyable on the JVM is definitely Kotlin.
I wonder sometimes how much Kotlin contributed. It’s certainly a case that languages need to be championed by competent IDE writers otherwise they fail to scale. Because you can’t have 50 devs all using neovim - and only neovim - without making a huge gigantic mess. Large projects can sustain a few brilliant people working with one hand tied behind their back but not everyone.
I tried few times checking on it, but I failed to find something that motivated me to continue
Earlier quoted context omitted.
> So many examples of programming languages have huge breaking changes between versions I can only think of 2: python 3 and perl 6. Those two were very traumatic so it's not surprising it feels like more.
Java 8 -> anything 11+ wasn't great at scale. It's been smooth sailing for a long time again though.
The progressive introduction of automated type checking in Elixir should serve as a reference on how to improve a programming language gracefully without breaking changes. So many examples of programming languages have huge breaking changes between versions that end up creating a split in the ecosystem that takes years to resolve. Thankfully José has been very clear about Elixir being done since at least 2018. The la…
Dart is doing slow nullable changes slowly , opt in. Last time I took a peek
Dart 2.12 (released March 2021) introduced null-safety.
That started a 2 year transitionary period during which you could mix nullsafe (language versions 2.12 or above) and non-nullsafe (language versions below 2.12) code in one program.
Dart 3.0 (released May 2023) removed support for language versions prior to 2.12 - meaning that you can no longer opt out of null-safety.
Earlier quoted context omitted.
I wonder sometimes how much Kotlin contributed. It’s certainly a case that languages need to be championed by competent IDE writers otherwise they fail to scale. Because you can’t have 50 devs all using neovim - and only neovim - without making a huge gigantic mess. Large projects can sustain a few brilliant people working with one hand tied behind their back but not everyone.
I'm curious about Kotlin. What makes it great for you? I tried few times checking on it, but I failed to find something that motivated me to continue
But as I said above, I realized long ago that languages without IDEs by and large falter in the long term (that's why I'm currently concerned about Jetbrains needing a buggy plugin to do Elixir), so Jetbrains being behind it added a lot of gravitas.
And after fighting with Larry Ellison for a bit, Android phones moved to Kotlin to get around the lawyers.
Earlier quoted context omitted.
When you say "above any language I've ever seen", can you be more explicit? Do you have an example? I have a lot of respect for the community behind it but the experience is still not there.
I think it would be easier for all of us to understand if you elaborated on what you think the issues are. What concrete things are you missing from ExUnit and documentation, what do you wish was different?