10/04/2005 10:39:00 PM - Mozilla Online Services - Uncomplete
Usually when I write a diatribe about UMO, someone will jump in and complain about me in one way or another.
UMO sucks. Well, no. Its pretty damn functional. But its very stagnant in terms of code. I don't fault any of the people that have worked on UMO so far. Not one bit. Actually, I blame mozilla.org. Or MoFo. I'm not sure which is actually responsible for anything. Or are they the same. Eh. No matter. Whoever the PTBs are, they seem to have let UMO fall off the map again. Thats the third person "in charge" of UMO so far.
Actually, UMO 2.0 did start making progress for a while. But then something more important came along.
There's enough Moz people working at Google now. How about they find some php programmers there to work on UMO? Or will we become days away from Firefox 2.0 when someone realizes that things aren't where they should be and they'll rush things again.
Downplaying critical/security updates and a revamped software update system to improve AMO would not have been prudent.
Without the core update system, the application on a user's machine could easily become out-of-date, non-secure and consequently break addons as a result.
I believe that MoFo is doing what is right for the largest percentage of users, and that's ensuring that updates will be delivered promptly, reliably and efficiently.
It sets a foundation that lets us do those other things we love, which is playing with extensions and themes to modify an already robust, secure and up-to-date product.
Don't despair, we'll get there.
Perhaps when I graduate and have a job, my time may workout differently.
