And also I was there!!!

Oh hi aaron

@@aarondfrancis Absolutely, you are like social lubricant. A powerhouse in your own right. Perfect episode

@@cherkim whew, I'll take it

I was writing my SaaS in NextJS+Typescript and hitting exactly this. I decided to try a 2 week sprint spinning up an alternate version in Laravel+Inertia and quickly realised how much more “batteries included” the Laravel stack was. There’s no comparison. I haven’t looked back.

@@fatalglory777this is the way

In my case, I always try to write it myself which leads me to spend a week pulling in and trying libraries, learning about it. When I'm done I've lost all energy and momentum to build the product I was excited about. So another abandoned app gets to litter my repos folder. I've recently picked up Adonis because it reminds me of Laravel. I'm coming around to the fact that maybe I should stop looking for alternatives to Laravel and just use it.

@@rumble1925 I went through a very similar process, lol. I recommend just use Laravel. With inertia you can still get all the good react stuff on the frontend.

Curious about your story, how did you get started, what type of work do you do?

​@@rumble1925 Hey! Yeah so I was working in an agency in The Netherlands and got sick of 9-5 so I partnered up with a good friend who focuses on the frontend and we started looking for clients. Not long after that we stumbled upon another 2 person design agency looking to get into the web dev world and the rest just flew from there. We work about 70% of the time with CMS sites (Statamic but with our own Blade version) and C# Umbraco. The other 30% is SaaS and making bespoke platforms for startups which we do in Laravel (and very rarely, if they request it, with .NET). It's all about putting yourself out there!

there is laravel idea or laravel.nvim

Glad someone caught that 😂

Even guys with Lambos need to empty dishwashers.

I liked them at first, until I realized they're not mockable/stubbable 😅

@@nimmneun haha 💯, man don't even get me started 😂

hahaha :D The devil himself :D

If it's worth anything: I know two types of software devs. Those who got a cs degree and got a job because of that. And those who learned to make simple websites and scaled from there. There's always someone who just wants a website.

What's special about Astro DB? Isn't it just a managed SQL database, like I can get from Neon, RDS, or other managed dbs? I mean, looking from their website, it does not look like something special, despite that it has first-party support to Astro. It does not sound like something that's part of the framework itself, but a service you'll have to pay, same for authentication (Laravel does not require developer to get a number of services to have auth, db, etc).

@@vanderleisbarainiamancio8369 ^ a lot of js eco is paying for infra when in php is more about doing it yourself and scaling later. dax made a great point that js is mostly cloud. personally I like to orchestrate services locally using docker or service providers before shipping to the cloud.

I use PHP since version 4, when there were many horrible programmers using PHP in the craziest ways., It's not like that anymore, for years. PHP has improved so much, it's not the mess it was back in the past (programmers' fault honestly) and its performance today is absolutely very good, and the RFCs show us that it will keep improving. We can run it on nginx, apache, caddy, Franken, Lambda; we can distribute it using a single executable file, if a bug in the code is found, it does not put down all the server. Laravel is also pretty popular these days. I also don't see any reason to port it to something like Go (where community does not like frameworks - you can do everything with http library, they say). Then, we have JS, that sucks more than PHP, its popularity is bigger just because people are lazy and don't want to switch language context between backend/frontend.

Laravel is what makes PHP bearable, Go doesn't need Laravel.

We've already spent the last 10 years improving PHP - PHP doesn't suck these days. In fact every time I try a new language like Ruby, Python, Go, etc, I wonder why they're all so much more of a pain to work with than PHP/composer/nginx/Laravel. If you haven't tried Modern PHP/Laravel lately, give it a spin. You'll likely be pleasantly surprised.

Certainly there are many people doing great things with JS. But true is that JS is not the silver bullet that many JS developers and influencers try to picture. It's not hard to read/hear that JS don't impose language context switch, that it can work on both backend and frontend flawless, etc. Exactly painful to listen to and read as well. The ecosystem of paid services around JS has grown so much, but why? Because JS is just easy to create things or because dies it also introduce whole new challenges in such a way that developers have to look for ready solutions to things that become complex to create in-house? JS was born for the frontend and PHP for the backend. I've done things using JS on backend, Livewire (PHP) for frontend, but as much as I can, I separate things and absolutely prefer the language context switch.

Totally disagree

He needs to start chopping them up into shorts and then when you come across a short you like from an episode, you’ll convert over and watch the full thing. Good luck getting higher numbers in 2024.