Common knowledge but not the sort that is actually true.

https://www.discovermagazine.c...

But but but

Just use SDL! WxWindows! MFC if you must! No need for raw Win32!

Which means the real problem is probably around writing C/C++.

You kids get off my lawn etc.

whenever a taxpayer funded operation is, ahem, railroaded into poor planing, cost overruns and all the other excessive wastage. Burn that fucker to the ground and walk away from it. It's not worth another cent.

I bought eero since I was excited to fix my hard-to-cable apartment problems. They advertised on their front page "never reboot your router again!".

When I got them they failed to work well, and cabling the back-haul led to even worse performance. When you log into the support system, the first suggestion is "reboot your eero".

Great work, guys. So I returned it and got Plume and it kicks way more arse.

FWIW, eero doesn't say any more that you'll never reboot your router again, but it's still the first item in the trouble shooting guide. I'm not sure I've ever had to reboot any Plume nodes.

It needs a reference to the errata from the vendor. Future revisions may need to tweak code flow and understand exactly what this is trying to achieve.

These aren't lies.

Low trading volume in the stable period means a lack of interest in anything except the speculation:

https://data.bitcoinity.org/ma...

That's not healthy for any security.

I read this as "dull" referring to, very little trading volume:

https://data.bitcoinity.org/ma...

ie. nobody cares unless it's going up. If there was a decent trading volume when it was stable, that would be an excellent thing for bitcoin. That's not what's been going on.

... wake me up when they charge the telcos for every robocall they don't filter. That will make a change.

I think you're confusing the smartest users with the users that claim they're the smartest. The smartest users understand it just fine.

Have you read the security guidelines for the T2?

https://www.apple.com/mac/docs...

If you read my original post in this thread, I'm specifically asking for proposals how to do that. In all my security work I don't know how to do this. You seem to know it can be done, so please, do share. Or go out there and build a better product and make mint. I'd love for someone to demonstrate how it can be done, but proof by assertion isn't.

The whole security model of the T2 chip prevents it. You can't get your data or authenticate your password without the chip. Users are guaranteed to notice if you mess with it. If you fail over to "working with some detail", you can use the working side of it to hack around the detail.

Do you have a proposal for how to separate these two? What's to stop a malicious change from masking this boot warning? The security point of the T2 chip is well documented by Apple. The conspiracy theories are the same for the iPhone, though. Bottom line: You can't make a secure system if you allow random modifications. The tiny market share of people who are going to tweak their devices isn't worth forsaking real security for everyone else.

If you really like your phone the way it is and are worried about slow downs, don't update. It's that simple.

More features == more bloat == slower than the previous software on the same hardware. This has been true since the dawn of computing.

Like really, how exactly is this a legit question?

... or have I just been asleep at the wheel while it changed slowly?

This kind of BS seems like the norm nowadays. Yawn.