You must be new here, to think that editors edit! :)

But by no means are they alone.

If I had mod points I'd mod you up. Let Python 2 die, already.

Oh, it'll be simple: that 8K screen you want to use will require a USB4 v2.0 revision 19 errata 27 cable. No problem!

Complexity... check! Every time my iPhone reboots it throws a "Failed to send message" dialog for a 4,000+ day old message, but you can't actually do anything with that dialog to get to the problem message to delete it or somesuch. Short of deleting the entire conversation history for that contact.

Good luck getting the toothless ACCC to action that. Australia's just a market for last year's equipment that didn't sell in the USA and EU, and the ACCC has neither the power nor the apetite to actually protect consumers by pursuing companies that exist outside of Australia.

Which one? The original Enterprise actually had switches and levers and such.

If it's a DNS issue as suggested could be interesting to see what requests the printers are making and why they'd not work when accessing an internet-connected DNS server.

Vodafone already track the mobile device IMEI/IMSI/MSISDN for customer billing purposes. Likely this is just a poorly obfuscated data feed to advertisers based on that information but also including their current public IP address for data matching. i.e.: changing the Android/iOS ad-tracker IDs won't have any effect because they're too far up the stack, but VPN connections will still defeat it because the client IP presented to origin web sites will be from the VPN endpoint.

Totally agree. Until Apple starts forcibly locking out older devices and apps I don't need anything more sophisticated than my current iPhone 6 Plus for SMS, email and PagerDuty alerts.

And modern batteries are awesome, too. I just had the battery replaced recently and now only need to charge the device maybe once per week instead of being tethered to a charger like it was previously.

If we accept that the laughably bad label should be applied to them then what does that say about the companies that they've breached so far?

It's bad practice, yes. But it still happens. Just like some developers create and maintain systems that persist plaintext password credentials.

It's probably way higher than 90% and it's been that way since we moved on from machine code to assembler.

Also, processes in the "?E" state aren't even displayed in Activity Monitor.

No, kill -1, kill -2, kill -9, kill -s KILL, kill -s QUIT, etc., have no effect on processes stuck in the "?E" state because they're already trying to terminate - they are probably stuck in an infinite loop/wait somewhere and don't respond to signals. That's why you have to power-cycle the computer to recover, because the processes can't be killed to allow a restart/shutdown to complete.