Meanwhile, .tech exists and is not country-specific but is far less popular for some reason.

Simple answer: length.

Two chars look a lot better than something with more chars, and all two chars TLD are ccTLDs.

But then it is the developers fault, never management

Yepp, and no one really listens to the others, just trying to remember what you did and make sure no one dumps more work on you.

Only issue I see is that the 8 chars required is very short and easy to brute force. You would hope that people would go for the recommended instead, but doubt it.

Sure, but even if they started tomorrow it would probably be years before it even could be considered experimental outside of the most daring early adaptors.

Having a combability layer is not ideal but it would mean they could have something worker for more users faster and at the same time see which modules/drivers they should focus on.

What I meant was that if you are returning 404 for example when a user doesn’t exist. You can’t tell if the user doesn’t exist or someone changed the API to remove the endpoint.

But forcing HTTP codes without a moment to think it through seems to be the new fad.

The clown, but flipped with a success field. If it is true then command succeeded, if it false something was wrong and there should be an error field as well.

HTTP codes should be used for the actual transport, not shoe-horned to fit the data. I know not everyone will agree with this, but we don’t have to.

Rounded corners tho… <shudder>

Just a small gif (as png didn’t exist/widely supported) that had the rounded corner. Then if someone wanted to change the color or background you would have to redo all the images. Fun fun.

And ethernet port!

“Thread closed due to inactivity.”

No, the main point of standing desk is that whoever has one talks about them all day, every day. At least, that was my experience 10-15 years ago, which was the last time I spent in an office.

And if it succesful, or at least passenger doesn’t boycott them over it, it is just a question of time until other airlines adds it as well

That is still source code, obfuscated but still source code.

Counting in lines of code is the most stupid metric.

It works quite fine, use it daily. Well, XMMS2 to be pedantic.

Just some shellscripts bound to windows-keys to pause/play and load new files.

The question is whether x86 is even relevant anymore

Also RISC-V, though that is probably a few years away at least.

That seems to be the general atmosphere, “leaving money”. They probably analysed it and thought it wasn’t worth the effort. Companies like to make money after all.

You still need to keep supporting it for future releases, make sure it actually works and not just builds, test, update QA pipeline, tell support, etc etc

You are getting downvoted by people that have no idea how software development and maintence works.

Every feature cost. More than most people realise. Both in development time and to maintain it over time and releases. It all adds up, not saying EA are correct in not supporting it. But to think it is free is just incorrect.

They made a business decision to not support it. We think it is the wrong decision, but it is ultimately theirs to make.

He could have handled it better. But he didn’t call the code crap directly, just the bundle of everything.

Having a meta package and let users choose seems like the best way. But this is a Debian issue, and not a keepassxc issue. It is up to Debian to package it anyway they want.