UnoriginalGuy
Joined 14 years ago
Joined 14 years ago
I feel like throwing everything behind a VPN and pretending it is secure is a crux.
Several famous break-ins over the last ten years have hypothetically been on the inside of that wall.
Better to isolate services from each other limiting cross service jumping, than to build security around a single point of failure.
We added an iPad and tried to purchase something, but the only card on file was long since expired and thrown away.
But in order to verify the account we had to enter the card's digits, which we did not have, and we couldn't add a new card because we hadn't verified the old one.
In other words we were stuck. Had to contact Apple support. Took several days to resolve.
I guess it is part of becoming a more professional industry. It we did add an Easter Egg it would likely need a spec, docs, owner, and code review.
They were still successfully prosecuted though. And AT&T received no punishment.
When a company says jump the USG asks how high.
It being "open source" or not kind of misses the bigger picture. If Google had any interest in AMP being a web standard they would have sent the spec out, and helped fund a neutral org to run it.
Boeing's procedure only works if you catch it quickly. If you let MCAS trim the aircraft too much it is difficult to recover, particularly at low altitude.
Have you checked your chair/table height, monitor height, and are you placing both feet on the floor? You might be able to mitigate this without buying things.
Blizzard entertainment does half client half server hashing which is rather clever, one of the few examples where client hashing makes sense.
After they were patched they've been stable as a rock and "just work." But it has felt like Microsoft shipped half baked hardware.
Plus while Windows 10 is stable, it feels like a moving target with large feature patches that also don't always feel fully baked.
In-spite of the above I really like Microsoft's hardware and oddly would recommend it. It is definitely heading in a good direction, but isn't up to the height of Apple's "just works" period (which I don't believe we're still in).
I'm sure in general Microsoft would love to scrap VB in Excel but there's too many companies that run entire areas of business on it, or the whole business itself.
It is the typical legacy/back compat problem. Python or even Powershell would be a vast improvement, but you're going against billions in sunk cost/skills/knowledge.
VB.Net was slowly losing popularity, VB in Excel isn't.