Laravel Pulse, First Party Packages, & the Future of Laravel

In this episode, we're unwrapping the highlights from Laracon AU, with a special focus on Laravel Pulse leading our discussion. Taylor takes the reins to guide us through the origins and functionality of Laravel Pulse, a health monitoring tool for your Laravel applications.
We then shift our discussion to Laravel first party packages. Taylor openly shares insights into his decision-making process—revealing how he selects packages to join the Laravel family and when it's time to bid them farewell.
Our conversation doesn’t end there though. We also look at the future of Laravel and examine the strategies used for continually injecting innovation and fresh ideas into the Laravel ecosystem.


-----

[JagdeepSinghKalsi]

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.

[zachariascreutznacher]

Just love this podcast, thanks for doing this! Always fun and interesting to watch you both talk through all these questions and topics! 👍

[crhayes]

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.

[binaryfire]

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.

[ByteOdyssey]

This package is thrilling and I cant wait to try it out

[sarsoeurng]

Laravel-Vite HMR not working for JSX in some reason and no merge manifest feature like mix

[kennedymwenda]

Watching after deploying Pulse to production

[fernandogonzalez-qvnh]

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.

[mokhosh]

great episode.
taylor's sound needs adjustment tho.

[DoubleOBond]

Once it's out of beta, I will use it.

[rafaelacioly]

Is there any plan to support more queue driver by default? RabbitMQ, Kafka, GCP PubSub

[sergyuma]

What about splade? Splade looks like a better nicer choice of both worlds. You have vue power from blade.