3 ms·
The problem was choosing Rust and SvelteKit over Elixir with LiveView (Phoenix) - especially coming from Rails where it’s an easy transition due to shared philo
by cpursley 2y ago
The problem was choosing Rust and SvelteKit over Elixir with LiveView (Phoenix) - especially coming from Rails where it’s an easy transition due to shared philosophy and even syntax to some degree. Rust is neat but complex and probably overkill for a web app. But yeah, in general - innovation tokens cost time vs what you already know.
- physicsguy 2y agoIf few people know Rust, then even fewer people know Elixir. That's a major concern for these types of projects, often.
- cpursley 2y agoLike I've commented maybe 100 times on hn, there's more people who want Elixir jobs than there are Elixir jobs - it's not a real problem. Probably same for Rust. Especially when AI makes it so much easier to get up to speed on a new project, framework, etc these days.
- deleted 2y ago[deleted]
- randomdata 2y agoNow there is a familiar tune! > Few people know Ruby and if you ask a company whether they want to hire PHP or Ruby guys, PHP wins because there's just more people who know it. https://board.phpbuilder.com/d/10312349-php-frameworks-which-to-choose https://board.phpbuilder.com/d/10312349-php-frameworks-which... (First example I found, but was a common trope back in the early days of Rails)
- brink 2y agoI've worked with Rails, I've worked with Phoenix, I've also built with Rust and Svelte. I'd choose Rust+Svelte every time. Much better experience. Rust's async is not nearly as bad as people make it out to be. Building new Rails apps is a blast, but dealing with old Rails apps is a pain, they're difficult to refactor. New Rust apps are great, and dealing with old Rust apps is a much better experience as they're easier to refactor.