e_y_
Actually for many years even to build regular Bluetooth devices that did anything besides audio, you needed to add a special chip (Made for iPhone chip) to your hardware to verify that it was an authorized Apple Accessory. Pebble had one, but any 3rd party apps that wanted to send data to the watch (like Uber app, sports apps, random indie apps) had to get allow listed to communicate with accessory devices like Pebble.
And if the person is unsure whether the situation is critical, they might try to "sleep it off" rather than driving or getting a ride, because ER is also kind of expensive and you could be stuck there all day.
They should be able to get to SFO from Millbrae Ave and San Bruno Ave without getting on the highway proper, although it'll likely be a lot slower unless you're getting a ride from nearby. While SJC can serve downtown SJ and Santa Clara without getting on a highway.
There's a risk that robotaxis could become too cheap and people use them for point-to-point transportation because it's faster. This could be mitigated through taxes on robotaxis (with incentives to connect people to transit) and/or car usage in general, or maybe using robo-buses to provide a middle ground between personal convenience and system efficiency.
I think the ecosystem has more of the opposite problem: engineers create libraries to scratch a particular itch, because they needed to solve a problem for their own project, or maybe it seemed like an interesting solution that they wanted to share with the world. If the person was working for a company, they may even be paid to maintain it for a while.
A bunch of other projects start depending on it, but the original creator/maintainer has moved on. They might not even be using the library for their own projects any more, nor paid to work on it. Now they're stuck maintaining it out of a feeling of obligation, or maybe it's a passion, but at a certain point it becomes unsustainable and the project becomes unmaintained or under-maintained (huge backlog of tickets). Maybe they find new blood to help out, maybe they don't.
For progressive enhancement, I like the island approach used by Astro. I do think that most developers are not just building static sites though. And if you're generating HTML on the server side and then updating it dynamically on the client, having two different languages (Java/Go/Python on the backend, JS on the frontend) becomes messy pretty quick.
There are times where you should build the simplest solution that meets your needs, and times when you should think ahead to future use cases so you don't box yourself into a corner. And picking a framework is a big part of that process.
There's also nothing stopping you from serializing unstructured data using an array of key/value structs, with a union for the value to allow for different value types (int/float/string/object/etc), although it probably wouldn't be as efficient as something like CBOR for that purpose. It could make sense if most of the data is well-defined but you want to add additional properties/metadata.
Many languages take unstructured data like JSON and parse them into a strongly-typed class (throwing validation errors if it doesn't map correctly) anyways, so having a predefined schema is not entirely a bad thing. It does make you think a bit harder about backwards-compatibility and versioning. It also probably works better when you own the code for both the sender and receiver, rather than for a format that anyone can use.
Finally, maybe not a practical thing and something that I've never seen used in practice: in theory you could send a copy of the schema definition as a preamble to the data. If you're sending 10000 records and they all have the same fields in the same order, why waste bits/bytes tagging the key name and type for every record, when you could send a header describing the struct layout. Or if it's a large schema, you could request it from the server on demand, using an id/version/hash to check if you already have it.
In practice though, 1) you probably need to map the unknown/foreign schema into your own objects anyways, and 2) most people would just zlib compress the stream to get rid of repeated key names and call it a day. But the optimizer in me says why burn all those CPU cycles decompressing and decoding the same field names over and over. CBOR could have easily added optional support for a dictionary of key strings to the header, for applications where the keys are known ahead of time, for example. (My guess is that they didn't because it would be harder for extremely-resource-constrained microcontrollers to implement).
Although even as a non-participant, witnessing a party first-hand would be more informative than the filtered version you get from Hollywood.
The accidental omitempty and - are a good example of the weirdness even if they might not cause problems in practice.
There's also many advantages to being able to lift something large/heavy in one go, rather than smaller payloads that need to be unfolded (like JWST) or assembled in space, which can drastically increase the development costs.
https://slickdeals.net/e/3220862-hp-touchpad-9-7-wifi-tablet...
It's also harder to speak out when you're a US government employee, but now that they've been fired ...
CPU chipsets have borrowed video decoder units and SSE instructions from GPU-land, but the idea that video decoding is a generic CPU task now is not really true.
Now maybe every computer will come with an integrated NPU and it won't be made by Nvidia, although so far integrated GPUs haven't supplanted discrete ones.
I tend to think today's state-of-the-art models are ... not very bright, so it might be a bit premature to say "640B parameters ought to be enough for anybody" or that people won't pay more for high-end dedicated hardware.
I still think it'll do well because even if you need to hire 1 person to remotely monitor every 10 cars (I doubt Waymo has anywhere near that many support staff) it's still better than having to pay 10 drivers who may or may not actually be good at driving. But to really take over they'll need to be much more independent.
https://www.tomshardware.com/tech-industry/artificial-intell...