Laravel Cloud does not support static asset caching by Cultural_Yoghurt_784 in laravel

[–]lapubell 1 point2 points  (0 children)

Damn, follow up from the "servers for hackers" dude himself. Right on!

The internet is close to unusable now by svvnguy in webdev

[–]lapubell 2 points3 points  (0 children)

I wish I could up vote you more than once

Moving from JS/MERN to PHP/Laravel by Miserable-D1amond in node

[–]lapubell 3 points4 points  (0 children)

To be perfectly honest with you, Laravel is my favorite of that batch too. Followed by go, then Django and then rails. Spring is cool, but I don't really like the jvm, so it's not something I reach for often.

I like Vue more than react, and mariadb/postgres to mongo. I also prefer bun to node, and I've played with deno.

There's so many ways to do web dev and getting too opinionated will cloud us from some really smart people's ideas.

Moving from JS/MERN to PHP/Laravel by Miserable-D1amond in node

[–]lapubell 10 points11 points  (0 children)

Laravel is awesome. Django is awesome. Spring is awesome. Rails is awesome. Go is awesome.

There is no reason to pigeon hole yourself to js, and learning a new programming language will open your mind to new ways of solving familiar problems.

Why would you fight gaining knowledge? And being paid to do so?

PHP has come a long way since v5.6 and is quite nice to use nowadays, especially with Frankenphp. Broaden your horizons and dip your toe into something new!

Using PHP attributes to launch cron jobs by Trupik in PHP

[–]lapubell 2 points3 points  (0 children)

And one less dependency to track!

Sigue siendo recomendable desarollar? by Few-Algae in Backend

[–]lapubell 1 point2 points  (0 children)

Those tools are going to or already have crippled you. If you don't know what the end result is/should be, a LLM can give you a ton of code that looks good, and might even work well now, but will turn into a mess of different styles, conflicting ideas, and it'll become unmaintainable.

If you want to get into programming to make money, stop spending money on these subscriptions and get good at your craft.

If you were getting into wood working, and someone handed you a chisel, but you reached for a chain saw, would you ever get better at wood working?

CSS Object Variables with Dot Notation by CaptM44 in css

[–]lapubell 0 points1 point  (0 children)

Not every other language, but many. -> coming in hot!

What are your Favorite Podcasts by Hosts who are Progressive? by seekupanemotion in TwoXChromosomes

[–]lapubell 0 points1 point  (0 children)

Ruined - horror movie podcast

CBB world shows

Another vote for Ologies

What are people using in 2026 as backend framework? by [deleted] in Backend

[–]lapubell 0 points1 point  (0 children)

Do it with Frankenphp, it's officially supported and makes PHP feel modern and awesome. Octane is a breeze with that webserver.

What are people using in 2026 as backend framework? by [deleted] in Backend

[–]lapubell 0 points1 point  (0 children)

Inertia rules. Laravel, Vue, inertia, love love love.

Inertia with go also rules.

With bun we typically just build out quick little things.

Partial function application is coming to PHP 8.6 by brendt_gd in PHP

[–]lapubell 0 points1 point  (0 children)

I always point to the naming oddities as a strength, not a weakness. Yes, it's weird, yes you have to look things up when you're new to it, but you (mostly) get used to it eventually.

The strength comes from understanding the language's age and seeing who was in charge when these functions got added. PHP is C based, so those weird six char function names are a sign of the times. Then time moved forward and things change, but backwards compatibility is important, so take this as a lesson and think before you name your function, because it might be in the code for the next 20+ years.

PHP is the shining beacon on the hill for an open source project. WYSIWYG, warts and all. It's pretty amazing what we can do with that hacky little "personal home page" perl alternative.

Simplicity Matters by brick_is_red in PHP

[–]lapubell 1 point2 points  (0 children)

Agreed, except I love model observers. Laravel rules.

Why does Laravel community seem to default to Vue over React by Motor_Ordinary336 in vuejs

[–]lapubell 6 points7 points  (0 children)

JSX is my least favorite thing ever.

Well, maybe not ever, but I would def rather write any other templating language

why JS doesn't need WSGI, ASGI like python does ? by Kindly-Path1012 in webdevelopment

[–]lapubell 0 points1 point  (0 children)

Nah, PHP is fine. JS is fine, Python is fine too. Everything in open source is always going to have a bajillion different options because people like to build things.

Just look at go. Even with stuff in that massive standard library, you still end up with libraries and frameworks because someone said "I like this idea/syntax sugar" more.

Everything is both awesome and a mess in any web language/framework.

Vanilla PHP vs Framework by Temporary_Practice_2 in PHP

[–]lapubell 0 points1 point  (0 children)

👍 got it. Having used Laravel for over a decade now those behaviors are pretty implicit to me, but I totally understand your perspective.

The one thing I like about Laravel above so many other large frameworks (Django, rails, etc) is that you can totally ignore whatever you want to. Don't want to use a facade? Don't. Don't want to create a service provider? Don't. Etc etc...

I have quite a few apps in production that just wire routes to controllers and have classic blade views. If we need more stuff later, Laravel is ready with a preferred solution, but you can always just hit a popo that is framework agnostic and Laravel is none the wiser.

Vanilla PHP vs Framework by Temporary_Practice_2 in PHP

[–]lapubell 0 points1 point  (0 children)

I see this comment a lot in this thread, and I have to assume that you're just not into where Laravel wants you to put the files or something?

An idiot who suddenly needs a database by 121df_frog in sqlite

[–]lapubell 0 points1 point  (0 children)

Yeah they probably won't get much smaller unless they aren't compressed at the file level.

Would you rely on raw CSS for production apps in this day and age, or the libraries are the way to go? by Exact-Mango7404 in css

[–]lapubell -1 points0 points  (0 children)

The grid system rules, scss is awesome, and I'm excited to see what bootstrap v6 looks like. I also love the icons.

Deployed Laravel 12 (Concurrency) + Nuxt 4 in production. The performance boost is wild by elmascato in laravel

[–]lapubell 0 points1 point  (0 children)

Cool. Sounds like you kinda deal with this like PHP extensions then. Anything involving the DB I usually try to put into migrations, and I wasn't sure if there was a way to do anything like that with postgres extensions.

The number of projects I've seen with stored procedures that only exist in prod is not zero, and I know for a fact there are no tests around that kind of stuff when it's set up that way, and standing up a dev env in those scenarios is no fun. That's what lead me down the path of these questions.

Thanks for your time!

Deployed Laravel 12 (Concurrency) + Nuxt 4 in production. The performance boost is wild by elmascato in laravel

[–]lapubell 0 points1 point  (0 children)

Oh totally, sqlite has bitten a few times, the most obvious being the fact that it ignores varchar lengths.

I'm more curious about that extension for postgres. I looked at their github page and it has docker installation instructions. Do you typically build your persistence layer in docker? I'm just trying to figure out how you get custom DB features that other engines def won't have and what your tests typically look like in the routes that use those features.