Re:Elixir for Ruby developers: the three most important diff...
by manmal on Sunday July 23, 2023 @02:06PM
(#36837964)
As a convenient side effect, GPT-4 is actually quite good at coding in Elixir. I tasked it once to find a bug in an Ecto query and it even improved the query‘s structure. I‘d been worried that, as a small-ish language, Elixir would suffer from bad LLM support, but that’s not the case.
Re:Elixir for Ruby developers: the three most important diff...
by enraged_camel on Sunday July 23, 2023 @04:12PM
(#36839322)
My experience has been the total opposite. It can give simple answers but makes up total nonsense for anything non-trivial.
That said, with Ecto I just ask it to give me the SQL query. From there it’s pretty easy to manually write the Ecto equivalent.
Re:Elixir for Ruby developers: the three most important diff...
by arrowsmith on Sunday July 23, 2023 @04:39PM
(#36839584)
Are you using GPT-4 (the paid version) or GPT 3.5?
3.5 is as you describe. 4 isn't perfect but it's good enough, in my experience.
Re:Elixir for Ruby developers: the three most important diff...
by manmal on Sunday July 23, 2023 @05:56PM
(#36840273)
That was right after the release of GPT-4, when it was slow but good. Haven’t gotten around to much Elixir coding since, it could be that they crippled GPT-4 too much to be of use in the meantime.
Oh and the chat is better for me than the API. API sometimes gives me the complete opposite of what the chat (correctly) gives me.
This is indeed very common the forums, ha. Also common is for people to actually then go read the docs and be like, "Oh crazy, I'm not used to this!" Not to over-sell the quality of the docs, of course they aren't perfect but they really are particularly good.