News for hackers. Stuff that matters.
Re:Laravel Cloud by slt2021 on Monday February 24, 2025 @11:55AM (#43161789)
think from a perspective of laravel developer: your customer pays for delivered features, not for platform engineering/SRE/devops type of stuff
Re:Laravel Cloud by ZYbCRq22HbJ2y7 on Monday February 24, 2025 @12:09PM (#43162010)
You don't think your customers are paying for performance and uptime?
Re:Laravel Cloud by slt2021 on Monday February 24, 2025 @12:13PM (#43162073)
I think a lot of customers take it for granted and expect stuff to "just work". If they pay for laravel site - they expect it to work, and don't expect to pay for keeping stuff running for the stuff they paid already (feature development + cloud bill)
Re:Laravel Cloud by wavemode on Monday February 24, 2025 @12:29PM (#43162286)
To be frank - no. Systems with horrendous performance and uptime still tend to sell perfectly well. Especially when your customers are enterprise users.
Re:Laravel Cloud by osigurdson on Monday February 24, 2025 @01:58PM (#43163394)
It is kind of an odd chasm. Users care about and pay for pixels. Sometimes decision makers care about underlying technologies as they don't actually interact with the pixels (e.g. SAP).

I also think that not caring at all about the underlying stuff (particularly if approached from a standpoint of arrogance) can cause you to miss important inflection points that might make a huge difference. Of course, the opposite (e.g. arrogantly not caring about the pixels) is probably worse.

Re:Laravel Cloud by znpy on Monday February 24, 2025 @02:15PM (#43163647)
> It is kind of an odd chasm.

It not an odd chasm, it's a wrong (and fake) chasm.

If you bring in a bit of (proper) engineering and some common sense it's easy to determine there's a threshold under which it makes sense to pay a PAAS and above which it makes sense to pay an SRE and look at managing infrastructure yourself.

Engineering is not a matter of what side to pick and what belief-system to adopt. Engineering is essentially all about trade-offs.

Re:Laravel Cloud by osigurdson on Thursday February 27, 2025 @08:47AM (#43194315)
>> your customer pays for delivered features

I was responding to this comment in a general sense, not weather or not to use managed services.

Re:Laravel Cloud by wesselbindt on Monday February 24, 2025 @02:37PM (#43163917)
Well no, but chuck your app in a container and you've got something that'll run just fine on ec2 or a dozen other language agnostic platforms. What is the value add of restricting the framework you can use for your app?
Re:Laravel Cloud by ahofmann on Monday February 24, 2025 @04:16PM (#43165022)
The "chuck your app in a container" is doing some very, very heavy lifting here. Deployment of a full blown laravel app isn't three lines of docker config.
Re:Laravel Cloud by wesselbindt on Monday February 24, 2025 @06:05PM (#43166015)
I admit, I actually don't know much about the php ecosystem. I just extrapolated what I know about the python web app ecosystem, and that's probably not entirely fair.