Sunday, June 03, 2007

Death to Microsoft Exchange OWA - pisses me off.

I have Vista on a machine. Exchange 2003 OWA doesn't work properly with Vista. Microsoft, the pack of assholes, requires a patch to the exchange server OWA to make OWA work on Vista RTM. No one should have to patch the server simply to fix a broken fucked up client like IE7.

Anyways.

Firefox works great. Its not the premium client - but hey, at least I donut have to ask IT to risk breaking a working exchange server simply to make Vista work.

So now the main reason for tolerating exchange, OWA (outlook web access), looks like shit because I have to use Firefox to actually be able to reply to things - and Microsoft premium OWA requires fucktive activex, so that means opera and firefox have to look like shit.

Now here is the kicker.

You know how Firefox is super-awesome and saves half filled out forms and post boxes for you so in case of an accidental forward/backward or crash, its all there for you when you get back? Well IE7 doesn't do that shit, and somehow, OWA fucks Firefox from being able to work its magic in the reply box.

So I lost about 3-4 minutes work on a longer email reply.

All I have to say to Microsoft - give me a break. Microsoft can pull off vista, have a huge OS that works ok, a huge API, you name it. But they cant manage to keep libraries straight (WinSXS anyone? What a fuck-up), the 64 bit emulation sucks (WOW64 is a dirty, lame hack and Windows in 64 bit mode sucks, stuff like palm desktop doesnt even work right over USB), they manage to have an IE 7 that sucks worse than FireFox in every way but startup time (adblockplus - yes , stumbled upon, yes). Not even IE7Pro can help to unfuck how bad IE7 is, the Interix environment (Subsystem for UNIX-based Applications), get this, ar was fucked up because they named is ar64 or something, and the userland on Interix out of the box sucks hard - so hard, its hard to bootstrap the GNU toolchains - and what the fuck is with .NET frameworks. Why not just do the $JAVA_HOME thing and be done with it? Why is this stuff so melted and glued and stapled into the OS? Here is a directory with the VM and some classes and shit. Use if you want to.

This is all to say that the core, the David Cutler / DEC/VMS rip off part works great. The frosting sucks shit. Microsoft needs to pay more attention to not getting fucked by stupid shit. The kernel works great, now stop making shit flavored frosting and everything will be grand.

I wish microsoft had a super thin no login require portal to post stuff like this so they could improve this stuff. If I was gates/ballmer/whoever, I light a big fire under the product managers for transgressions like this - letting open-source stuff drastically out-pace Microsoft on usability.

1 comment:

vsync said...

Blogger sucks. Your HTML cannot be accepted: Tag is not allowed:
<blockquote> Your HTML cannot be accepted: Tag is not allowed: <tt> Your HTML cannot be accepted: Tag is not allowed: <var>


<blockquote>So I lost about 3-4 minutes work on a longer email
reply.</blockquote>

Always write long posts in a text editor to protect yourself.
Webforms suck.

<blockquote>But they cant manage to keep libraries straight
[...] the 64 bit emulation sucks</blockquote>

LOL. 64-bit binaries in "<tt>%SYSTEMROOT%\SYSTEM32</tt>", 32-bit
binaries somewhere in BFE, anyone?

<blockquote>and what the fuck is with .NET frameworks. Why not just do
the $JAVA_HOME thing and be done with it? Why is this stuff so melted
and glued and stapled into the OS? Here is a directory with the VM and
some classes and shit. Use if you want to.</blockquote>

<tt>$JAVA_HOME</tt> isn't a panacea. Then you have to have wrapper
scripts that set the variable and bundle custom VMs with your
product. Java Web Start is the least worst in a world where asshole
product teams create languages like Java and .NET that change
incompatibly from release to release, and asshole developers write
code that depends on bugs or undocumented VM behavior. With JavaWS you have an app descriptor that says what version it wants.
JavaWS has a trivial registry of installed JREs. If you don't have
the one required it downloads it for you. But yes, each JRE is
independent and in its own tiny directory. The only thing that would
be cooler is if files that are the same are hardlinked between
releases to save space.

<blockquote>The kernel works great, now stop making shit flavored
frosting and everything will be grand.</blockquote>

Yeah, when are they going to stop building poppycock on top of win32?

Shut up Raymond Chen. You want to learn how to do compatibility over
time right, look at FreeBSD. They could polish things more on the
system+ports stability front, but look at the "compatxx"
libraries. You can take a FreeBSD 2.2-RELEASE binary and run it on a
7.0-CURRENT system with no issues. Yet all the old cruft is in the
corner out of the way.