Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Erlang/OTP 29.0

erlang.org

Post reply on HN
Print view View original

21–30 of 64 posts

Re: Erlang/OTP 29.0

#21

Post by sph »

faangguyindia wrote: post #14

Who even uses Erlang? I used Rails and then i tried Phoenix and it was lot more difficult to get things done. I don't understand Phoenix hype For solo devs, Rails is arguably most productive webapp system. LLM is very good at writing ruby rails code. Much better than writing django in my experience even though python training corpus is huge. I write my experimental apps in Rail when it stabilizes, i do a Go rewrite.…

I’ve been writing Elixir apps full time since 2016. Clients are very, very happy never to see a crash. In fact, all the applications I have deployed in production in the past 10 years have 100% uptime. (Apart from hardware, OS and network faults outside my control)

You might want to broaden your horizons.

Re: Erlang/OTP 29.0

#22

Post by out_of_protocol »

sbrother wrote: post #10
ch4s3 wrote: post #7

I'm interested to see how records play out in the ecosystem.

I was about to say "what, we've had records for decades" but then I read the changelog. Interesting. I wonder if there a world where Elixir starts compiling maps to "native records"?

Probably going to be replacement rather than direct recompilement of structs. I imagine all sorts of corner cases are lurking around if you swap implementation around, e.g. if someone force-pushed unknown key into a struct at runtime. Would be nice to keep current struct syntax though with the only difference in declaration

Re: Erlang/OTP 29.0

#23

Post by out_of_protocol »

faangguyindia wrote: post #14

Who even uses Erlang? I used Rails and then i tried Phoenix and it was lot more difficult to get things done. I don't understand Phoenix hype For solo devs, Rails is arguably most productive webapp system. LLM is very good at writing ruby rails code. Much better than writing django in my experience even though python training corpus is huge. I write my experimental apps in Rail when it stabilizes, i do a Go rewrite.…

I'd say Rails is faster than Phoenix (as in development speed) only for the first day or so. After that you'll stumble upon impicit logic, method-missing and this kind of stuff, which will require more time to figure out how it works. Elixi/Phoenix is more exlicit in that regard, making long-term support (as in anything past first week) a breeze. No hidden state, no figuring out where ModuleName.method(params) is coming from, no need to setup stuff to launch said method (just pass right arguments). The only downside i see is smaller library of ready to use packages

Re: Erlang/OTP 29.0

#24

Post by faangguyindia »

out_of_protocol wrote: post #23
faangguyindia wrote: post #14

Who even uses Erlang? I used Rails and then i tried Phoenix and it was lot more difficult to get things done. I don't understand Phoenix hype For solo devs, Rails is arguably most productive webapp system. LLM is very good at writing ruby rails code. Much better than writing django in my experience even though python training corpus is huge. I write my experimental apps in Rail when it stabilizes, i do a Go rewrite.…

I'd say Rails is faster than Phoenix (as in development speed) only for the first day or so. After that you'll stumble upon impicit logic, method-missing and this kind of stuff, which will require more time to figure out how it works. Elixi/Phoenix is more exlicit in that regard, making long-term support (as in anything past first week) a breeze. No hidden state, no figuring out where ModuleName.method(params) is com…

but if you want explicit any not just use django?

Re: Erlang/OTP 29.0

#25

Post by ellbee »

faangguyindia wrote: post #14

Who even uses Erlang? I used Rails and then i tried Phoenix and it was lot more difficult to get things done. I don't understand Phoenix hype For solo devs, Rails is arguably most productive webapp system. LLM is very good at writing ruby rails code. Much better than writing django in my experience even though python training corpus is huge. I write my experimental apps in Rail when it stabilizes, i do a Go rewrite.…

Would you like to take a guess what the Ruby Discord uses?

Re: Erlang/OTP 29.0

#26

Post by pmontra »

faangguyindia wrote: post #14

Who even uses Erlang? I used Rails and then i tried Phoenix and it was lot more difficult to get things done. I don't understand Phoenix hype For solo devs, Rails is arguably most productive webapp system. LLM is very good at writing ruby rails code. Much better than writing django in my experience even though python training corpus is huge. I write my experimental apps in Rail when it stabilizes, i do a Go rewrite.…

I used both Rails and Phoenix.

ActiveRecord is more pleasant to work with than the ORM of Phoenix IMHO, but not everyone shares the same feeling.

Despite having built in concurrency my team ended up building a version of Sidekiq because supervisors don't cover all use cases of job control.

I prefer deploying with Capistrano than with Elixir builds. Another matter of taste.

Structural pattern matching is the only feature I dearly miss, but that's a feature of the language.

We never used Liveview. We had a backend for a JSON API so I can't compare that feature.

Re: Erlang/OTP 29.0

#27

Post by out_of_protocol »

pmontra wrote: post #26
faangguyindia wrote: post #14

Who even uses Erlang? I used Rails and then i tried Phoenix and it was lot more difficult to get things done. I don't understand Phoenix hype For solo devs, Rails is arguably most productive webapp system. LLM is very good at writing ruby rails code. Much better than writing django in my experience even though python training corpus is huge. I write my experimental apps in Rail when it stabilizes, i do a Go rewrite.…

I used both Rails and Phoenix. ActiveRecord is more pleasant to work with than the ORM of Phoenix IMHO, but not everyone shares the same feeling. Despite having built in concurrency my team ended up building a version of Sidekiq because supervisors don't cover all use cases of job control. I prefer deploying with Capistrano than with Elixir builds. Another matter of taste. Structural pattern matching is the only feat…

> ActiveRecord is more pleasant to work with than the ORM of Phoenix IMHO, but not everyone shares the same feeling.

Well, depends on what you do. Ecto is closely follows SQL logic and allows to translate weird sql queries into code directly. All queries are explicit, e.g. you either do preload(...) or can't access nested records at all, no chance of N+1 by design.

Changesets are also different and are just functions you can define as needed.

    defmodule MyApp.User do
    ...
    def changeset(user, attrs) do
        user
        |> cast(attrs, [:email])
        |> validate_required([:email])
        # This matches the error from the DB uniq index to the :email field
        |> unique_constraint(:email)
    end

Re: Erlang/OTP 29.0

#28

Post by sph »

pmontra wrote: post #26
faangguyindia wrote: post #14

Who even uses Erlang? I used Rails and then i tried Phoenix and it was lot more difficult to get things done. I don't understand Phoenix hype For solo devs, Rails is arguably most productive webapp system. LLM is very good at writing ruby rails code. Much better than writing django in my experience even though python training corpus is huge. I write my experimental apps in Rail when it stabilizes, i do a Go rewrite.…

I used both Rails and Phoenix. ActiveRecord is more pleasant to work with than the ORM of Phoenix IMHO, but not everyone shares the same feeling. Despite having built in concurrency my team ended up building a version of Sidekiq because supervisors don't cover all use cases of job control. I prefer deploying with Capistrano than with Elixir builds. Another matter of taste. Structural pattern matching is the only feat…

> ActiveRecord is more pleasant to work with than the ORM of Phoenix IMHO

A stateful mechanism vs a data mapper? Absolutely not. Being able to write `user.save()` is such a lunacy, thank god we have functional languages that (necessarily) decouple storage from data models.

I cringe every time I have to use imperative, stateful languages.

Re: Erlang/OTP 29.0

#29

Post by out_of_protocol »

faangguyindia wrote: post #24
out_of_protocol wrote: post #23

Earlier quoted context omitted.

I'd say Rails is faster than Phoenix (as in development speed) only for the first day or so. After that you'll stumble upon impicit logic, method-missing and this kind of stuff, which will require more time to figure out how it works. Elixi/Phoenix is more exlicit in that regard, making long-term support (as in anything past first week) a breeze. No hidden state, no figuring out where ModuleName.method(params) is com…

but if you want explicit any not just use django?

Django is not very different than Rails and imo much less ergonomic. Many issues are still there like hidden state/setup needed to call something

Re: Erlang/OTP 29.0

#30

Post by signa11 »

sph wrote: post #21
faangguyindia wrote: post #14

Who even uses Erlang? I used Rails and then i tried Phoenix and it was lot more difficult to get things done. I don't understand Phoenix hype For solo devs, Rails is arguably most productive webapp system. LLM is very good at writing ruby rails code. Much better than writing django in my experience even though python training corpus is huge. I write my experimental apps in Rail when it stabilizes, i do a Go rewrite.…

I’ve been writing Elixir apps full time since 2016. Clients are very, very happy never to see a crash. In fact, all the applications I have deployed in production in the past 10 years have 100% uptime. (Apart from hardware, OS and network faults outside my control) You might want to broaden your horizons.

hello,

would you please recommend a good resource to get started with elixir ?

thanks for your time !

Post reply on HN