My surprise is that the tailwind creator could have a engineering team based in a css framework that basically was used for people that didn't knew real css. Is normal that this people now use other products more effective how AI for this task.

I know CSS and was quite sceptical about tailwind before I used it in anger.

I was going to write a longer response, but instead I keep reading your last sentence:

> Is normal that this people now use other products more effective how AI for this task.

I think it's too early to tell on that.

If you don't want learn ffmpeg syntax, is better use a visual gui how handbrake that a frontend for a fatty LLM.

I can understand problems with SSPL license, but i cannot understand the problems with AGPL. If you use software for your SAAS service for free, and made changes in it, you should share the changes with others. Is free software, not a gift for your business.

What?, apache have mpm_event since many years ago, you don't need prefork process model except if you want use mod_php or something not thread safe.

This website froze my phone, not joking.

Yeah, there's sort of a glitchy virus matrixy thing going on with the text as I scroll and it's really weird.

In 2005, i compiled linux kernel in 15 minutes on AMD Duron 700. Is true that was a very optimized kernel for my architecture, but i think that the typical kernel with all modules could get 1 hour or something.

Damn, thats pretty fast. Maybe I was doing something wrong in the config step?

not sure how much can really be done wrong, worst case would probably be an allyesconfig, which is huge, and while it was still big in 2010, it was considerably less so than now

GitLab with problems?, again?.

I think that the best name is "server for dummies".

As far as I know, all the projects that promote themselves as "serverless" are stateless functions and not designed to store states, which means if you want a database you will need to store it elsewhere and utilize it from the "serverless" container. So no DB for you out of the box if you want to use serverless architecture.

So I don't think it's for "dummies". Dummies want an all-in-one server.

> As far as I know, all the projects that promote themselves as "serverless" are stateless functions…

Any normal PHP app is just a collection of stateless functions, but that doesn't automatically make all PHP apps "serverless" apps. What makes something "serverless" is the FaaS[1] execution model.

[1] https://martinfowler.com/articles/serverless.html

Or, you know, it's better to reference the source: https://tools.ietf.org/html/draft-robinson-www-interface-00

Most PHP apps are run by DBs. They are not stateless.

Most "FaaS" apps also access a remote datastore as well. The fundamental value of most web software applications revolves around state transformation in some way or another. FaaS just "cleans up" the application state insofar as it forces the state boundary to a comparatively slow edge and doesn't let you, for example, store things in in-memory shared datastores.

in the past year or so i've seen serverless extended to anything where the underlying compute is abstracted away. so ex. bigquery and dynamodb, two very stateful services, are also described as serverless.

Do you compare assembler with SQL?

i guess that debian and gnome are preparing her nuclear reactors for execute gitlab, :P