enterhas.blogg.se

Kelp 4 less
Kelp 4 less







kelp 4 less kelp 4 less

The other issue they faced, though I doubt it was as much of an obstacle, was that they were working on pet insurance. The CTO and other devs on the team painted a bleak picture of building the team, and elixir seemed to be the main obstacle. Part of what worried me was realizing just how much they struggled to find interested candidates, and it seemed like they were willing to compromise to hire as a result. I interviewed a company a while back that was using elixir which I thought was cool, but I ended up not taking the job. I suppose part of the concern is finding people who actually want to use your tech stack too, though. It's not perfect (lord knows I wish there were more libraries). The tooling is descent, the day to day ergonomics let me focus on solving our startup's problems rather than wrestling with the platform. Python comes close if you're willing to take a drastic hit on performance. I haven't encountered a language that does that better yet. Now if we're talking Pareto efficient intersection of performance, developer productivity and maintainability, yea elixir hits that sweet spot well. (yes I know an experienced haskell dev will probably be jsut as productive as a experienced elixir dev but it will take much longer to train someone from another language to haskell than to elixir.)Ĭonversely, if you want speed at all costs, rust is certainly nice. If you absolutely need to cut down errors to a minimum and are willing to sacrifice developer speed/productivity, Haskell with IHP is certainly a compelling offer. Its all about the tradeoffs you're going after. Elixir is s a platform that fits a nice sweet spot where you need to knock something out fast and still have something reasonably maintainable (and refactorable) that also happens to be really fast(performance wise) for the level of day to day developer productivity you get.īetter is subjective so I'd rather not go into that too deeply haha. Source: me with 6 years of elixir experience and having built the entire backend for my startup in elixir over the last 3 years.

kelp 4 less

you don't have to bother with that last 20% of functional programming rabbit hole crazy town.

kelp 4 less

TLDR: yes Elixir is functional but its the 80% that is easy to learn. you don't have to make special functions marked as IO or use any type of exotic type theory. Elixir in contrast gives you genservers for state which is very simple by comparison as well as having dead simple IO. If anything it really only makes you pickup immutable data, pass by value, immutable bindings (with implicit lets)įunctional programming gets really hard when you try doing stuff like state and IO monads. day to day elixir work doesn't require you to understand currying, abstract types or monads. Functional programming overall isn't that difficult.









Kelp 4 less