3 ms·
I'm sure this is causing some people on HN real, excruciating pain. However, this application was built according to the standards of its day, and I don't know
by tekklloneer 10y ago
I'm sure this is causing some people on HN real, excruciating pain. However, this application was built according to the standards of its day, and I don't know that it's so unreasonable to expect them to hire at 6 figures a developer for no "real" benefit.
And, the "IE" of today could be the "Chrome" of tomorrow. I don't like this situation (does anyone?). I wonder if for CRUD apps like this, it'd be beneficial to have a limited subset stack guaranteed for long term ABI compatibility, similar to CoreOS for binary runtime environments?*
* of course, this is just one of those many "wouldnt it be nice to have" things.
- leephillips 10y agoIf the "application" (a web site) were built according to standards it wouldn't matter what browser we used to access it.
- allendoerfer 10y agoI have built websites when 6 was the latest IE version and can assure you, that this website was not built according to the standards of its days
- xbmcuser 10y agoIt was not build suing standard that's the reason its not compatible with today browsers