Reality: to most audiences the toilet (and sanitation technology in general) is just a punchline, and the show's producers know that. That's why. We're getting what we pay for, and we vote with our eyeballs.
The proposed sealed toilet seat[0] is honestly a good idea, and it's a sensible implementation of the concept. I wish them luck. The TV segment felt oddly like a modern-day version of when John Snow said that maybe we shouldn't drink cholera water, everybody. :-\
So you're telling me that the next GitHub outage could take out my dev environment and give me an afternoon off? Time to convince management that we need to switch to Codespaces!
You say “though” as if it absolves them. If they break basic requirements of a Git host like fetch and push while working on this extra feature that’s on them.
There are different risks, but there is not necessarily more risk. Does Codespaces have lower or higher than the availability risks of your current environment?
I’ve had corporate laptops get BSOD’d because a sysadmin pushed a bad GPO rule that worked fine on 99% of their clients but butchered the developer laptops.
Another fun one was when an org was rolling out CarbonBlack on all endpoints and decided to block all Java. Because apparently Java in the web browser is a security threat. They blocked 30 devs Java runtimes as a result. So there was an entire afternoon wasted for those guys.
To a corporation the risks of GitHub being down might be ok. Plus this will drastically increase on boarding devs to an existing project.
If you've never had these issues, this product is probably not for you.
The question is, how much time do you spend on dev environment issues per year?
When I was at one of the FAANGs, our dev enviroment took about 1hr to install, and you had to redo it everytime you switched platform / version (about every week).
We spent ~50 hours per year managing our local dev enviroment. probably more in reality.
> The question is, how much time do you spend on dev environment issues per year?
Definitely not little. But at the same time, I usually learn a lot about how stuff works during that. Which I like to think makes me better at helping other people debug weird shit.
In the context of my comment of having a free afternoon off - having my local environment messed up means that I'll need to spend my afternoon fixing it instead, whereas having Codespaces go down is essentially an announcement to the entire engineering team to go take the afternoon off as there's nothing we can do
I believe that in this case it's simply convenience/laziness to have a single notifications codebase across both operating systems? That and Windows didn't have native notifications when it was first developed. Not that it excuses a big chat application from MS behaving this way, just saying that they probably didn't deliberately choose to re-implement notifications just because they didn't like the OS ones.
Windows has had balloon notifications since Windows 2000. These show up as toast notifications by default in Windows 10, so compliant applications would be transitioned automatically.
Some software also presents that in the settings as the choice between "native notifications, which don't have as many features" and "custom notifications, which have all bells and whistles". And the default of course is the one with more features, not the one that respects your settings. I think Mattermost was where I've seen that distinction.
This is what happens in an Electron world. Lots of experts around to make some JS+CSS notification boxes because they keep reinventing those for every SPA anyway, but.. integrate with the native system notifications? They don't even know how Electron works so how would they begin to do any of that.
I'm building a web app to play an icon clicking/hunting game based on Dota 2. It has been pretty fun working with Web RTC and web sockets, as well as doing some cool stuff with React hooks and PWAs, and I'm planning on "releasing" it soon.
