4 ms·

Your last sentence is a bit of a gut punch tbh - I was meaning to get more familiar with Elixir for side projects, and I’ve made a few small web apps with LiveV

by manmal 1y ago

Your last sentence is a bit of a gut punch tbh - I was meaning to get more familiar with Elixir for side projects, and I’ve made a few small web apps with LiveViews. Absolutely love it, even though I don’t feel I‘ve grasped the language fully yet. But some research shows that most LLMs don’t support Elixir that well. But since my free time is so extremely limited, it would be really nice to get better LLM and agent support. So I hope the lesser used languages and frameworks get more training love, soon. Lest we all only use Next for hobby projects in the future.

_bin_ 1y ago
Unfortunately this is consistent for non-ultra-mainstream langs. They’re next to unusable for complex Haskell. If you want to vibe code, it’s Python/typescript/react or nothing.
- skydhash 1y ago
  I wonder how well they do for Go and Java. The first is a boring language where there's little to none chance to stray from the default. The second is verbose, but with strict rules on the syntax.
  - egeozcan 1y ago
    They are fine with Go. Not with whole codebases but libraries/functions around a thousand lines of code are written perfectly with tests (Although, I always say, never let the LLM write the tests AND the code, or at least write your own tests in addition to what it generates).
atonse 1y ago
Elixir has been my main language since 2017 and it’s been amazing to work with all these years. I’ve built and delivered so much value and the quality of libraries in general feels much more stable than JS land with its ever changing upgrades. I’ve never had to worry about leaving a code base untouched for 6 months. Whereas in JS land I’d have to groan about half the stuff not working, some new transpiler breaking changes, blah blah and just give up. But developer ergonomics rough edges mostly around LiveView, and partially language servers and type support (which recently had some developments) and bad LLM support (no fix yet) are finally causing me to question whether I should look elsewhere. The underlying tech (scalability, echo, etc) has still been excellent.
TimTheTinker 1y ago
Honestly, I'd strongly suggest not using an LLM to get started on a new language. It'll be harder at first, but you'll build intuition about how things work under the covers (especially important when the runtime environment is unique like the Erlang OTP), and you'll build your ability to code idiomatically. Instead, read lots of great code in that language and incrementally work to understand and imitate its style. The standard library and any popular tools written in it would be good places to start.

by manmal 1y ago

_bin_ 1y ago

Unfortunately this is consistent for non-ultra-mainstream langs. They’re next to unusable for complex Haskell. If you want to vibe code, it’s Python/typescript/react or nothing.

skydhash 1y ago
I wonder how well they do for Go and Java. The first is a boring language where there's little to none chance to stray from the default. The second is verbose, but with strict rules on the syntax.
- egeozcan 1y ago
  They are fine with Go. Not with whole codebases but libraries/functions around a thousand lines of code are written perfectly with tests (Although, I always say, never let the LLM write the tests AND the code, or at least write your own tests in addition to what it generates).

atonse 1y ago

Elixir has been my main language since 2017 and it’s been amazing to work with all these years. I’ve built and delivered so much value and the quality of libraries in general feels much more stable than JS land with its ever changing upgrades. I’ve never had to worry about leaving a code base untouched for 6 months. Whereas in JS land I’d have to groan about half the stuff not working, some new transpiler breaking changes, blah blah and just give up. But developer ergonomics rough edges mostly around LiveView, and partially language servers and type support (which recently had some developments) and bad LLM support (no fix yet) are finally causing me to question whether I should look elsewhere. The underlying tech (scalability, echo, etc) has still been excellent.

TimTheTinker 1y ago

Honestly, I'd strongly suggest not using an LLM to get started on a new language. It'll be harder at first, but you'll build intuition about how things work under the covers (especially important when the runtime environment is unique like the Erlang OTP), and you'll build your ability to code idiomatically. Instead, read lots of great code in that language and incrementally work to understand and imitate its style. The standard library and any popular tools written in it would be good places to start.