The stakes are the highest across the entire kernel. Data that's corrupt cannot (easily) be uncorrupted.
Bad drivers could brick (parts of) your hardware permanently.
While you should have a backup of your data anyway.
Readit Newstpolzer commented on Bcachefs may be headed out of the kernel lwn.net/Articles/1027289/... · Posted by u/ksec
tpolzer commented on Automakers Sold Driver Data for Pennies, Senators Say nytimes.com/2024/07/26/te... · Posted by u/strict9
A long time ago, I read an article about a journalist that did just that: bought a pack of “anonymized” location data set, then promptly tracked and interviewed one of the people in said data set.
It kills me that I can’t remember where the article was exactly, because it’s one of mu favorite examples of why fighting indiscriminate tracking is important. I remember it being from a Scandinavian newspaper, maybe Dannish?
One of the oldest (AFAIK) occurrences of this was AOL releasing a data set of "anonymized" search queries in 2006 and it took a about a day for the first person to be deanonymized.
https://www.nytimes.com/2006/08/09/technology/09aol.html
https://techcrunch.com/2006/08/09/first-person-identified-fr...
tpolzer commented on What's the point of std:monostate? You can't do anything with it devblogs.microsoft.com/ol... · Posted by u/luu
It has other uses for end-user developers. For example, when you need a class member to be conditionally elided based on template parameters. You can swap the normal type with non-zero size with std::monostate such that it has zero size.
A std::monostate member will still have non zero size, because it needs a unique address.
tpolzer commented on What's the point of std:monostate? You can't do anything with it devblogs.microsoft.com/ol... · Posted by u/luu
The distinct types are the whole point. You wouldn't want a std::tuple<> to be implicitly convertible to a std::optional<T> (for arbitrary T), and std::nullptr_t exists to be the type of nullptr, which captures the conversion behaviours appropriate for null pointer literals and has nothing to do with the variant use case std::monostate exists to serve.
If there was a std::unit_t and it was implicitly convertible to optional, tuple and pointer, I don't think that would be worse in terms of usability at all (maybe worse in readability for people who haven't heard of a 'unit' type).
As for the std::variant use case, using std::monostate is only a matter of convention there. You could use any of the other unit types just the same.
tpolzer commented on What's the point of std:monostate? You can't do anything with it devblogs.microsoft.com/ol... · Posted by u/luu
What's really weird to me is not that C++ has a unit type and picked a weird name for it (that's just C++). The weird thing is how many unit types it has:
- std::nullopt_t
- std::nullptr_t
- std::monostate
- std::tuple<>
And I'm sure there's more.
tpolzer commented on Options for genuine ECC RAM on the desktop in (early) 2024 utcc.utoronto.ca/~cks/spa... · Posted by u/ingve
Some devices with 13th gen Intel processors support in-band ECC. This basically hides a fraction of RAM from the OS and uses it for ECC.
Example devices are: LattePanda Sigma [0] and AsRock Industrial NUCS BOX-1360P [1].
Unfortunately they are quite expensive and enabling in-band ECC lowers performance significantly. So my next server rig will likely have an AMD PRO CPU instead.
[0] https://www.servethehome.com/lattepanda-sigma-review-the-ras... [1] https://www.anandtech.com/show/18732/asrock-industrial-nucs-...
I find it annoying that (a) this seems to be a hardware feature that is almost universally permanently disabled in firmware and (b) it's almost impossible to find out whether it is supported by any given product (neither of the two products you link provide any mention on the spec sheet).
tpolzer commented on Solid-state EV batteries now face "production hell" spectrum.ieee.org/solid-s... · Posted by u/jnord
I personally wonder how much more the 33% would be if we had continued the focus on ICE. I believe there is no business case anymore to invest significantly in advancing technology, if everyone wants a new shiny toy.
The theoretical limit is 50% according to Wikipedia, but there's other factors being optimized for as well aside from efficiency:
https://en.wikipedia.org/wiki/Engine_efficiency#:~:text=Mode....
tpolzer commented on 2TB microSD card is on the way early next year overkill.wtf/2tb-microsd-... · Posted by u/brandrick
What about speed? Is the adoption of SD Express slow compared to previous standards? I never see any computer (or smartphone) specs advertising "microSD Express" speeds, and it is already 4 years old.
The coming standard claims "up to 2GB/s possible." [1], and at this "speed" (of adoption, that is), this is not coming anytime soon.
[1] https://www.pcworld.com/article/2124706/sd-express-9-1-new-s...
SD Express is basically dead as far as I can tell.
SD card users who care about speed have UHS-II equipment, but SD Express and UHS-II use mutually incompatible high speed signalling on the same pins (so cards and readers are only supporting one of the two - I guess technically this could be fixable with special purpose chips, but at large cost).
Users who care about speed but not about SD card compatibility are already using CFExpress, which is supported by most modern professional cameras and has much better hardware availability than SD Express.
tpolzer commented on Linksys WRT54G and WRT54GS power supply (2005) kioan.users.uth.gr/wirele... · Posted by u/peter_d_sherman
Now that source/supply and sink/drain/device are usb-c, it seems like this kind of flexibility would be possible for a huge number of systems.
It'd be interesting for systems to expose their efficiency curves, to make these kind of decisions optimally. Maybe your charger is much more efficient at 20v that the power efficient optimal solution is to pipe 20V in, even at low power modes. There's all kinds of optimization problems we could tweak, if this sort of efficiency data were visible.
Ideally with PPS, your device can actually just ask exactly for the regulated voltage it needs on USB-C.
Most modern smartphones can use that to charge their batteries more efficiently/with less heating of the phone.
Is that supposed to be a lot? Your phone receives multiple joules every second when charging, even with a slow charger.