7 ms·

The point is that Microsoft has been terrible at this since 1999. They consistently do their own thing instead of going with standards, and they are always beh

by mmazing 16y ago

The point is that Microsoft has been terrible at this since 1999. They consistently do their own thing instead of going with standards, and they are always behind the curve. They seem to be trying to catch up with standards but have been unable to make any sort of impressive progress. To be honest, if they've put five years into it and are still so far behind, they need to fire some people. Does anyone actually consider IE to be a valid contender for browsers? Personally, I gave up years ago.

acabal 16y ago
Exactly... you, and every other serious developer. That IE is garbage is obvious to anybody who's done web development for more than a month. So why is Mozilla even bothering with these technical articles? IE lost to developers years ago, and IE9 won't change that. I guess I'm just confused as to why this article, and the other similar ones from this past week, are even news.
- fady 16y ago
  Not news, but pressure and the fine art of telling the truth. It's to keep MS in check, transparent. In my opinion.
- rbanffy 16y ago
  > So why is Mozilla even bothering with these technical articles? Because they need to educate the clueless who decide to make their internal web applications IE-dependent. Making an internal web app IE-only is one of the most common and crippling mistakes corporate IT makes.
rbanffy 16y ago
> To be honest, if they've put five years into it and are still so far behind, they need to fire some people. You are assuming Microsoft wants to adhere to standards. I find it more likely their strategy is to fragment the market because the day web applications become the norm, as opposed to desktop applications, they become OS-independent and Microsoft will have its main advantage (the Windows software ecosystem) negated. They won't allow that.
- nailer 16y ago
  I'm not sure MS are that dumb §. They know apps are moving to the web, and they want to be sure that Google and Apple don't control that experience. They know IE9 is a bit crap, and they'll release an IE10 with proper history API, gradients, transforms and the rest when they can. They'll have a working web office someday too. In the meantime they'll pimp IE9, the Office 'web apps' and other substandard ones to their customers until their kickass version 3 products come out. § Withstanding there are probably a few people in MS who really still love fat client.
- blub 16y ago
  > the day web applications become the norm, That will never happen. Web apps have critical issues that can't be solved even by HTML8.
  - rbanffy 16y ago
    Care to explain those issues?
    - blub 16y ago
      The issues are quite noticeable for someone that isn't heavily invested in web apps. Most of HN is - and that's why they prefer to ignore them. But let's look at the market... Have web apps displaced desktop apps? No. Have they displaced mobile apps (as per HN mantra 90% of iPhone apps could be web apps)? Not even close. Now why is this? It's because web apps offer a significantly poorer user experience across the board. * with all the progress that's been made in performance, web apps are slower than native apps and will continue to be. There is only so much that you can offload from JS. * web-apps don't have access to the platform's entire range of graphics capabilities, including standard widgets, animations and so on. * web apps don't have access to special platform functionality such as GPS, sensors, camera, etc. Furthermore, the biggest mobile players have all started to invest in native mobile apps to the detriment of web apps. Including Google. It's in their interest to lock-in users to their platform, even more so since Android became a major player. These issues can be worked around eventually (maybe). The core issues with web apps can't be worked around: 1. Web apps are using a text-transfer protocol with a pile of hacks on top to make it stateful. To this day engineers are still working on solving this problem (web sockets, web sql, etc). They can't solve it. 2. One does not own web apps, one merely rents them.
blub 16y ago
As a FF user, I wish they would adopt the same security improvements that IE has, instead of writing lame posts about canvases and shadows. i.e: automatically running under a restricted account and tab-as-process.

by mmazing 16y ago

acabal 16y ago

Exactly... you, and every other serious developer. That IE is garbage is obvious to anybody who's done web development for more than a month. So why is Mozilla even bothering with these technical articles? IE lost to developers years ago, and IE9 won't change that. I guess I'm just confused as to why this article, and the other similar ones from this past week, are even news.

fady 16y ago
Not news, but pressure and the fine art of telling the truth. It's to keep MS in check, transparent. In my opinion.
rbanffy 16y ago
> So why is Mozilla even bothering with these technical articles? Because they need to educate the clueless who decide to make their internal web applications IE-dependent. Making an internal web app IE-only is one of the most common and crippling mistakes corporate IT makes.

rbanffy 16y ago

> To be honest, if they've put five years into it and are still so far behind, they need to fire some people. You are assuming Microsoft wants to adhere to standards. I find it more likely their strategy is to fragment the market because the day web applications become the norm, as opposed to desktop applications, they become OS-independent and Microsoft will have its main advantage (the Windows software ecosystem) negated. They won't allow that.

nailer 16y ago
I'm not sure MS are that dumb §. They know apps are moving to the web, and they want to be sure that Google and Apple don't control that experience. They know IE9 is a bit crap, and they'll release an IE10 with proper history API, gradients, transforms and the rest when they can. They'll have a working web office someday too. In the meantime they'll pimp IE9, the Office 'web apps' and other substandard ones to their customers until their kickass version 3 products come out. § Withstanding there are probably a few people in MS who really still love fat client.
blub 16y ago
> the day web applications become the norm, That will never happen. Web apps have critical issues that can't be solved even by HTML8.
- rbanffy 16y ago
  Care to explain those issues?
  - blub 16y ago
    The issues are quite noticeable for someone that isn't heavily invested in web apps. Most of HN is - and that's why they prefer to ignore them. But let's look at the market... Have web apps displaced desktop apps? No. Have they displaced mobile apps (as per HN mantra 90% of iPhone apps could be web apps)? Not even close. Now why is this? It's because web apps offer a significantly poorer user experience across the board. * with all the progress that's been made in performance, web apps are slower than native apps and will continue to be. There is only so much that you can offload from JS. * web-apps don't have access to the platform's entire range of graphics capabilities, including standard widgets, animations and so on. * web apps don't have access to special platform functionality such as GPS, sensors, camera, etc. Furthermore, the biggest mobile players have all started to invest in native mobile apps to the detriment of web apps. Including Google. It's in their interest to lock-in users to their platform, even more so since Android became a major player. These issues can be worked around eventually (maybe). The core issues with web apps can't be worked around: 1. Web apps are using a text-transfer protocol with a pile of hacks on top to make it stateful. To this day engineers are still working on solving this problem (web sockets, web sql, etc). They can't solve it. 2. One does not own web apps, one merely rents them.

blub 16y ago

As a FF user, I wish they would adopt the same security improvements that IE has, instead of writing lame posts about canvases and shadows. i.e: automatically running under a restricted account and tab-as-process.