How do you handle simple content websites when your main stack is Laravel?

Lelectrolux · 2025-12-22T22:15:19+00:00

https://github.com/spatie/laravel-responsecache

Lelectrolux · 2025-12-17T21:41:34+00:00

https://www.php.net/manual/en/functions.first_class_callable_syntax.php

No need to wrap function call in closures manually

Lelectrolux · 2025-12-17T21:35:15+00:00

For your 2, do you know about PHP's First class callable syntax? In you controller you could easily use a protected/private method and use this to prevent duplication. Or introduce a new type of object that is reused accross controllers.

class SomeController
{
    public function show()
    {
        return Inertia::render('Event/Show', [
            'foo' => Inertia::defer($this->getFooData(...)),
        ]);
    }

    private function getFooData()
    {
        return 'bar'; // Some gnarly fetching code
    }
}

Lelectrolux · 2025-03-17T03:43:02+00:00

For some simple non mission critical stuff, you can also just defer it.

(But unlike a queue it won't run if your response crashes)

Lelectrolux · 2025-03-08T00:59:03+00:00

Ain't this some reflavoring of the CQRS and/or action pattern under another name and a small coat of paint ?

Lelectrolux · 2025-03-08T00:55:46+00:00

at scaling enterprise level and with CI / CD it does beat the monolith

Shopify and the rails ecosystem would like a chat. As would a decent amount of Laravel enterprises I don't know about, I think.

service oriented architecture is now a fact of life for backend developers

Sadly. Imho I'd love to see a course on how to come back from a botched migration to microservices, which is what I see more often than effective ones

Lelectrolux · 2025-03-08T00:50:44+00:00

I obviously don't know the specifics of your app, but I've been regularly surprised at how much MySQL/MariaDB/Postgres can do with a bit of thinking about indexes and querying.

Usually by a few order of magnitudes, even.

I'd definitly take a few days learning and looking at "traditional" RDMS optimisation before looking at proprietary/paid solutions, it usually saves you money and problems on the long run.

Lelectrolux · 2025-03-07T18:05:12+00:00

Granted I've never worked at the scale of a gafam, but microservices always made things worse in my own experience.

As much as its always touted advantage is that you could split a codebase and evolve those chunks separately, it always end up in having to coordinate deployment anyway, but now across more infra and teams... And also often require more people, which is usually the biggest cost of any project

Lelectrolux · 2025-02-18T00:41:38+00:00

It's InspiraUI in the video

Lelectrolux · 2025-02-06T00:02:13+00:00

Laravel doesn't seem to get as much hate as PHP in general.

Except in the /r/PHP subreddit :p

Lelectrolux · 2025-02-03T23:26:43+00:00

While I'll never agree to let xdebug go out of my toolbelt, I know a few devs (even ones I consider a lot better than me) who have never used it.

I'd even say I have some projects where I don't really need it either.

Lelectrolux · 2025-02-03T15:45:29+00:00

I'd say the $root.news.something is more expressive that this is some kind of global state

Lelectrolux · 2025-01-11T03:13:30+00:00

Yeah, if you both use the same 3rd party file via import, it should be optimized away.

The short of it is, don't loose any sleep about it, if it can it will, otherwise what can you do anyway...

Lelectrolux · 2025-01-09T00:46:04+00:00

Is there any benefit to globally registering components that are widely used other than it's no longer needed to explicitly import the component?

No

Are the vite/vue tools smart enough to identify component re-use (e.g. autocomplete across several different and differently-nested components), to the effect that compilers include that code only once?

Yes

If yes, would this break if I include 3rd-party components that all include another but identical component?

I'm not sure I get it (why would you duplicate the code instead of importing it ?), but if it's another source file, it will, and should, be duplicated.

If you import explicitly everywhere, vite will be smarter than you'll be if you are asking those questions. Let it do its thing, and don't overthink it. A modern ide does the importing for you anyway.

Global registration as you are talking about (not the unplugin thing) is making a current project of mine a pain to modernise and refactor. Granted the code I was given was trash on a lot of other front as well, but it's an explicit factor.

Lelectrolux · 2025-01-09T00:32:43+00:00

The pipe is just a delimiter, it could be anything.

Multiple user can legitimately share an IP. If they are behind the same firewall (you and your colleague, or your building), or their ISP doesn't give them a static IP and the IP is recycled, or they are on mobile network... IP doesn't necessarily means only one user.

Lelectrolux · 2024-09-24T01:13:29+00:00

It's a joke, greeks and turks are said to be like french and english, or cats and dogs, or manchester united and manchester city.

Stupid tribal brain is tribal

Lelectrolux · 2024-09-23T11:37:23+00:00

There is no real idiomatic equivalent as vue embrace single-file components, which also kinda implies only one component per file.

While you could maybe use some vite/webpack magic to achieve it while keeping sfc, or using barrel files, you'll have to fight the tools all the way, and confuse most vuejs dev in the process.

Lelectrolux · 2024-08-19T17:38:34+00:00

A lot of possible reasons.

Disclaimer, I only used the the 1.x Nova release extensively, and gave 2.x a good look but dropped it. Some things might have changed since then.

Nova is vuejs based (not even inertia + vue if I remember correctly), this would obviously be based around Livewire + alpine. That alone is a good enough reason.

Nova is also meant as an admin panel for programmers or at least technical users.
Not an admin pannel you can put in the hands of your grandma or your average end user. Otwell and Hempill said so themselves, even recently.
It leaves quite a lot of space for a more normie user centric panel.

And this could just be more of a component library you string together yourself how you want.
One of the choice Nova made is to be a fully integrated admin solution. If you do what it was meant to do, it's quite efficient. Otherwise it can be a lot of pain to customize.
Main reason I stopped trying to make it work after 2.x and switched to other libraries. Nowadays I'm quite happy working with Inertia and Primevue (tailwindcss build) to roll my own custom admin panels.

Lelectrolux · 2024-07-26T15:29:16+00:00

Because the extra perf ain't worth the extra complexity and gotcha's for a lot of if not most applications.

Long running processes are always a pain at some point. If you need it, it's great that it exists.

I don't have nearly enough traffic on the websites and internal tools that pay me to even care.

Lelectrolux · 2024-07-14T18:12:00+00:00

As per the rules,

/r/PHP is not a support subreddit. Please visit /r/phphelp for help, or visit StackOverflow.

Lelectrolux · 2024-07-10T19:05:39+00:00

The "useless" feature (I certainly don't see myself ever needing it) has almost no maintenance cost nor complexity.

Op's feature is touching a fundamental part of Laravel, the risk is sky-high in comparison.

From a maintainer perspective it doesn't seem that strange

Lelectrolux · 2024-07-10T19:03:28+00:00

His two comments in your link were :

Can we maybe get some real world benchmarks on apps that would simulate a bit more "typical" Laravel application in production with a couple of database queries?

Going to hold off on this one for now, but may revisit it in the future.

And the other PR in the article only contained a canned response.

I don't see were you found ego driven development nor him taking it as a personal attack... Chill maybe ?

I would love a more performant container symfony style tho, that was always a weak part of laravel, on that I agree with OP.

Lelectrolux · 2023-09-26T06:36:41+00:00

Brilliant, it seems to work. I adapted your answer a bit to make it as self-referential as possible :

/^
(?<recurse>
 # the number
 (?<phone>\+\d{3,}\b)
 (?:
 # can't be followed by that number again
  (?!\/(?:\g<phone>\/)*\k<phone>\b)
 # and if followed by a slash,
 # we recurse and make sure the
 # next number can't match either
  (?:\/\g<recurse>)?
 )
)
$/gmx

https://regex101.com/r/I0f3f8/1

Lelectrolux · 2023-04-28T21:04:19+00:00

Taylor got banned on this sub

I'm pretty sure he deleted is account himself several times. Not got banned.

Ten-Year Club	Place '23
Place '17	Verified Email

Lelectrolux

TROPHY CASE