Switching Your Tech Stack (Rails to Laravel). Worth it?
Вставка
- Опубліковано 8 лип 2024
- This week unpacking the question, is it worth it to switch my go-to tech stack for building new products? I happen to be a Rails developer exploring Laravel, but this question (and this video) applies no matter which stack(s) you're using or considering.
It's a business question. Not a tech question. Let's get into it.
What do you think?
00:00 - Should you switch your tech stack?
0:18 - Question
1:13 - This vs That Stack
2:44 - Worth the time?
6:11 - 4 important factors
7:59 - Healthy ecosystem
9:11 - Streamlining your business' tech stack
10:42 - At the end of the day...
13:24 - A business decision
Got a new product to ship? Let's work together: instrumentalproducts.com
Good for you to brave enough to look over the fence, which ever way you choose, it is always good to review other languages for different perspectives every year or two.
Hey, it’s the Bootstrapped Web / Restaurant Engine / productize / audience ops guy! Haven’t listened to you in a while, but I’ve learned a ton from you over the years.
Ha good to hear!
I’ve sold and moved on from 3 of those 4 things :)
He is still sticking with Rails. 😁 Because Rails is freedom and kingdom!
How is your exploration of Laravel going? I noticed you switched your Instrumental Products site over to Laravel. Are you starting new client projects in Laravel? Are you close to deciding? Asking because I'm just starting to look into this too.
Actually I’m sticking with Rails for all apps I work on.
For my websites I use Statamic CMS, which is Laravel based.
@@briancasel Awesome, thanks for the input.
I can't imagine any scenario where'd it'd be worth going from Rails to Laravel if you already have a functioning application. Sure, ruby kinda sucks, but both frameworks are so similar. I'd ride it out until some scaling issue causes you to have to change things.
It's almost always worth the effort to try and learn new things, though.
I should have clarified... Definitely not talking about migrating an existing application from Rails to Laravel (no way).
This is about learning a new stack to build new products on going forward.
I'm interested in what part of Ruby you think sucks, especially compared to PHP. When looking at Laravel code and Rails code I'm really stumbled about how anyone could prefer PHP. Almost every aspect of the Rails framework feels more polished and it's mostly about the Ruby language. Of course, PHP is "easier" to learn but Rubys meta programming abilities is superior.
One very apparent example is Eloquent vs ActiveRecord imho. No problem when you are getting a collection of posts, but when doing validation, relations, more advanced query building, fighting n+1 queries etc ActiveRecord is superior. Also ActiveRecord is database agnostic, while Eloquent is only MySQL, right?