The biggest issue is, of course, (4) - how do you plan on enforcing that for sites that don't run out of your country of residence? Implicitly restrict access to only those sites in said country?
You don't enforce that, the owner (or the owner's parents, etc) of the device set that policy. MDMs can all already do this, there just needs to be a more user-friendly/consumer focused MDM to allow parents to control their kids devices. Just have it warn "Out of country sites may not follow your device policy, do you want to block them (Y/n)?"
Same way the US enforces any internet foreign policy. Make the credit card companies cut them off,make advertisers cut them off. US controls most of the ways they could make money.
Even then - I have a reasonably nice Brother Printer/Scanner/etc device, and I could never get AirPrint to reliably work until I switched over to using Ethernet instead of Wi-Fi. Something to do with it going to sleep and not broadcasting the necessary mDNS stuff, IIRC. I couldn't find any combination of settings in the printer to make it happy, and since it's now right next to a switch, it's not really worth the effort of digging any further.
The Java one can actually be quite helpful, for a couple of reasons:
1. It tells you which variable is null. While I think modern Java will include that detail in the exception, that's fairly new. So if you had `a.foo(b.getBar(), c.getBaz())`, was a, b, or c null? Who knows!
2. Putting it in the constructor meant you'd get a stack trace telling you where the null value came from, while waiting until it was used made it a lot harder to track down the source.
Not applicable to all situations, but it could be genuinely helpful, and has been to me.
In actual Java-Java (as opposed to Kotlin or something), first line of defense should be a linter that tries to prove nullability properties. In situations where that doesn't work, well, I think I'm the world's only fan of Java's assert keyword. If you can't use assert the language feature, you can at least throw AssertionError, which is a non-Exception Throwable subclass that's more likely to make your program die instantly, as it should, instead of treating the contract violation as a recoverable condition.
When spoken? Almost certainly. But I think they mostly write in Hochdeutsch, especially in formal contexts, at least that I've seen (private chats/etc are a totally different matter), so I don't foresee any major issues there.
Austrian standard german is slightly different from the German variant, even when written. The differences are pretty minor, though, so it’s very possible to have a relatively long text without being able to tell which one it actually is (especially when potatoes are not referenced in it).
They really are very, very different. Knowledge of one helps with the other, but it's far more than just "a couple of weeks to adjust to the accent", for example.
EDIT: It's worth noting that this is mostly a spoken thing, AIUI - most formal/semi-formal writing would be in Hochdetusch rather than a local dialect.
Turns out that under certain conditions, such as severe exhaustion, that "sus filter" just... doesn't turn on quickly enough. The aim of passkeys is to ensure that it _cannot_ happen, no matter how exhausted/stressed/etc someone is. I'm not familiar enough with passkeys to pass judgement on them, but I do think there's a real problem they're trying to solve.
If you're saying something is less secure because the users might suffer from "severe exhaustion", then I know that there aren't any proper arguments for migrating to it. Thanks for confirming I can continue using OTP without feeling like I might be missing something :)
Yeah, but they genuinely also prevent you from moving away from companies in the process of enshittification, since the whole export/import thing seemingly hasn't been figured out or even less been deployed yet.
Besides, if you ignore security alarm-bells going off when exhausted, I'm not sure what solution can 100% protect you.
That matches my experience, in an admittedly slightly older car. Note that you'll rarely be charging over 80% because it's just too slow, and going under 5-10% is a bit too stressful, so practical range is probably 70-75% of maximum on longer trips. Less if it's winter and/or the AC is running.
If I could rely on every Rasthof having multiple functional EV chargers, I think range anxiety would be far, far less of an issue for me, but as of now it's something that I do think about for longer trips, and do have to plan for.
Of course you start the trip off at 100%, but the point is that charging speed varies substantially based on the SoC in the battery. So if you deplete most of your charge and need to stop, recharging to 80% takes substantially less time than topping it off to 100%. So if your battery range is 300 miles, you might get 280 on the first leg of your trip but will only be able to do maybe 220 on the second leg.
I have a PHEV specifically so I can take an occasional 500-600 mile trip without range anxiety. With the ICE, I can almost do the trip without a pit stop. But I make a stop. So it seems that ICE or EV both have to make one stop for a 500 mile journey. Of course, the ICE could make a 1000 mile journey with two stops where your EV would need three. But I make a 1000 mile journey in a single day less than once a year. So 10 extra pit stops in 10 years doesn't seem like a bad trade-off for the 4 or 5 fill-ups I skip every month.
> Of course, the ICE could make a 1000 mile journey with two stops where your EV would need three.
It sadly doesn't work like that. Range is reduced by about 25% in the cold. Further, one doesn't charge 0-100% at stations. They charge 10-80%. This is suggested by Tesla because the last 20% takes longer than the first 70%. So the effective range on a new standard range Tesla Model Y is 455 * 0.75 * 0.7 = 239km between stops. Assuming Tesla's 455km initial estimate is accurate, and it's not really. It tends to overestimate, so in reality, it's less than 239km. Especially at highway speeds.
A 1,000 mile journey would require approximately 7-8 stops, depending on charge at journey start and end.
Answered different thread - superchargers get from 5-10% to 95-100% in line 30 minutes.
When we are on roadtrips I often have to go and unplug it so I don't get extra charges for idle. I know superchargers are not everywhere.
Thats… not obvious at all. Unless you’re within the super small part of society that can charge at home, you might be as well starting with 20 or 30% - exactly the same as with a regular car.
Right, but that’s just a single, very un-typical country. Most people in developed countries live in cities. If you live in a city - you live in an apartment (unless you’re quite wealthy)z
I expect that most people living in NYC do not have a single family house with a garage and a garden.
It is not at all an un-typical country. It might even be the case for the majority of the US, most of which live outside New York City.
Plus, cities in countries over on this side of the pond provide street charging and even have legislation about maximum distance to a charger. Parking garages and lots also provide charging. Not as convenient as living in a house with a charger where you can always plug in at night (and possibly use private solar cells for extra benefit), but good enough for most commuting.
I had a road trip, and pretty much all the time I got 95-100% charge while having lunch with supercharges, which are everywhere. It takes 30 minutes to do it.
* In the big cities, increased rents will almost immediately eat up the extra income from the UBI, and there won't be any meaningful change in the status quo for anyone who rents — which I imagine includes the majority of the people who do the important but undesirable jobs.
* Anywhere that the people doing these jobs either can afford houses (smaller American towns, e.g.), or where there's enough rental supply that rent won't immediately go up by the same amount as the UBI, will have to start paying people more to do these jobs. As far as I understand it, jobs like trash collection are already relatively well-paid given the training and qualifications required, so they might not even have to pay that much more.
Most people who prefer DW would say that D&D sometimes has clear rules for something, but often has no rules, boring rules, or rules that aren't necessarily "fun". Combat, while tactical, tends to be slow and can frequently consume a lot of time in a session, plus the majority of rules and character powers are focused on combat.
If you're playing sessions with a lot of RP, DW will have a much better balance of rules:session-time, it's much easier to prep for, and given how rules-lite D&D really is outside combat, will probably have about the same amount of narrative input. Note that it's not necessarily the "group debating if the player survived", but typically the GM giving the player a choice when they fail to climb the wall, like "you fall and take a little damage, or you slip a little, cursing loudly and alerting the enemies at the top to you".
Done well, it gives the players a lot more agency, and much better buy-in for the story as they're now shaping it, instead of just being along for the ride. I would also say that pre-written narratives aren't really a thing for DW (at least, as far as I know!), so it's really down to what the DM sees as an appropriate penalty or choice, often phrased as "you succeed, but <thing>".
It's not really better or worse than D&D overall, I'd just say that it's much better suited for certain play-styles. If you enjoy tactical gameplay and using miniatures, then D&D (or maybe Pathfinder) are much better options. If the thought of yet another fight makes you want to gouge your eyes out, I'd recommend giving DW a try.
The player choices and handling of partial success in PBtA games (like dungeon world) really makes them sing. A partial success leads to adding complications, which creates really interesting situations.
The original Apocalypse World book has some really great ideas on how to run a campaign, as well - very worth reading for anyone who runs ttrpgs.
I had played enough TTRPGs at that point that when I encountered Apocalypse World that I found the advice to generally just be common knowledge. But if you're new to TTRPGs I highly recommend it for good advice even when running traditional TTRPGs.
