Yeah, because of the ASICs built into them to enable that decoding.
Without that, a 4K HEVC video is in upwards of 100+ billion operations/s to decode on the CPU. Which limits you to high end CPUs getting capped out on something you essentially get for “free” otherwise
This isn’t tech news, go post your Elon spam somewhere else
Almost nothing you mentioned here has to do with accessibility and accessibility tooling.
I get the feeling that most of the people replying here and downvoting the folks that are right don’t actually know what accessibility means.
Which… Honestly tracks. If the community in general doesn’t actually understand what accessibility is of course the projects themselves aren’t going to give a shit about accessibility.
And the Linux community, par for the course, shits on anyone who has real critical feedback.
It’s not about being better than everything else.
It’s about literally maintaining the same capabilities that it had before that don’t alienate an entire class of users. And taking into consideration how dropping centralized APIs and ecosystem fragmentation affects users.
Accessibility apis are non-optional for accessibility tools that many individuals require in order to use their device effectively.
That’s a pretty big difference from what you seem to be thinking. We’re not talking about how the user interface looks here.
I mean if you rely on accessibility apis you’re not going to use it because it’s not there… You literally cannot use the OS because you require accessibility tools to use your computer effectively.
And implying that someone should just make it their own is kind of asinine. This is a big shift in the Linux Desktop ecosystem that one person cannot affect when decisions have already been made and contributions that go against project decisions are not necessarily welcome.
Developers of large accessibility projects slowly dropping Linux support because of Wayland Is a Wayland problem, not a “devs of accessibility tools problem”.
They are already vocal about it, to frustratingly no effect.
Accessibility apis on Windows and Mac actually work and are actually consistent.
They’re only consistent across Linux Desktop environments if you are using X11. Wayland kills that
I think most of the commenters that are replying to me or completely missing this point
I’m confused as to what this is.
You have a PAAS project like Coolify, that’s rather obvious. It tries to provide abstractions and automations for common platform scenarios, which is what the As A Service part is.
What is Dokku abstracting and automating that makes it a PAAS?
I’m probably missing something here.
Too bad Linux completely abandoned accessibility with Wayland by putting accessibility API implementations up to the distros. Which, by far, don’t. And when they do it’s fragmented as fuck.
Making Linux an absolute no go for anyone that needs accessibility tools like Talon, which does work on X11 APIs. Since those were actually consistent.
Not a single one of the robot vacuums that I’ve bought in the last 2 years seem to be able to function without internet access.
It’s asinine.
Also they break down so freaking fast. It’s not even funny. Even worse when the part that’s broken is non-replaceable and it’s like a $3 part.
What you say is true.
It’s not a product that you pay for or product that is sold. It is a product that is provided for free. However, that product can no longer be provided for free because Mozilla doesn’t profit off of you using their free product.
Mozilla (the non profit) actually doesn’t aim to profit at all. They aim to support the ongoing development of Firefox and similar projects. Which is currently under risk of not having the necessary funding to pay engineers to build and maintain it.
Mozilla needs more money so that they are not under the risk of sudden collapse if they stop getting money from Daddy Google.
Honestly, it’s a shitty situation to be in. As the grand majority of users don’t understand just how involved browser development is. And those users instead donate to projects that are either forks of Firefox (and directly depend on Mozillas investment) or are (at this stage) toys, like Ladybird.
Which leaves a slim set of choices for the continued funding of the project. All of which it’s core user base hates (Market trend following, new features to see what sticks, AI related integrations, ads, subscription services…etc)
Yet it’s core user base isn’t willing to donate so it’s kind of a self-caused problem.
Side note. IIRC the foundation’s highest paid executive employees make about what a senior engineer at Netflix makes. To put that into perspective.
I mean, technically correct?
People use the term wrong, but people who are ruled by emotion and not facts hate to think things through rationally. Which is the majority of everyone.
Firefox is a commercial product. Is it not?
They need to make money so that they can fund hundreds of engineers salaries to keep building it and maintaining web standards operability.
And somehow do this while keeping off with Chrome who has a team 4-5x their size.
Trying to figure out a way to be independent of Google while competing with Google is a tough nut to crack. If they can’t sell it and they can’t get enough donations, then then it comes down to partnerships and advertising.
Then donate!
They are in this situation because they have to keep up with chrome’s capabilities _ velocity with a team that’s 1/4 the size at best.
Essentially they have to produce more with less and they have a funding problem. Almost all of their funding goes into software engineering salaries.
At the risk of not being able to keep up and becoming an obsolete web browser leaving Chrome as the only dominant one there is a shitty position of being the bad guy so that you can get money.
In short, I sympathize with the reasons why they are having to do this even if I greatly dislike them. Reality is complicated.
Wayyyyyyy lesser.
We’re talking Mussolini versus your local grocery store clerk who’s a dick sometimes.
Fuck…
I’m so sorry 😞
That’s brutal. I love my cats and I feel like crying for you…
FR.
You don’t get rewarded for good, fast, or high impact work anymore.
Why do it at all them?
Doesn’t matter because the Democrats caved so all of this was for naught and all this leverage is now gone.
The pr was getting terrible for Donnie and his party, the slide was getting steeper.
To other companies?
There is a lot movement opportunity for experienced developers still.
That is parallelized… I didn’t make mention of threading being the concern here.
The 100+ billion operations per second isn’t exactly easy.
4k 60fps = 498 million pixels per second
Each pixel takes a couple hundred logical operations with HEVC.
A modern high end 4GHz, 8 physical core CPU at 4 instructions per cycle, at maximum capacity, can handle 128 billion operations per second.
You probably wouldn’t even get your realtime framerate in this scenario.