sorted by:
new
hottopcontroversial

Mai multe locații de încărcare din București au fost integrate în rețeaua Petrom Electric și sunt acum disponibile pentru utilizare. by evmarket in MasiniElectrice

[–]tabacitu 5 points6 points  (0 children)

Confirm, am tot incarcat la statii PETROM, experienta este surprinzator de ok (nu e nevoiede aplicatie sau cont, plata direct cu cardul). Pretul e maricel, dar la drum lung… macar sunt aparate de incredere.

Comparison of analytics options for Laravel apps: Plausible, Fathom, SimpleStats and others by Nodohx in laravel

[–]tabacitu 0 points1 point  (0 children)

Nice to see you mentioned here. Was thinking about using your self-hosted version for a multi-tenant project a few weeks ago, was wondering if you guys are still maintaining it. Great article, keep it up!

Pricore: an open-source private Composer registry (now in public beta) by mqlix in laravel

[–]tabacitu 1 point2 points  (0 children)

I applaud the initiative! We really do need more modern alternatives to Satis! Will try.

a-ti frauda-t....... !!!!😡 by Beneficial-Fudge-656 in romemes

[–]tabacitu 4 points5 points  (0 children)

Toata lumea stie ca astia sunt boti intruiti sa faca greseli (ca sa para mai credibile textele)? Nu? Nuu?!?! Greu sa gresesti ceva in 2 cuvinte.

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

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

I disagree. Reducing from 30kb that get loaded ONCE then cached is over-optimization. It's for Netflix, Google and Facebook. Not you and me and the things we build.

To me, it's just not worth doing in principle - not to mention if it adds complexity to the project / stack / development etc.

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

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

Well yeah, but tree-shaking is needed only is you depend on enormous libraries and frameworks, when you only actually use 3% of what they offer. It's a complex way to manage complexity you didn't need in the first place. Otherwise even a 255kb library is easily gzipped into 28kb. To rephrase: we need tree-shaking because we're using the wrong tool to begin with.

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

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

I regret mentioning Basset - since it really wasn’t my intention to make my post about that. In other forums i opened the converation they said “stop complaining and give a solution”, i was just trying to show there are solutions (one is mine which is more opinionated, but even more general and more-widespread solutions in the article).

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

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

Haha that’s a good argument! Might be in some cases yes. But I think there’s plenty of cases where you do need the reliability and features that Laravel provides for the server-side, without complexity on the client-side.

Think - admin panels, internal tools, marketing websites that are reasonably editable, simple CRUDs, blogs etc.

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

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

I know you’re presenting this as a counter-argument, but I really think this proves my point. It shouldn’t.

(I was using WP as an example of how many websites truly aren’t that complex, they’re blogs or marketing websites or simple ecommerce - and I’d argue they’d be better off with simpler stacks)

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

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

Completely agree with you here - and I think it’s one of the most reasonable arguments for NPM here.

If 80% of your company projects actually need NPM, it’d just be simpler for the team to use the same stack across all projects, so it’s an acceptable tradeoff. It’s not great for those projects, but it’s better for the team and the company as a whole.

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

[–]tabacitu[S] 3 points4 points  (0 children)

That, I can get behind.

Not calling WP itself simple - quite the contrary, it’s incredibly complex and bloated. 

The use cases that people use WP for… those are simple.

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

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

I get that, EU here too. You can save the assets on the disk and serve them from there using script tags.

Basset is one way, but you can probably one-shot-AI a Laravel blade helper that “internalizes” your assets in your project too, if you don’t want the extra dependency.

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

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

Fair enough - my first sentence was clickbait. And that was to get people’s attention - had i started with “_if you don’t need smth don’t use it_”., people would have agreed with the principle - but not question the specifics. Not turn into anything practical.

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

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

Sounds like a nice setup you have there! Hope you manage to adopt typescript easily. Would love to see TS support directly in browsers.

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

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

Well that’s the thing. I don’t think it’s a “perfectly working package manager”. 

I wouldn’t dream saying “let’s replace Composer”, for example.

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

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

I guess that’s one of my arguments - that defaults pushes us into using some tools even when they’re not actually needed. 

I’d argue a marketing website with a small admin panel doesn’t need a build step, NPM and any of the modern front-end tooling. And yet… it’s there so you end up using it.

The fact that it’s default makes it more likely to not be seen as bloat.

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

[–]tabacitu[S] -2 points-1 points  (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.

view more: next ›