MOAR POWAH = faster magic smoke production! Efficiency!1!!

Jesus, not this shit again. You know why colleges are 58-61% women? Because 55-60% of the application submitted are from women. Now, with us acknowledging that more women are in college (and graduating college) now look at something like amount of women CEOs. Or the general pay gap. Or even the pay gap in the same job (much smaller, but still exists). If women are getting more college degrees, shouldn't that mean they also earn more and get higher positions since people with college degrees earn more? So why isn't this happening? Care to explain how that with your anti-male bias BS?

Exactly. And Vmware's calculus is that as long as it has a dozen gigantic clients (governments, huge enterprises) that it can charge whatever it wants, then the small fish aren't worth it.

Word up, freakin' Wolfman Jack and GOAT GLANDS! Public service, indeed.

Eh, I'm sure it'll be fine. No need to be alarmist, like they were about Trump.

If it were open source and someone cared enough to fork it, then presumably there are open licensed contribution to the repo that Siemens won't own the copyright to.

What happens to those? Can they be taken closed source at all?

We have bubonic plague infections every year in the United States. Very, very few, admittedly, but it's not like it's been eradicated. So there's still benefit in studying it.

The more I hear about this so-called "SF Democratic Party," the more I'm convinced they don't speak for the majority of SF voters. Seriously. They seem to be some strange, centrist organization that no voters belong to and nobody knows where they get their money from.

This "new" site is part of a larger effort by that slob to kneecap or compromise US government Web sites, and steal your personal data.

I first read about the effort here: https://thedreydossier.substac...

Yesterday, she took a look under the hood of America.gov, and yes, it's as bad as everything else the DOGE vandals have been doing: https://thedreydossier.substac...

Up until this point, government Web sites were designed, built, and maintained by the agencies responsible for that government service. For example, if you wanted to apply for or renew your passport, you would go to state.gov, which is run by the US Department of State, which is responsible for processing applications for and issuing passports. No other department has lawful jurisdiction over passports.

From the point of view of the law, that's still true. But the slob, without anyone's permission, kluged together passports.gov. This site was built and is run by the White House's "National Design Studio," completely outside the law and without any independent oversight. The State Department was not consulted and has nothing to do with it. Further, the site is filled with third-party trackers, analytics, and some custom code that copies every page you view, including form contents, to an unknown third party.

Oh, and the guy leading the National Design Studio and in charge of building these fake sites? He's Joe Gebbia -- cofounder of Airbnb. Read both articles for more details.

In short, you should treat America.gov as a malware site and stay well away from it. Under no circumstances should you feed it any of your personal information.

Just to note, the WSL containerisation approach is horrible for anything I/O intensive. WSL 1 had ELF binaries supported by the kernel and ran natively, this is a far superior approach to WSL 2's containerisation when it comes to raw speed.

I benchmarked this a few months ago and it was between 300%-600% slower on raw disk performance I/O.

Unfortunately, CustomCSS is dead. See announcement:

https://github.com/Aris-t2/Cus...

It still worked for me perfectly with the previous Firefox ESR (140.x), but with 153.x I suddelny got my search box (yes I want a separate search box, not automatic search from the url bar!) with double line spacing. No other issues though.

The announcement has a couple of other recommended projects as suggested migration paths.

Get locally produced stuff instead of imported ones from overseas. "Local" does not necessarily mean like from nearby farm, but whatever has minimal time spent in logistics.

Problem with shipping fruit from faraway places is that they are typically picked raw, and then they ripen during the months they spend in a shipping container and finally get an artificial ripening (e.g. with ethylene gas) at the end of journey. Of course they do not have nutrients or taste.

Just wondering, since related topic is Tesla FSD. EU is right now debating on whether to allow FSD across all member states. Some member states have permitted it already, but the big decision is still to be made. There's an interesting report from Belgium where Tesla FSD decided to disobey traffic laws around pedestrian/cyclist zones (going 50 kph in 20/30 kph zones, overtaking cyclists in bicycle lanes, etc).

https://www.johanna.be/images/...

Results start on page 12, but summary include the nice snippet

"Performance in home zones was similarly concerning. Of the 12 tested home zones, FSD exceeded the 20 km/h legal limit in five cases (42%), averaging approximately 26 km/h. In two-thirds of the tested locations, the system incorrectly isplayed a higher speed limit, typically 30 km/h or 50 km/h. Given that home zones are specifically designed as shared spaces here pedestrians, including children, may occupy the full width of the street, these findings raise significant safety concerns."

So yeah, I'll just drive myself unless car manufacturer assumes full liability when it decides to run over some kid on their bicycle.

If the RAM limitation was to prevent resellers from sourcing cheap RAM chips, and adding them to low RAM versions of RPi for a markup, and the RAM limitation is easily bypassed with and SPI firmware downgrade, then what is to stop the resellers from continuing to do that and also downgrading the firmware? What's the point?

Seriously, there's a ton of articles about this, but here's a link directly from Google:

https://support.google.com/and...

Steps 1 & 2 are for the one-time 24-hour cooloff, step 3 is just like before. Oh and note 2e: "After the security delay is complete, you can choose whether to keep the advanced flow on for seven days or indefinitely."