3 ms·

Very interesting to see Laravel pivot to this direction (VC-backed cloud deployment and hosting solution) while Rails pivots the other way (Kamal deploy with br

Very interesting to see Laravel pivot to this direction (VC-backed cloud deployment and hosting solution) while Rails pivots the other way (Kamal deploy with bring-your-own cloud/provider/server). Obviously you can still (for now, anyway) 100% run Laravel independently without Laravel cloud or any of the optional paid Laravel features. But you don't have to squint too hard to see the Laravel core team starting to prioritize features that benefit Laravel Cloud and then slowly start building Laravel Cloud-only features. Especially as VC demands larger returns. I have a lot of respect for Taylor Otwell and I am happy he's found a way to continue to monetize his life's work, but I hope they're able to find a sustainable balance between free/open source work and paid/proprietary work.

yurishimo 2y ago
I think we need another year or two to see how this pans out. Supposedly the Laravel team has features for Forge on their roadmap. I’ve listened to quite a few podcasts with Taylor speaking on this topic and he’s very aware that the majority of Laravel devs know that hosting a PHP app is not rocket science. He wanted to built a platform that offered a substantial bump to the UX of managing servers but realizes that it will never be a solution used by companies that want to fine tune the software or do weird shit. Given the track record of Laravel so far, I’m willing to hear them out and let them cook for a bit before casting judgement. Taylor has also said he’s not in it for the money but only time will tell if he can hold onto that ideal as time marches forward.
- dcchambers 2y ago
  Oh absolutely.