4 ms·
> Another, more relevant side of this is that it's not going to be possible for people with web servers to just let them sit. This problem goes far beyond just
by bartread 6y ago
> Another, more relevant side of this is that it's not going to be possible for people with web servers to just let them sit.
This problem goes far beyond just HTTPS, and here's a small example. I have a side-project, which is a website where I post versions of old arcade games I've created. Now I can go months without deploying any changes but despite that things just keep breaking from time to time.
Without digging through my GitHub issues here are three examples:
- Web audio support at different times in both mobile and desktop browsers (now fixed)
- Motion control support via accelerometer (now fixed)
- Full screen support (still not fixed, although bizarrely works fine on iOS which has no explicit full screen support but will enter full screen automatically when you reorient your device)
The fact that you can't simply deploy code and have any realistic expectation that it will continue to run without supervision or tweaking for even a few months is INCREDIBLY ANNOYING.
People need to stop tweaking APIs and the behaviour backing them, and breaking compatibility all the time.
- gambler 6y agoThis is, in reality, the biggest problem. A lot of modern technologies have built-in assumptions that most people promoting them didn't ever think through. "Everything will be updated all the time, everywhere" is one of those assumptions. "Security" people who yammer about MitM attacks don't give the slightest fuck about that other side of the coin, because that's not what they're paid for. However, a lot of these assumptions have costs that will compound over time. What is the cost of constantly loosing old media, for example? What is the cost of perfectly good consumer devices being rendered unusable via infrastructure updates? What is the cost of constantly rising complexity? This is not discussed with any level of honesty.