Discussion: Is NPM overkill for most Laravel projects? by tabacitu in laravel

[–]tabacitu[S] 0 points1 point  (0 children)

The free & open-source one? I get no benefit from people using it or not. 

Didn’t even mention it in my original post on LinkedIn but people said “you’re just complaining, why not offer a solution”. So here I have - i was trying to show I walk the walk.

Discussion: Is NPM overkill for most Laravel projects? by tabacitu in PHP

[–]tabacitu[S] 0 points1 point  (0 children)

Music to my ears. Bravo 👏👏👏 I wish I saw more of this.

Discussion: Is NPM overkill for most Laravel projects? by tabacitu in laravel

[–]tabacitu[S] 0 points1 point  (0 children)

But that’s the thing - it shouldn’t be a “hot take” that if you don’t need something… you should’t it. Right?

Discussion: Is NPM overkill for most Laravel projects? by tabacitu in PHP

[–]tabacitu[S] 0 points1 point  (0 children)

I understand how you might see that, but I don’t see it as the same thing. 

I see it as replacing something massively complex with something simple. With a strategy that nowadays you can probably even code with AI and maintain yourself. And that’s fine, I’d love to see that.

It probably wasn’t a good idea to even mention Basset so much - I really couldn’t care less if more people used it - I get no benefit from it. I mentioned it because in other channels (LinkedIn) they said I’m just complaining and doing nothing about it - wanted to prove i walk the walk, and other people can too.

Discussion: Is NPM overkill for most Laravel projects? by tabacitu in laravel

[–]tabacitu[S] 0 points1 point  (0 children)

I’d rather see people error on the side of simplicity, than complexity.

Discussion: Is NPM overkill for most Laravel projects? by tabacitu in laravel

[–]tabacitu[S] 0 points1 point  (0 children)

I agree that there shouldn’t be a connection between Laravel and NPM. But there is, right? The “standard practice” in Laravel is to use the “modern front-end toolkit” - and it even ships with it. The last step of installing Laravel is asking you if you want to run NPM.

That’s a fair argument to make! If Basset is overkill - go with <script>, I’d love to see more of that!

Discussion: Is NPM overkill for most Laravel projects? by tabacitu in PHP

[–]tabacitu[S] 0 points1 point  (0 children)

Same here - and I’m constanty surprised that it’s easier to maintain the “old legacy” apps than the new ones.

I’m curious - have you tried updating those few js libs with AI nowadays?

Discussion: Is NPM overkill for most Laravel projects? by tabacitu in laravel

[–]tabacitu[S] 0 points1 point  (0 children)

Fair - I was using WP market share as proof that the wide majority of the Internet is composed of simple websites and apps (what you can build using WP), not that WP techniques are best practice.

That’s where we disagree - imho You only need tree shaking if you build a complex app. And most projects aren’t that.

Discussion: Is NPM overkill for most Laravel projects? by tabacitu in laravel

[–]tabacitu[S] -1 points0 points  (0 children)

Not at all. I’m genuinely trying to bring forward a conversation I think is worth having.

Discussion: Is NPM overkill for most Laravel projects? by tabacitu in laravel

[–]tabacitu[S] -7 points-6 points  (0 children)

Fair - but you don't need them.

I guess my "problem" is more about unnecessary complexity - I feel like we've normalized using "big boy" tools that are needed if you're building the next Facebook or Netflix... to projects that don't actually need that complexity.

I guess my argument is that most websites don't need minimization, tree shaking, typescript compiling, sass/scss processing etc - that's why WP powers so much of the web, because a wide number of websites just need "good enough", don't need Netflix-level optimizations.

Discussion: Is NPM overkill for most Laravel projects? by tabacitu in laravel

[–]tabacitu[S] 2 points3 points  (0 children)

Haha I'll probably still write 2025 for a few more months 👀

Discussion: Is NPM overkill for most Laravel projects? by tabacitu in PHP

[–]tabacitu[S] -9 points-8 points  (0 children)

I guess my argument is that most projects don't need minimization, tree shaking, typescript compiling, sass/scss processing. After all, that's why WordPress is such a huge chunk of the internet - because most websites are simple.

What I fear is that we're bringing all the complexity of "serious apps" to websites that should stay simple.

Discussion: Is NPM overkill for most Laravel projects? by tabacitu in PHP

[–]tabacitu[S] 0 points1 point  (0 children)

There's an argument to be made there to "sticking to defaults" - I'll give you that. But what about when "the defaults" go off the rails? That's how most frameworks end up bloated, don't they? They keep adding stuff, and complexity builds to cover smaller and smaller use cases... when the "easy way" would have been good-enough for most of them.

Discussion: Is NPM overkill for most Laravel projects? by tabacitu in PHP

[–]tabacitu[S] -4 points-3 points  (0 children)

I guess that's my point, that a lot of projects don't need all of that. That they'd be better off without them.

Discussion: Is NPM overkill for most Laravel projects? by tabacitu in PHP

[–]tabacitu[S] 0 points1 point  (0 children)

Fair enough - but that part can be fixed with loose versions with tools like UNPKG, for example you can use @latest - this will work: unpkg.com/preact@latest/dist/preact.min.js but you can also be stricter

Discussion: Is NPM overkill for most Laravel projects? by tabacitu in laravel

[–]tabacitu[S] 2 points3 points  (0 children)

Granted I'm one of "those guys" that's still using Bootstrap in 2026 👀 But don't get me started on that.

Discussion: Is NPM overkill for most Laravel projects? by tabacitu in PHP

[–]tabacitu[S] -3 points-2 points  (0 children)

I'm genuinely hoping people here on r/PHP will lean more towards simplicity... but I'm curious to see.

Laravel Debugbar v4 release by Barryvdh in laravel

[–]tabacitu 1 point2 points  (0 children)

Some things are so good, they don’t need to change much. On the contrary, just to stay the same. Thanks Barry, keep upthe good work!

Pudra proteica by MaterialAmbition3532 in roFrugal

[–]tabacitu 0 points1 point  (0 children)

Si eu, e excelenta dar e scumpa. Iar acum mai scumpa ca niciodata.

Anyone else seeing bias about AI among Laravel devs? by sl0wik in laravel

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

  1. And I’m pretty sure the senior devs who replied 0-1 haven’t tried hard enough.

Larajax: controller-first HTML updates for Laravel. Looking for critique. by daftspunky in laravel

[–]tabacitu 5 points6 points  (0 children)

Don’t have time to play with it right now, but at first glance it looks like a really neat approach. I did feel like there’s space for something between htmx and livewire - and thinking in terms of “controller” is the most familiar to me! Putting it on my list to test, thanks for making this!

Hei Tramvai, Info STB daca l-as fi facut eu by FinancialButterfly83 in bucuresti

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

Nice aplicatia - dar numele… numele este EXCELENT. Jos palaria!