It's as dumb as the german Pauschalabgabe, where everyone is forced to pay a specific amount of money for technical devices, because there is the possibility of private copies for licenced media.

https://de.wikipedia.org/wiki/Pauschalabgabe

I have some apps that works from 5.3 to 8.5. php has great compatibility, if you don't rely on external libraries or framework and don't use types.

For PHP 8.5 code to work with PHP 5.3 you'd have to forego short array syntax, finally blocks, scalar type hints and nullable types (OK, you mention this), the ?? operator, the ?-> operator, traits, and probably a million other things that we use every day.

For PHP 5.3 code to work on PHP 8+ you'd have had to completely forego error catching because that was completely upended in 7.0 or 7.2 (I forget which), not used short open tags, never used the class name as a constructor (that happened a lot in PHP 5), have no mcrypt functions, not used __autoload(), have had the foresight to use PDO instead of mysql_ (was PDO available in 5.3? I'd never seen it that early I think), you'd have had to be fortunate enough to not used ereg_, I think that older versions used # in ini file comments (I remember that breaking at some point, don't remember when), never used each(), not used safe_mode for mysql (strange because that was the default I think), and probably a million other issues that I hadn't encountered. If you have codebase written for PHP 5.3 that still works on modern PHP, I'd love to see it. I honestly don't believe such a codebase exists beyond the most trivial.

Most of the apps where developed for php 5.2-5.3 , as many things that you wrote where already bad code in this time. Spl autoloader, MySQLi, __construct was already available.

The apps are internal legacy apps so I can't share the codebase.

Because of this there was no big rewrite like types etc.

> Videos take forever to get to the point.

I feel the same with this article.

Everything gets much easier without windows, but many people feel a sense of security with windows.

I also prefer a flight without get a feeling of a flying can.

It also helps passengers on long flights experience the passage of time as something other than number go up

another solution: https://www.theliquidview.com/

Is that just a TV with a fancy bezel that plays a 24-hour video? $10K seems a lot to drop on something so mundane.

If this meant more space and bigger seats due to reduced costs of the plane, sign me up.

If history is any indication, it would only mean more passengers in the plane.

I think it's ok, that there is a warning on a parody site than looks like Google.

This is a full block not a warning in any conventional sense of the word, and it resembles Google but it very clearly says "Foogle" so it's not pretending to be Google, and no email or anything at all is asked from the user, so yeah it's just plain abuse of their power and very little space to argument that they are just being "overly cautious", but just like abuses by the state or the police there is always people in favor of such abuses in the name of safety.

And it get worse, as they are changing the max days to until 47 in 2029.

On the other hand, as the time gets shorter, it'll become less likely that something will go undetected for a long time.

The site is for developers and most of the rare species are developers.

The designer fail to target their audience.

Ruby is not targeting those kind of developers though.

It's C/C++ developers that typically prefer a no-fluff approach.

As polyglot developer, I am also for a no-fluff approach and vanilajs for the win.

One of the reasons Next.js is attractive to me, is exactly they have rediscovered why so many of us have stayed with SSR.

> no-fluff … Next.js

Hmm. We can agree to disagree on the definition of fluff.

Sure, if you ignore the SSR and SSG part, which sadly most nodejs stuff lacks.

Additionally, Next.js should only be used when SaaS product vendor doesn't allow for any other option, which sadly is the case when making themselves sellable to magpie developers, while riding VC money until the IPO takes off.

I rather deliver, than do yak shaving, but at least can deliver only HTML and CSS if I chose to.

Then why we pay a fix price for everything, size of repositories, webhooks etc, except the self hosted actions.

No one stop you to backport kde to x11. It's honestly tiring how the people force open source developer to support something.

"For enterprise support and actively maintained versions, please see MinIO AIStor."

Commercial only, they will replace the agpl contributions from external people. (Or at least they will say that)

It's worth noting their enterprise support is a joke. As is their whole pivot to "AI." Their pitch is that they are an AI company now. Good riddance. I look forward to a good community fork.

I don't understand. They've seen the contributions. How can they possibly do a clean-room implementation to avoid copyright infringement? (Let alone how tangled up in the history of the codebase they must be...)

I hope some contributors get together and sue. ;)

It doesnt matter unless someone takes them to court over it.