Linked by Thom Holwerda on Tue 10th May 2011 08:19 UTC, submitted by porcel
Permalink for comment 472666
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
More News »
Sponsored Links



Member since:
2009-08-18
Which was nothing to do with IE6. There was nothing else worth developing for at the time.
As for SVG ... I never seen it used, I never need to use it on the web ever. I never had a use case where I've needed to use it.
Most websites their code doesn't even pass validation (I run a firefox plugin that validates my markup as develop so I can see instantly whether a website passes). So it nice that we have cool things like SVG etc ... but most
The lack of compatibility was vendors not using the APIs.
I have plenty of programs from the Win98 era that work fine on Vista and 7, wait a sec there is one that doesn't work ... Visual Studio .NET 2003 ... which isn't supported anymore.
I would like to see how many MacOSX programs and Linux programs that require a GUI you could still run from 2004 on modern systems. I guess it nowhere near the number that are working on current versions of Windows.
It isn't decent. It kinda good enough most of the time, but OO is miles behind even Office 2007.
Nobody gives a shit about the openess of document file format except the GNU brigade.
Most businesses roll out updates to office company wide so everyone is running the same version, so it becomes a moot point in 99.9% of circumstances.