neilalexander

> you kind of deserve to get owned, right?

The people who have no idea what services are listening on their machine due to some default that someone else decided upon absolutely deserve to get owned, yes, because that's a totally reasonable mentality to have.

Sarcasm in case it wasn't obvious. At what point did it just become normal to be so user-hostile?

Presumably this means one day it will just stop working when Microsoft decide to shut down the cloud backend.

Stage Manager is disappointingly over-engineered. Managing the workspaces is much more mentally taxing than having windows just fade into the background, every new app somehow always seems to open up at the wrong size and then annoyingly takes everything else off-screen with it. I am a heavy iPad user but Stage Manager is rarely useful for me.

If you think IPv6 is too complicated, you are either overestimating IPv6’s complexity or underestimating IPv4’s complexity. IPv6 is undeniably simpler. It has a cleaner header format that is simpler to parse, it has no need for on-path routers to perform fragmentation, it combines host/router discovery and various diagnostic control packets down into a single protocol called ICMPv6, it has stateless address autoconfiguration and correct link-local address behaviours amongst others. It fixes decades of mistakes that have accumulated in IPv4.

Docker's runtime overheads on Linux are tiny. It's pretty much all implemented using namespaces, cgroups and mounts which are native kernel constructs.

I didn’t say that iOS is some different breed of computer, I said that it doesn’t present a lot of the complexity. Of course it’s all files underneath but the point is that they are usually presented in a way that doesn’t leave the user thinking of them as “files” as an abstract concept. People browsing through the Photos app aren’t really thinking about file names, whether it’s a JPEG or some other format, what folders they’re in etc. The “abstraction” doesn’t need to be deep to be effective.

It's easy to say that files should be easy to understand by now but for a lot of people who aren't necessarily computer natives, there is a non-trivial learning curve as to what a "file" conceptually is: something that's on a storage device, that's in a specific part of some abstract folder tree, that is required to have a name, that has a type that may or may not in the name (file extensions), that has a format that some programs understand and others don't, that has an associated program or programs that know how to open it, that can be copied and that copies are in no way connected to the original that may be found in different locations to the original, etc.

Contrast that to how iOS just generally leaves applications to "own" their own data and present them however makes most sense, with only a few exceptions (the most notable being the Photos app, which sorts and displays photos by things that make sense for photos). The place where you'll find the thing you were working on is actually just in the app where you were working on it, which is, unsurprisingly, far easier to explain. Plenty of people get on perfectly fine without knowing or caring about "files" and are not really worse off for it.

If you're looking at this from the perspective of a power user, then sure. For everyone else, the iPad makes a robust computing device that simply does not have a lot of complexity that we power users have just learned to accept. Try explaining the concept of "files" or "terminals" to a random person on the street.

I don't think it's anything to do typing the address. It's that there are a lot of people out there who don't understand what a web browser really is, how a web page is distinguished from an app, or how to get something from a web browser to their home screen.

See also: people who copy and paste images into Word documents before attaching them to emails. Same mental model disconnect.

A downside to having persistent storage that is not mentioned is that a server could potentially be compromised in a way that survives restarts. No amount of disk encryption will protect you from that.

If the machine has no persistent storage and boots from a medium that is provably read-only (i.e. a DVD or a netboot image), it's always going back to a known state every time it comes back up.

Of course it’s not gone, although I suspect there’s a very large number of people who would be surprised to learn either that their Wi-Fi network at home is actually a LAN or that a LAN has utility outside of just providing access to the Internet.

I think these days Apple Silicon is more of an umbrella term for the packaging of their CPUs, GPUs and NPUs.

The affected generations of Apple TV were from 2010 and 2012 respectively, predating the current tvOS-based models by several years which are all still supported. Those generations weren't especially popular at the time anyway but it would be very unlikely that there is a significant number of these in use after 12 to 14 years given that Netflix were probably one of the last streaming platforms supporting them.

Congratulations: you've just created a culture where people are afraid to report potential issues for fear of losing their jobs. Maybe there are some cases where you find that specific individuals end up acting irrationally more often than not, but on the whole, it is better to treat these acts as if they were good faith until proven otherwise.

You can do it over USB but both devices need to be signed into the same iCloud account.

Apple have full control over process scheduling so there is absolutely no reason that it should compromise the experience at all. They could notify the app it's about to go into the background so that resource-intensive tasks can be paused, then severely limit CPU shares to preserve battery life and then notify it again when it's about to hit the foreground. That would be enough just to keep application state in memory or socket connections alive.

In the UK at least, they mostly do. You park up, plug the car in, tap your contactless card and that starts the charge. Once the charge completes (or you unplug the car), the charger works out how much electricity you used and your card gets charged accordingly. In my experience there aren't too many charging points that don't accept contactless payments in this way.

Sometimes having memberships, RFID cards or apps for the different charging networks unlocks cheaper rates though, so contactless payments don't always end up being the most economical in the long run and that can make it harder to compare charging providers, hence why things like Zap-Map and Electroverse were born.

Over 10,000 miles, my EV saves me roughly £1300/year compared to my previous petrol car on the basis of being able to charge the EV overnight at home for £0.09/kW and the petrol costing around £1.40/L before. If I were relying on public charging in the UK, that story would be quite different.

A typical public 7kW AC charger here would start at around £0.45/kWh, at which point the savings would only be £300/year and that is assuming there is somewhere close by that I could leave the car charging for hours at that speed.

If I had to rely on a typical 50kW+ DC charger here in order to get charged up more quickly, that would start at a much higher £0.79/kWh, at which point driving the EV would be £700/year more expensive than the petrol car.

While you're correct, it's worth keeping in mind that Wireguard only looks up DNS names when the tunnel is started.

If your remote endpoint address changes, the only way your client will find out is either if you restart the tunnel on the client device by hand, or in the lucky case, if the remote endpoint happens to send some data to you at the right time while your client is still hopefully reachable at the same IP+port, which may not be a given behind a NAT if a port mapping times out from inactivity or if it changed network in the meantime.

If you use Wireguard only to route to/from to a central hub that has a static IP address then what you have is perfectly fine.

Tailscale works well for situations where you have lots of roaming devices that perhaps want to talk to each other as well as to central hubs or you want to gate all of this behind some kind of SSO.

It's about the clearest way that they can tell you that they value your presence more than your skill without actually saying it.

802.11ah, not 802.11ac.

In many ways this is a "classic Microsoft" move — take something that works perfectly fine and replace it with something new but completely inferior and often less featureful. They have been doing this in the consumer space for years and inevitably users get upset but move on.

What I doubt they have considered is the number of businesses dragging-and-dropping mails as EML files and working with offline PST folders and relying on various other invisible features daily that will be completely broken by the transition, not to mention that many businesses likely won't be as tolerant of that breakage as the average consumer will.

Nothing to do with English. It's about the Latin or "Roman" alphabet.

> The encoded value can change any time you re-compile your program, so you can't actually use it for anything where the value of the enum leaves the process that instantiated it

This is not true, iota is stable in its ordering. https://go.dev/ref/spec#Iota

> but most can also be smart jammed by various methods: spamming disconnect packets

At the very least for this particular case, WPA3 mandates Protected Management Frames (PMF) to prevent de-auth attacks on Wi-Fi networks.

The real practical reason, everything else aside, is that you’ll need IPv6 connectivity to reach IPv6 services as the world continues to adopt and transition over to IPv6.

Someone having a change of heart of their own volition is different to trying to make someone change.

If "IPv6 addresses are harder to type or remember" is the worst thing that happens during the transition to IPv6 then I'd call the whole thing an unquestionable success, given that there were numerous far more important things that could have gone wrong or ended up worse but didn't.

DNS exists to solve the problem of people not having to remember or type IP addresses. This is true regardless of whether you are talking about IPv4 or IPv6.

The aliasing scheme is called DNS.