4 ms·
Pure JS developers trying to jump off the JS train have a few decent choices now: - Elixir / Phoenix - .NET / Blazor - Laravel / Livewire - Rails / Hotwire
by modernerd 6y ago
Pure JS developers trying to jump off the JS train have a few decent choices now:
- Elixir / Phoenix
- .NET / Blazor
- Laravel / Livewire
- Rails / Hotwire
Or hold on for the JS ecosystem to figure out good patterns that balance performance/maintainability (React Server Components look ok, and will probably trickle into Next.js for those who want a framework).
Does one of the above stand out as a good thing to learn from a career perspective, say, for a JS developer growing tired of frontend?
Is the thirst for React developers ever likely to dry up and leave devs who know these frameworks with an advantage?
- cutler 6y agoWell Blazor ain't gonna reduce your load front-end load, that's for sure.
- danielsokil 6y agoAlso IHP (Haskell) has Auto Refresh https://ihp.digitallyinduced.com/Guide/auto-refresh.html https://ihp.digitallyinduced.com/Guide/auto-refresh.html
- IggleSniggle 6y agoThanks for reminding me about this. I really want to give IHP a try. Seems like a really nice design.
- arvindamirtaa 6y agoIt's really not Rails + Hotwire. It's any backend + hotwire. It works just fine with Django.