4 ms·
>>And Phoenix would be the Rails to Erlang's Ruby (Elixir). The learning curve is steep, you will need to learn OTP. Which is probably why adoption lags. You d
by enraged_camel 8y ago
>>And Phoenix would be the Rails to Erlang's Ruby (Elixir). The learning curve is steep, you will need to learn OTP. Which is probably why adoption lags.
You don't need to learn OTP to become productive in Elixir/Phoenix. It's abstracted away from you, but also gives you the ability to dive in if you want/need.
- brightball 8y agoAgree. You don’t need to learn OTP to use Phoenix anymore than you need to learn the entire Java ecosystem to use Kotlin. Erlang has been around for 30+ years...there’s a lot. Doesn’t mean you need to use it all.
- bitwalker 8y agoI think it's disingenuous to say you don't need to learn OTP. You need to learn the basics of it, or you will struggle, because you will be trying to solve problems in a way that doesn't fit with the underlying language and runtime. That said, learning the basics of OTP is super easy, and can be done in an afternoon (spawning processes, sending messages, supervision, understanding what applications are in Erlang/Elixir parlance). It's like saying you can build a Rails app without understanding classes/objects - sure maybe you could throw something together because the tools are so friendly, but you would get lost pretty quick when trying to do something on your own. Learn those basics up front, and you can get a long way without having to delve into more advanced topics.
- brightball 8y agoBasics, sure. I think you learn the basics just to learn Phoenix though.