The problem was named after an incident in 1996 in which AOL's profanity filter prevented residents of the town of Scunthorpe, North Lincolnshire, England, from creating accounts with AOL, because the town's name contains the substring "cunt".

haha

A strength of the GPL is that the community can fork projects, and "take them over" that way.

At the same time, and this instance is such a case, on a centralized platform, projects can be taken over instead of be forked.

They developed and published a plugin. Now it's been taken over by someone else, on the primary distribution and discovery platform, and they have no control over it. Worse than that, the takeover now offers their sold functionalities for free.

This makes the "open source but not free, but after two years true FOSS licensed" licenses look very useful if not necessary for businesses and developers that want to monetize. At the very least when they [have to] use centralized platforms.

The EU passed laws that require companies (under conditions) to ensure base requirements in their supply chain.

I think a digital equivalent could be possible and similar. Requiring reasonable security and sustainability assessment.

It's not very obvious or simple to enforce, but would set requirements, and open up opportunities for fines and prosecution.

Hahahahahahahahahahaha

(Pause for breath)

Hahahahahahahahahahaha

Was that tone really necessary? I would have liked your comment more without this part.

I did a bunch of other experiments, which didn't make things faster:

Also particularly interesting what didn't work.

Is that the case at CrowdStrike?

costumer

Sounds to me like the AI was programming using you instead of the other way around.

Did you copy and paste back and forth without learning or understanding anything? Or did you read and assess the results, and try to understand errors and issues?

I would have expected that at least all the frameworks were using the same database, but no. Some frameworks use MySQL, others use PostgreSQL. Some framework implementations are ultra-optimized and others are what you would expect in your average web application. Some frameworks are using proper templating libraries, others are using Sprintf.

The term engineering is not about problem-solving, especially when differentiated from development. Engineering is about deliberate understanding and decision-making, about giving it an architecture, a structure.

You can develop without any structure, solving an issue, without understanding a bigger context or picture or behavior. But that's not engineering.

I think the guideline should be: future software should be written on a whim

I hate popovers. This one not only covers the whole screen, it opens the virtual keyboard because of auto focus. So people actually subscribe like that? I don't. I leave.