The reputation loss is probably worse than whatever fine they end up paying
Time to pull a Meta/X and change name
The reputation loss is probably worse than whatever fine they end up paying
Time to pull a Meta/X and change name
Unfortunately some things will IMO always remain a natural monopoly. For example good luck trying to convince developers to write their apps for all those different operating systems.
Luckily Apple strictly controls the App Store and will never allow apps to abuse this, right? Right?
Your parent comment was mentioning the fact that their store still does not support user reviews, which should be one of the most basic features.
Epic chose not to try and compete with Steam on that front
Forget competing, they lack even the basics.
Where’s the punch?
In the face of everyone expecting an upgrade
To be fair trees still use energy for doing this, but that energy is conveniently provided by the sun.
High or low level doesn’t matter. Mathematically it just makes more sense to use 0-based indexing https://www.cs.utexas.edu/users/EWD/transcriptions/EWD08xx/EWD831.html
Can’t those be installed in toolbox?
Jokes on you, I subscribed to my mobile plan 8 years ago and I still pay 6€ for unlimited calls/sms and 30GB (Italy, Iliad)
Isn’t there already Box64/Box32? Not to mention most Linux software is already compiled for ARM thanks to being open source.
They used to, but they weren’t very good.
Metro UI toggle buttons were rectangular though.
GNOME devs never said that theming is incompatible (just “not supported”), and you’re still not explaining whay you mean with “incompatible” either. Managing window controls also doesn’t seem a requirement to be “compatible”, as the app still runs fine even with client side decorations (again, it just won’t fit visually with the rest of the system).
And by the way, the problem is not theming per-se, but the fact that apps get themed by default, they inevitably break by default, and app developers are left to deal with that. Nobody ever tried to improve the situation so the solution they came up with is to have their apps always look the same.
How about when the theming is baked in and impossible to change?
It can still be changed, it’s just a harder to do so.
It’s about doing things that go against the interests of the user.
This conveniently ignores that app developers are also users of ui frameworks, and they would like a well defined platform to test for, rather than an endless stream of distros each with its own theme that could break their app.
Libadwaita is only compatible with gnome and only works with gnome. Other DE’s can try to make it work in their DE, but the experience for them is hostile.
Not sure what you mean with “compatible”, as libadwaita apps are supposed to work on other DEs as well. It might not fit visually with them, but that’s not being incompatible.
TBF the report says this was done using credential stuffing, so it wasn’t really Roku’s fault.
Because Rust is not the only language that made this faulty assumption. It is an issue that affects Rust’s stdlib, just like it is an issue that affects Python’s stdlib and other libraries. In fact this was first reported as a vulnerability to yt-dlp (where it was actually exploitable) and then discovered it applied to many other libraries (where the exploitability is highly dependent on how the feature is used).
Rust here is only used as clickbait because of its aim to be “safe”, but its position is no different from other languages.
If you read the article from the researcher that discovered the vulnerability you’ll see they never call out Rust in particular, only as part of a list of languages that are affected. https://flatt.tech/research/posts/batbadbut-you-cant-securely-execute-commands-on-windows/
It’s also extremely unlikely that you’d be running a bat script with untrusted arguments on Windows.
It happens in yt-dl, which is where this was first reported https://github.com/yt-dlp/yt-dlp/security/advisories/GHSA-hjq6-52gw-2g7p
CEO bonuses should be awarded 10 years after their mandate