This is so true. I've always had horrible usability issues with YoutubeTV, especially when using with a Chromecast. I was always shocked that the app/website had so many bugs, the same type of bugs OP is talking about. It was literally the buggiest piece of software I've used in the past few years. The person I share the membership with never ran into these bugs somehow, so seeing this comment really makes me feel better about my experience. Still scratching my head about how so many bugs could show up in production for so long. I'm guessing severely inadequate testing.
You misunderstand some of the nuances of PoS that make it secure. Along with slashing, there is a period of time during which your staked funds are frozen, where they are unspendable and unsellable. This period is supposed to be long enough such that all nodes sync at least once during that period (think on the order of weeks or months). So if you try to create an alternative history during that period, your funds are slashed (since you couldn't have sold them). And if you try to create an alternative history after that period, everyone will know you're lying, since that portion of the history you are trying to recreate has already been finalized.
Sure, if you get a majority of stake in the network, you can create alternative histories. But, as others have pointed out, this is much more difficult than a 51% attack in PoW.
The text "At most, all slashing does is makes Step 3 take more time." makes it pretty clear that I understand that completely. If you can suggest a revision to my comment that makes it more clear I'd be happy to mae it.
> has already been finalized.
This is presuming the existance of an external consensus mechanism.
I wonder if this depends on what language you develop in. I've been working on C++ teams for the past few years, and I don't witness any age bias. If there is an age bias, it's against younger engineers, because usually older engineers are much better at C++. The classical image of a programmer is still highly respected on every team I've worked on.
Also, I am an ex division 1 wrestler, and pretty muscular, and I always felt my physique actually worked to my detriment in interviews; I take a lot of steps to not come off as a jock/meathead. I wear glasses to make myself look more like a programmer, than an athlete. Maybe there is a difference though between being in shape, and being a division 1 wrestler.
Or maybe this is mostly a west coast/silicon valley thing. I've been working out of NYC mostly. Regardless though, this article really does not resonate with my experience as a software engineer.
