As someone who benefits greatly from serverless at a company I started I have to agree on the whole.
I love JS/TS, I really do. I love the syntax, I love almost everything about it. Packaging and commonJS vs ESM are the worst. It feels like black magic and problems take me a long time to fix. In the end I’m not always clear on why there was a problem in the first place.
I use raw PHP at my $dayJob (and have for almost a decade, well I used CakePHP and Laravel at other jobs) and I’ve got to say PHP can be pretty great. Most my annoyance with it comes from specific historical decisions the company (or I) made and not the language itself. Laravel provides a very nice layer on top of the crufty parts of PHP and while it sometimes over-complicates or over-abstracts things I do really like Laravel.
There just are less things in PHP that are “show stoppers”. I hope that things like Deno make wiring the language I love, TS, easier and less of a pain in the long run but today PHP is easier.
Sharing code with the front/backend is really nice in TS and only thinking in 1 language is great. Also serverless, for all it’a downsides, has one major upside: I don’t have to think about scaling almost at all. I know that’s not 100% correct but it gives me a massive peace of mind. My business is very spikey/bursty and so this matters a lot to me. Cold starts suck but once you get going it’s great. Also using Lambdas as “glue” for queue or just little self contained bits of logic does feel like magic. We use it at my $dayJob for things that we need to scale at a moments notice and it works like a charm.
I know you can run Laravel on Lambda but I do feel strongly that it’s not the right move to force a monolith into a Lambda (see also Express). I think serverless requires a custom/no framework because it’s just very different from normal deployments.
I love JS/TS, I really do. I love the syntax, I love almost everything about it. Packaging and commonJS vs ESM are the worst. It feels like black magic and problems take me a long time to fix. In the end I’m not always clear on why there was a problem in the first place.
I use raw PHP at my $dayJob (and have for almost a decade, well I used CakePHP and Laravel at other jobs) and I’ve got to say PHP can be pretty great. Most my annoyance with it comes from specific historical decisions the company (or I) made and not the language itself. Laravel provides a very nice layer on top of the crufty parts of PHP and while it sometimes over-complicates or over-abstracts things I do really like Laravel.
There just are less things in PHP that are “show stoppers”. I hope that things like Deno make wiring the language I love, TS, easier and less of a pain in the long run but today PHP is easier.
Sharing code with the front/backend is really nice in TS and only thinking in 1 language is great. Also serverless, for all it’a downsides, has one major upside: I don’t have to think about scaling almost at all. I know that’s not 100% correct but it gives me a massive peace of mind. My business is very spikey/bursty and so this matters a lot to me. Cold starts suck but once you get going it’s great. Also using Lambdas as “glue” for queue or just little self contained bits of logic does feel like magic. We use it at my $dayJob for things that we need to scale at a moments notice and it works like a charm.
I know you can run Laravel on Lambda but I do feel strongly that it’s not the right move to force a monolith into a Lambda (see also Express). I think serverless requires a custom/no framework because it’s just very different from normal deployments.