In the fall/winter in northern areas it’s free! (Money that would already be spent on heating).
Summer is a negative though, as air conditioning needs to keep up. But the additional cost is ~1/3rd the heat output for most ACs (100w of heat require < 30w of refrigeration losses to move)
I want to reduce wasteful power consumption.
But I also desire ECC for stability and data corruption avoidance, and hardware redundancy for failures (Which have actually happened!!)
Begrudgingly I’m using dell rack mount servers. For the most part they work really well, stupid easy to service, unified remote management, lotssss of room for memory, thick PCIe lane counts, stupid cheap 2nd hand RAM, and stable.
But they waste ~100 watts of power per device though… That stuff ads up, even if we have incredibly cheap power.
I mean, lots of problems rise from this from interoperability, debug ability, removing control & ownership of your own data…etc
Obfuscating the data means you (The user, via your own means) no longer have access to it, you cannot integrate with it, …etc This is a problem for a project that promotes itself for openness and compatibility.
Firefox should not be solving your user level access permission problems, that’s not it’s job 🤦
Naw, they will figure out how to target you specifically.
Will these ever be useful on the second hand market
Nope, not ever. Even if it’s standard form factor gear.
They will be disposed of (“recycled”), since that grants the largest asset depreciation tax break, and is the easiest economically. The grand majority of all data center gear gets trashed instead of reused or repurposed through the second hand market.
Source: I used to work at a hardware recycling facility, where much of the perfectly good hardware was required to be shredded, down to the components, because of these stipulations. It’s such a waste.
Dumping bucket of tens of TB worth of modern RAM into a shredder is… Infuriating.
They wouldn’t though, large businesses see no consequences from laws that you and I would see consequences for.
I should have used softer language which I have changed it to be.
Everyone’s experience with neurodiversity is different. If you have a system and that system works for you then that’s awesome. Developing systems that work for your needs can be a significant hurdle.
Yeah, but they you gotta organize it, and garden it, and maintain it. Or it’s just another useless dump of probably useless information. This can be difficult for folks with ADHD and similar.
Not to mention that many tabs are transient, they are not meant to be permanent. Making them permanent means they are out of sight out of mind and will pile up even more
Protip: Installing more ram makes for more convenience on keeping tabs alive forever
There’s a reason I plopped in another 32GB stick
It really is a shame that Microsoft gave up their technical position in order to gain a market position. However, ultimately, that worked out for them.
Microsoft didn’t keep it because developing a web browser is insanely expensive, and they where too far behind. While they where trying to pivot to Azure and other cloud ecosystems.
With likely 1000+ engineers being involved in Chrome in a meaningful way, it’s an insanely expensive project, and Microsoft just couldn’t keep up.
Now given that Mozilla has an engineering team 1/4 to 1/6th the size for Firefox really puts into perspective How astronomically well they have been doing with Rust.
This also puts into perspective how unlikely other browsers like Ladybird are to ever take off, when a year of their development is eclipsed by a few weeks of major browser development. Compounding over and over.
Shits a mess.
Welcome to the monopolization of the internet. And blatant anti-competative practices.
Huge operators like Google can intentionally make their sites and services a worse experience for other browser users.
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.
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
All devices on the computer consume power.
The CPU being the largest in this context. Older processors usually don’t have as aggressive throttling as modern ones for low power scenarios.
Similarly, the “power per watt” of newer processors is incredibly high in comparison, meaning they can operate at much lower power levels while running the same workload.