A lot of the problems we have now with XOrg simply didn't exist when it was first written. It's an incredibly old protocol and that shows in places where technology and/or common use cases have evolved in directions that expose these previously unknown weaknesses.
No support for variable refresh rate for example isn't a problem when games don't even hit 60 fps and the most common use case was spreadsheets.
Knowing some of the fucks in the EU parliament it certainly won't stop them from trying. It is very reassuring to know that the courts are aware of what fuckery some of the politicians are trying to pull and are actively moving to prevent the abuse from happening.
I still fail to see how comparing an AM5 chip is in any way shape or form a good addition for discussing an objectively terrible review of a late addition the AM4 product family. What you say might be true... for AM5. Which is not the subject of the review everyone is talking about. Nor is anybody except you talking about what X3D currently offers, we're all talking about a review that, at the time it was written, was horribly researched, full of bias and false facts.
You coming in and suddenly talking about the 7950X/X3D adds nothing of value to the topic at hand. Because the topic at hand isn't "Is X3D worth it" it's specifically "look at how badly Userbenchark twisted this 5800X3D review".
I suspect they skipped checking who controls that domain at the time and just saw that it would make for a good name. Not good practice but I can see how that happened.
The only shame here is that there is no way for an instance to "prove" it is the successor to a defunct domain.
Digital Only with Proprietary DRM making sure you need to use their Official App (which will never work the way you want it to) in order to read the rented Files.
Offline Access only included in the Premium Plan (50% markup) and will be buggy for the first 4 years, occasionally not actually allowing you to access the files because the DRM bugged out.
The way this reads I think the company did not actually provide a good sandboxed environemt. So when they rm -rf /'d the thing they actually deleted a lot of stuff the recruiters still needed (likely the pentest environments for other candidates). Because imo that's the only reason I can think of to just outright ban a candidate from applying for any other role at the company.
I'm afraid Unbrexiting would just make this a whole lot worse.
In a Brexit environment at least everyone can eventually agree to just ignore the UK's outlandish laws. If they were still in the EU that would be almost impossible. Plus they would likely try to push this bullshit into EU policies as well (not like parts of the rest of the EU aren't doing that already)
The developer working on federation plans to merge the changes into forgejo first and then from there into gitea but I'm not sure in how far the recent changes to gitea's CLA have affected those plans.
Forgejo is a drop in replacement (they are committed to keeping it that way for as long as possible) so, as far as I know, simply changing the gitea image to the forgejo image is all you would need to do.
They did start a cloud service for hosting Gitea which introduces a direct incentive for them to make Gitea less hosting friendly by, for example, making newly added configuration options less comfortable to set up. And more recently some changes to code contributions that are not exactly community friendly (as a result forgejo will be unable to upstream some of their changes)
What lead to Forgejo, as far as I am aware, was less a problem that is already there and more the set of problems that have a very high chance of eventually manifesting, at which point forking the project would be too late.
My very honest opinion is that Raspberry Pi's should be for consumers only. They should not be a product enterprises use. They were originally a cheap and affordable solution to hobbyists needs of getting some minimal amount of compute power in a very limited space. They were not thought up to be bought by the dozens, almost hundreds, for corporations who cram them into a cluster and make a server out of it (I have seen that at my workplace).
Much like there are corporate only products imo there should be consumer only products and Raspberry Pi's should have very firmly made an effort to stay a consumer only product.
And even in the current situation, yeah they should have prioritized hobbyists. Businesses making themselves reliant on one single irreplaceable part from one single manufacturer in their supply chain have no one to blame but themselves when it comes back to bite them in the ass. That kind of setup is bad business no matter how you look at it and should not exist past a prototype stage unless you're in the business of gambling.
Nope they explicitly state in their support forums that they do not support Firefox and the Error Message you get recommends using Edge or Chrome. This is not an Ad-Block problem
Example: The meeting webservice my bank uses is for whatever reason blocked for Firefox. Not sure if they just User-Agent check but they consciously block out Firefox users. I alerted my bank person about that but I doubt that's going to be any different next time I have a meeting with them.
It's what happens when the devs have to spend more time making sure the DRM works than actually improving the UX of the platform. Pirates/Non-DRM users don't have that problem hence small FOSS projects can outclass big Streaming Services in UX quality.
Neshura @ neshura @bookwormstory.social Posts 3Comments 508Joined 2 yr. ago
A lot of the problems we have now with XOrg simply didn't exist when it was first written. It's an incredibly old protocol and that shows in places where technology and/or common use cases have evolved in directions that expose these previously unknown weaknesses.
No support for variable refresh rate for example isn't a problem when games don't even hit 60 fps and the most common use case was spreadsheets.