> The underlying technologies of the Web are in constant evolution and we cannot keep TitanPad up to Web standards.
Is the web itself really changing in backwards-incompatible ways that would break a web application like TitanPad? That's disappointing if so. I wouldn't want the web to evolve in such a way as that documents need to be actively "maintained" or else risk becoming unintelligible or unusable. The value of having standards is diminished if they are continuously moving targets.
In contrast, I understand exactly why server infrastructure faces a large challenge in this area. I'm sure they built their "legacy" service on version 1.0 of something, which ran on version "X" of something else, and now that platform's major releases focus on version "Y" and beyond (and by the way, version 1.0 of something no longer builds on version "Y" of the platform), and the platform team has recently announced "X" has reached end of life and will stop receiving security updates. And so on, and so forth.
Bit rot. It happens with system software. Is it happening to the web too? I am distinguishing between the server software that renders the HTML/CSS/JS content, and the compatibility of that content to be displayed and interact correctly in browsers.
Could this be referring to users expecting their tools to be up to snuff with giant tech corporation level? A website from the 90s will still work today but would be laughed at by a lot of tech savvy users. If that is their market, I could see the difficulty.
Unless you're using non-standardized features, the web is supposed to be backward compatible. I can still look at pages written in the 90s just fine.
The problem comes when you start using prefixed css keys or unstable / non standard features. Since those are sort of "WIP features", it should be obvious that they need to be maintained.
This blog post makes no sense. The first half sounded reasonable- lack of funding for maintenance and scaling make it difficult to ensure the servers are up to date from a security perspective and service level... but losing flash has been the only significant backwards break that I'm aware of in the past few years. The second half seems really off.
Sure, a few browser vendors have played with introducing new, non-standard features in the hopes that they would become standard such as native observers and web SQL, and backed down before they were standardized. But, there's no reason to think that the HTML/CSS/JS that they're using now will stop working at anytime in the remotely near future, since the site seems to work fine on multitude of browsers now.
[+] [-] Pyxl101|9 years ago|reply
Is the web itself really changing in backwards-incompatible ways that would break a web application like TitanPad? That's disappointing if so. I wouldn't want the web to evolve in such a way as that documents need to be actively "maintained" or else risk becoming unintelligible or unusable. The value of having standards is diminished if they are continuously moving targets.
In contrast, I understand exactly why server infrastructure faces a large challenge in this area. I'm sure they built their "legacy" service on version 1.0 of something, which ran on version "X" of something else, and now that platform's major releases focus on version "Y" and beyond (and by the way, version 1.0 of something no longer builds on version "Y" of the platform), and the platform team has recently announced "X" has reached end of life and will stop receiving security updates. And so on, and so forth.
Bit rot. It happens with system software. Is it happening to the web too? I am distinguishing between the server software that renders the HTML/CSS/JS content, and the compatibility of that content to be displayed and interact correctly in browsers.
[+] [-] sb8244|9 years ago|reply
[+] [-] roblabla|9 years ago|reply
The problem comes when you start using prefixed css keys or unstable / non standard features. Since those are sort of "WIP features", it should be obvious that they need to be maintained.
[+] [-] zdragnar|9 years ago|reply
Sure, a few browser vendors have played with introducing new, non-standard features in the hopes that they would become standard such as native observers and web SQL, and backed down before they were standardized. But, there's no reason to think that the HTML/CSS/JS that they're using now will stop working at anytime in the remotely near future, since the site seems to work fine on multitude of browsers now.
[+] [-] tjmehta|9 years ago|reply
[+] [-] unknown|9 years ago|reply
[deleted]