zamalek
The TV might throw an conniption over loss of this critical functionality.
The metrics to win over Steam gamers aren't hard - and it could be done with another well-funded and like-minded CEO. The problem is that the metrics that Steam wins with are for users, not board members, not C-suite, not investors, not shareholders. Valve is no saint, but they are pretty damned close to as close as a capitalist can get.
You couldn't get a competitor financed.
* It doesn't do things you ask it to
* It adds things you didn't ask it to
It still does both and therefore I still consider it failing. If you don't want to call it "lazy"; fine, but it seems as though the underlying issue is still there.
Claude does this too, FWIW.
But I don't the GP comment was talking about that; I have also used WiFi without an antenna (PCB or otherwise), and it was also slow for me.
A dummy load is probably the best idea: an impedance mismatch would obliterate any chance of anything working (including Bluetooth fwiw).
Sometimes a decision tree is definitely faster. When developing System.HashCode, I used a switch (which I think always compiles to a jump table in .Net - at least my case did back then). This was for the trailing non-block sized bytes, I think. It was either suggested, or I decided to try, a decision tree and it was significantly faster. This was _many_ years back, so I don't have the figures, but they can be better in some scenarios.
Where they could improve is hotkeys: they are all heavily reliant on them, which is unreasonably hostile to non tech users.
Humans aren't very good at identifying what they need from tech. The earliest example is the spreadsheet: no average user would have asked for it because there was no skeomorphism to draw from. We would have had graph paper with a single char per cell if we went with skeomorphic.
Cascading window managers are objectively terrible. Obviously we don't force better solutions onto people, but they have very few redeeming qualities.
> GP: EACv2 can't accept self-signed kernels and bootloaders
Also, from what I understand from the NixOS discussion[1] on this, it's using mok. That does put which keys are trusted in Epic's hands (which also isn't perfect, but is still vastly better than Microsoft). That article author seems to be poorly informed, or may be spreading FUD.
[1]: https://discourse.nixos.org/t/eac-linux-v2-requirements-vs-b...
Tim Sweeny being "one of the people who dooms Windows" was the least likely thing on my multiverse bingo card - but he's eroding that too. EAC v2 will have kernel mode (eBPF) anti-cheat. Microsoft has lost their moat at the throne of AI.
Ah good ol' serendipity. I strongly believe this too, and I think that's why older (less capable) models fared better: they hadn't fallen into the valley yet. Maybe it's not a valley at all, and is just a cliff after which there is uncanny.
When the earliest models launched I was super-excited to no longer have to write pull request descriptions and commit messages. I have done a sharp 180 on that and I'm no longer a meat proxy[1]: instead I point out any redirects and improvements I made the agent do before opening the PR (which there are still _many_ in even the most trivial tasks).
And this is where you need a world model. A human player would have taken the 2 minutes required to solve their hunger issue.
Big-O doesn't include constant factors for a reason (never mind just being a constant entirely), but maybe I am misunderstanding what you are trying to say?
1. Revenge on an ex.
2. Send someone the packet, set up a situation where they need to call 911.
The software is installed on the _sender_ device.
8.5% of American households have no car[1]. That isn't a strict majority, but if you can be charitably informal: paying for grocery deliveries is orders of magnitude cheaper than loan+insurance+maintenance for a car.
If you want to become car-less then the like of Instacart make that a realistic prospective (but Instacart specifically makes no sense because stores usually do it for free if you can tolerate next-day).
I don't understand how I hit the anti-Rust tripwire here:
> My comment: any memory safe language will do
Same thing applies here. Even Rust has a crate for dealing with binary data, despite its memory promises: https://crates.io/crates/untrusted
It's a fucking minefield, and this is one area where the Rust zealots are undeniably correct. It doesn't have to be Rust, any memory safe language will do, but Rust also happens to be performance competitive and that's usually also desirable.
So probably still in line with what you remember.