Hacker News new | ask | show | jobs
by bnchrch 869 days ago
Disclaimer: Elixir is extremely productive, Phoenix is outstanding, the community is world-class, and as a result of the Erlang VM / OTP / Beam you can remove whole parts of your traditional webstack. If you haven't tried it I cannot recommend it enough.

But!

As a long-time Elixir Developer who has gladly used it to bootstrap many applications and companies, I have to say I think this article is actively harmful to the community.

It's an extremely thinly veiled sales pitch for their "Petal Pro" paid boilerplate.

At the same time, it does nothing to address the tradeoffs of certain features like Live View. Which for the record is a poor fit if your app suffers from client-side latency or requires any kind of offline-enabled features.

5 comments

I can't speak for Tyler (the author) but as someone who's worked with him and managed him for over 2 years, I'd say take Tyler at his word versus assigning malice to his writing.

He's a powerhouse of a developer, loves, LOVES the ecosystem and has always wanted to give back as much as he could. He's submitted patches to the core, he did so much for our Elixir CI and felt bad not giving it back via open-sourcing it and then blogging on our platform.

Tyler was instrumental in many of our technical decisions at our company, and I can confidently say nothing he made us buy was unnecessary, and he often worked very hard to save us the smallest bit of money.

Just my 2 cents!

Author here! I've not been compensated by the Petal Pro devs at all. I've interacted with them exactly twice—once in support and once to submit the world's tiniest PR. I'm just a happy customer.

(If that's not enough, you can dig in to the Petal Components repo and see I'm not a contributor.)

Ah shoot, well then I'm sorry, that is unfair criticism on my part.

The pitch was just so direct, coupled with the perfect topic of "Want to build a SaaS? Use Elixir" I would have assumed you owned the paid boilerplate you discussed.

I unfortunately can't edit the post but I upvoted this in the hopes that people see it.

No sweat, I get it! :D
Endorse 100%.

The lack of discussion about LiveView tradeoffs is one of the few things I actively dislike about the Elixir community: and I love elixir and reach for it for almost everything.

The author does not own Petal Pro nor is he affiliated with it in any way.
> requires any kind of offline-enabled features

Considering it requires a server this is kind of a given right?

I am not your parent poster but I would interpret their comment as:

If you need offline mode you are better off disabling / removing the LiveView machinery in your Phoenix project.