Posts Tagged ‘microsoft’

New Microsoft Online Services site not even close to valid HTML

Tuesday, March 4th, 2008

Heard of Microsoft’s new Online Services initiative? Thought you’d check out the site?

You should. It’s at http://www.mosbeta.com/, and it’s one of the worst recent web sites I’ve seen by a large company.

Firstly, the web page is completely invalid. It’s not just a little bit wrong, as many are – hell, this site fails validation, mainly due to a couple of widgets. But the Microsoft site is hopeless. It doesn’t even have a DOCTYPE, the most basic description of what the page is even supposed to be. Publishing a web page without a DOCTYPE is unfathomable in this day and age – this is a point that is hard to overstate, for those of you unfamiliar with web design. There’s no charset, no meta tags whatsoever. It’s utterly, and incomprehensibly, incompetent.

Secondly, the site contains a “navigation bar” consisting of what appear to be links to other parts of the site: “Microsoft® Exchange Online | Microsoft® Office SharePoint Online | Microsoft® Office Live Meeting”. These are not actually links but merely unclickable text. Again, unfathomable – why are they even there? The CSS file contains classes to style these list items if they are links, but they’re not. Elsewhere, CSS is used partially and inconsistently. Very strange.

Thirdly, the site makes heavy use of a non-standard and rare display plugin, “Silverlight”. The viewer is exhorted to install this plug-in not once but twice on the same page. The viewing areas are iframes served from a third party site – again, unfathomable. Why not use a common video format such as flash or quicktime – or at the very least an image preview if the plugin is not installed? This is easy to do. Adding to the strangeness, the div that surrounds the silverlight window is entitled “flashpiece”.

Fourth, the site makes use of rare, non-standard, outdated tags in strange configurations. Take this excerpt from the code:

© 2008 Microsoft Corporation. All rights reserved.  Terms of Use | Trademarks | Privacy Statement | Contact Us
This site hosted for Microsoft by Catalysis.

Forgive yourself if you had to go look up what

and

even were, I had to as well. wbr is an ancient tag meaning “insert break here if needed”, whereas

indicate to the browser that text included inside those tags should not be broken. The most recent documentation I could even find on these archaic tags was from 1999. Adding to the weirdness, I couldn’t find any reference to the notion that

even needs to be closed. XHMTL would require it to be closed – but wbr is not valid in XHTML anyway, not that the page is XHTML regardless, since there’s no freaking DOCTYPE! But there’s the XHTML-style self-closing


in there? Who on earth coded this website?

I could go on, but I think you get the idea. Microsoft’s new website about its online services platform – beta, no less, implying that it should at least be recently made – is an incompetently written, strangely archaic, and ugly to boot mishmash of invalid, outdated HTML, obscure plug-ins and links that go nowhere. If this is a taste of what’s to come from MOS, Google, and everyone else, can breathe easy.

Yet another comment on an MS blog

Tuesday, February 26th, 2008

Microsft always silently delete my stream-of-pure-hate comments on their blogs, so I typically copy them and paste them here.

Dear assholes,

OK, OK – I get it. Microsoft’s strategy is to release crashy, buggy Mac software years late with half the capabilities of the Windows version. I understand you want to make the Mac look bad, I really do. I hate the practise but I know why you do it – cold hard cash. I guess I’d have difficulty saying no to all those billions of dollars, too.

But geeze, I think you’re overdoing it a little these days. I installed the student edition for my friend. She uses it to start editing a document. Being a girl, and using a Mac, she doesn’t save obsessively like me. An hour into it, she finally saves. Office 2008 crashes and loses her work. I search for some kind of autosave file. There’s nothing. An hour of effort, and a lot of peace of mind, gone.

This shameful garbage should never have been released, and you’re the worst programmers in the world. I know I know – it’s (probably) deliberate. But I wish you’d understand that you hurt normal people, waste their time, lose their work, in your pursuit of that one more Windows sale – and boy, I hate you – all of you.

Right, I know this isn’t going to get past moderation, but I just wanted to tell one of you that. Seriously – I loathe you. You’re scum. Rich scum maybe, but scum all the same.

Either you’re unbelievably incompetent or just malicious. Either way, the world would be better off without you.

love,

Sho

I wonder if these fantasies of mass murder I always seem to have while contemplating Microsoft’s sins against me through the years are normal?

Hm, no actual death threats in this comment – am I losing my touch?

UPDATE: More MS-bashing:

Office 2008 is the product of four years of our lives

4 years of your lives? Maybe for the next 4 years you could enrol in a college course and learn how to program fucking computers properly.

It’s surprisingly cathartic, leaving nasty comments on blogs!

MS to force IE7 upgrade

Wednesday, January 23rd, 2008

Apparently Microsoft is going to issue a forced upgrade to IE7 to all XP users on February 12.

All I can say is: about fucking time. This is the first step to the final removal of the scourge of IE6, and the need to cater for its utterly fucked up rendering, in web design. Wonderful.

Jackass free for Jackasses using SilverLight

Sunday, December 30th, 2007

Pretty ironic choice of movie, considering most people I know would say you’d have to be a Jackass to consider using SilverLight for anything at all.

From here.

Never, ever use IronRuby

Wednesday, December 26th, 2007

So, you’ve heard of IronRuby? Microsoft’s implementation of Ruby on .NET. I’m hearing a bit of talk about it around the interwebs. Thinking of trying it out, eh?

Don’t. Ever.

Microsoft invented the technique we now refer to as Embrace, Extend, Extinguish. They tried it to Sun Java (MS JVM). They’ve tried it with Kerberos, and even today every web developer in the world is frustrated, wasting time trying to get around MS’s attempts to poison HTML and CSS.

A Leopard doesn’t change its spots. There is only one conceivable reason for Microsoft to implement another language on its own platform, and that’s that it sees it as a threat and wants to kill it. First, make a really good implementation! Fast, easy, Visual Studio! Next, “improve” it – on Windows only, of course! Third, we’re using MS Ruby++ and we’re fucked.

Run a million miles from IronRuby. If you assist in giving it traction, if you feed it any attention at all, you’re just making the world a worse place for all of us.

And one would be advised to think very, very carefully before adopting any technology – or, just as importantly, any *implementation* of a technology – that is not open source from top to bottom. GPL is best but MIT will do.

May MS never stain the history of computing again…

81 Windows Updates

Wednesday, September 26th, 2007

A mere 81 Updates

Decided to check out VMWare Fusion today, in the lame hope it supports half-life. Went for a new install of XP “Free Edition” and did a double-take at the 81 updates it wanted to install! And that was after it had already rebooted once after some earlier, unknown number of updates. Ridiculous, but at least it can do them all together.

In other update news, our beloved WordPress has moved to 2.3, so I’ve dutifully updated that, too. The tagging system is very welcome indeed – but it seems we now have tags AND categories. Which one should I use? Regardless, I relish the opportunity to henceforth pollute the internet with gratuitous slashdot-style joke tags on everything I write.

There was some controversy about the new WP update system, sending identifying information to wordpress.org, but having examined the data sent it seems reasonable to me. If you don’t trust WP.org, after all, maybe you shouldn’t be running WP. Oh, wait …