Of course, it's never impossible for the user to click a button. They can click on anything under their cursor. The key is giving them feedback to show them what their clicks will do or just did. If you can update the visuals within a frame or two, that's already fast enough to give that feedback.
It sounds like your scheme would only allow browsing the "adult web" on locked-down, unmodified devices running government-approved software. Frankly, that's worse than even requiring ID.
There would be a bunch of value in having, say, a good 30B-class model that used my local language as well as it does English. There's lots of cases, especially in the government sphere, where local processing is a requirement and frontier-level capabilities aren't required. Making those cheap to run seems like a fine goal.
I haven't ever heard of an SoC supplier demanding that the device's bootloader must be locked. Are you sure that this is happening? I've only ever seen devices delete first-party blobs, presumably of the manufacturer's own volition.
New Zealand, along with Australia, shares a lot of its urbanism with the US and Canada. In the rest of the (urbanised) world, I'd say it's expected to be able to walk to stores, especially in cities.
It's interesting to ponder if it's just the low density (caused by "having too much land" to expand on) or other factors that deprioritise walking like this.
Closed-source projects have been dealing with this forever, by having a mostly-static pool of employees replenished through job listings and interviews. A FLOSS project adopting this model would certainly feel weird, but could work if there were enough willing candidates. The question is, who will take on effectively a job without the monetary reward?
As far as I know, speculative decoding still verifies that the proposed tokens are what the "big" model would generate, it just uses the guesses to make that process faster. Setting the probability threshold too low then shouldn't affect correctness, just speed (time will be wasted verifying bad guesses).
I'm convinced that in the billions of people living on Earth, there are a couple million that could agree on things that currently divide countries, like this. Sadly they're unlikely to ever be able to gather together in a single state.
The status quo is nation-states in roughly their post-WW2 borders, and it's fiercely protected. The upside is stability and fewer wars, the downside is that the only way to try anything new is to co-opt an existing country. Adding to that, most countries are ethnostates that would prefer to have only a small percentage of their population be migrants. It's an easy way toward social cohesion, you just stay roughly where you're born, with people who were also born there and share the same cultural background. As we can see, it's not ideal - two lifelong neighbours can easily hold completely opposite moral values.
This seems like it needs a regional distinction. I regularly do this since cars do reliably stop/slow down (in Prague, and not right in front of cars).
That only holds if you believe the market has a high level of efficiency.
Maybe if we wait long enough, the distribution of devices being manufactured will match consumer preferences, but I don't believe that to be the case today. The iPhone Mini sold ~millions of units. That may not be enough for Apple, but it's certainly enough to make a profit, yet nobody's building small phones now.
Well, before Apple, most phones were appliances with fixed software; there was no openness to speak of. That said, I wish they hadn't continued this trend and instead took inspiration from Windows Mobile.
You talk about "an Android that has a replaceable battery" as if that was something you could just buy at any store at no inconvenience. Sadly the majority of Android phones no longer have user-replaceable batteries, and only a select few models have official replacement parts available.
I'd be happier if this was something the market took care of, but after 10 years of glued-in batteries that you most likely can't even buy, I think it's time for a regulatory nudge.
The reasonable takeaway from that correlation is that people with preexisting issues turn to ergonomic keyboards to avoid worsening those issues, not the other way round.
Over a week or two that will accumulate enough error to make me miss a tram. Of course, you could just re-set the time every week, but there's your downside.
Eh, XML is as much of a superset of JSON as the Turing machine is a superset of context-free grammars. The former has all the _power_ of the latter and more, but the mapping between them is non-trivial, far from an embedding.
I think it's fine to say C#'s data model is a superset of Java's or Rust's a superset of C's, but XML and JSON is too far for me, personally.