True!
The day publishers start developing games (not just porting) the user based for desktop linux will increase exponentially. That would be the best challenge to the other monopolies on the desktop.
.. Linux
Fund SCO to prove Linux belongs to them. Then have them hand linux over so that it can be branded as the much awaited next genration MS platform:)
There are several quirks of IE that web-app developers use to make fancy interfaces that work just with IE. There have been some comments on extensions, appletx, active-x etc. Some of these are certainly a problem. But some basic DHTML/scripting interfaces are specific to IE too. From experience, I have seen that enterprise web applications that make heavy use of scripting sometimes break the cardinal rule of being "browser-independent" simply by making use of these. Some of the examples of the same are usage of document.all etc that are non-standard and are specific to IE. Most of these are inadvertent and probably occur because web-app developers simply test their work on just IE ? From all the applications that I have seen, it is this folly that restricts web-applications from being cross browser compatible.
Slashdot Mirror
*Except One*
True! The day publishers start developing games (not just porting) the user based for desktop linux will increase exponentially. That would be the best challenge to the other monopolies on the desktop.
.. Linux Fund SCO to prove Linux belongs to them. Then have them hand linux over so that it can be branded as the much awaited next genration MS platform :)
There are several quirks of IE that web-app developers use to make fancy interfaces that work just with IE. There have been some comments on extensions, appletx, active-x etc. Some of these are certainly a problem. But some basic DHTML/scripting interfaces are specific to IE too. From experience, I have seen that enterprise web applications that make heavy use of scripting sometimes break the cardinal rule of being "browser-independent" simply by making use of these. Some of the examples of the same are usage of document.all etc that are non-standard and are specific to IE. Most of these are inadvertent and probably occur because web-app developers simply test their work on just IE ? From all the applications that I have seen, it is this folly that restricts web-applications from being cross browser compatible.