
The problem with Flash is legion, from SEO and accessibility issues, to a terrible IDE, and a completely convoluted development model. Personally, I do think there is that "New SDK", but it's been around for ages. Stuff like that isn't a small thing to overcome. That's doable in IE, but not allowed in Firefox because of security settings. He kind of glosses over the numerous problems (like the copy/paste thing), and doesn't realize quite the problem that is there. Microsoft won't dramatically improve their rendering engine, because they're afraid of backlash from the millions of sites that are hooked on their broken model. How long has IE 6 been the dominant browser, even with IE 7 available? is still on dial-up, and those speeds are dropping fast, but not quite the same as doubling speed every 18 months (the bandwidth at the Diamond Bar office is a huge testament to that).Īlso, he grossly overestimates the browsers changing. The reason why the AJAX phenom is different is because 1.
MICROSOFT LOTUS 123 PC
The problem was they spread themselves too thin, not focusing on the core product, and wasting too much time on performance, without realizing just how quickly the PC market was changing. First, I don't think Lotus' problem was that they didn't add enough features. I have to disagree with Joel about his observation in quite a few areas.

Luckily, we are making strides, and I think we're improving a lot all around.
MICROSOFT LOTUS 123 CODE
And most features, while "cool", are many times not worth the effort that results from the added code download size, code complexity, bugs, etc. The problem is, it's always way easier to actually add a feature than it is to remove it. I'm all for needed features that are truly needed, but I think Liferay has a history of feature creep. I think we need to make Liferay follow the plugin paradigm, and even start removing features where we can.

I agree with your other post about streamlining Liferay down, which is something I've been pushing for since I started. I disagree with Joel on the whole feature thing, at least as regards feature QUANTITY goes.

Not small, but definitely not bad for a portal that is incredibly AJAX and JS heavy. Actually, when you take into consideration gzipping, the file size of the Javascript is around 80k.
