This one, specifically, provided such awesome insights into the backend and frontend branches of development. My company has been doing SPAs for around 8 years now and we did try a few times "inertia" and "livewire" kind of approach and it always made it easier. The concept of a non-SPA full stack development is not easy to "push for acceptance" - especially to "older/senior" decision makers. Great points BTW. Would be using some of the arguments for non-SPA development. Thanks guys.
Just whipped up something with Folio and Volt and it was pretty fun. IMO NextJS is still superior from a frontend developer perspective, but having access to all the Laravel goodies like Eloquent, Queue Jobs, Authentication, middlewares etc. is amazing.
Another great episode Matt! Regarding Laravel's future- I hope adding Swoole coroutine support to Octane is on the list. There was some talk about doing it a few years ago but it's a fair bit of work. It'd push Laravel's performance up into to the Go / Rust league. The cost savings would significant for high traffic apps. Most apps running multiple instances behind a load balancer could easily get away with a single instance.
Let me please ask a question because honestly I would like to understand: if Taylor works a lot in these kind of tools like Laravel Pulse and others and supposing that those are free and/or open source, could you tell in which ways does he earn money? Regards.
This one, specifically, provided such awesome insights into the backend and frontend branches of development.
My company has been doing SPAs for around 8 years now and we did try a few times "inertia" and "livewire" kind of approach and it always made it easier.
The concept of a non-SPA full stack development is not easy to "push for acceptance" - especially to "older/senior" decision makers.
Great points BTW. Would be using some of the arguments for non-SPA development.
Thanks guys.
Just whipped up something with Folio and Volt and it was pretty fun.
IMO NextJS is still superior from a frontend developer perspective, but having access to all the Laravel goodies like Eloquent, Queue Jobs, Authentication, middlewares etc. is amazing.
Great podcast!
Another great episode Matt! Regarding Laravel's future- I hope adding Swoole coroutine support to Octane is on the list. There was some talk about doing it a few years ago but it's a fair bit of work. It'd push Laravel's performance up into to the Go / Rust league. The cost savings would significant for high traffic apps. Most apps running multiple instances behind a load balancer could easily get away with a single instance.
This package is thrilling and I cant wait to try it out
Just love this podcast, thanks for doing this! Always fun and interesting to watch you both talk through all these questions and topics! 👍
Thank you so much! :) We're so glad you like it!
Watching after deploying Pulse to production
Laravel-Vite HMR not working for JSX in some reason and no merge manifest feature like mix
Hi, this forum is not a place where we can provide coding support. Thanks!
great episode.
taylor's sound needs adjustment tho.
Thanks! We'll work on that for next episode :)
Let me please ask a question because honestly I would like to understand: if Taylor works a lot in these kind of tools like Laravel Pulse and others and supposing that those are free and/or open source, could you tell in which ways does he earn money? Regards.
Just to make laravel echo system strong. He is already earning from Forge, nova and other paid services
Once it's out of beta, I will use it.
Is there any plan to support more queue driver by default? RabbitMQ, Kafka, GCP PubSub
Unfortunately we can't speak to whether or not that's the case in this forum. Thanks!
What about splade? Splade looks like a better nicer choice of both worlds. You have vue power from blade.
Oh man that is awesome! Where did you hear about this?
Promo*SM 🤘