Slashdot Mirror
Gates' Replacement says Microsoft Must Simplify
Javaman59 writes "This article in The Australian newspaper describes the background and the agenda of Ray Ozzie, Bill Gates'
replacement as chief architect at Microsoft. The creator of Lotus Notes, he's
a high-calibre technologist.
From the article: 'Ray's a programmer's programmer .. He's much closer to an uber-engineer, whereas Bill hasn't been a programmer for a number of years.'
Ozzie is also driving Microsoft to simplify its software: 'Complexity kills .. It sucks the life out of developers, it makes products difficult to plan, build and test, it introduces security challenges, and it causes end-user and administrator frustration.' He's not the only brilliant programmer in the world, but he does have Microsoft's resources behind him."
Notes is a nightmare like Emacs is a nightmare-- the interface's crap but those who know the rationale behind the interface (or can look beyond the not-so-pretty face) will discover a remarkably powerful scriptable workflow engine that incidentally is also an email client. I have personally razzed Notes before (I used it for my email for 6+ years and had to end up learning how to program it to make it bearable) but in the end I do appreciate the amount of flexibility the environment gives you. Add to that the number of good ideas Notes pioneered in the early 80s, and it's no wonder a lot of Notes folk end up like Lisp programmers, muttering 'heh, we did it first' whenever any workflow/unstructured-data 'innovation' is announced.
Back on topic, it's common knowledge among the Notes community that Ozzie was responsible for the Notes engine and backend, not the interface (that was Lotus standards, and later IBM's) -- given that I think he deserves a lot more credit than you give him.
Go somewhere random
Mr Gates himself was once moved to declare Mr Ozzie "one of the top five programmers in the universe" and revealed that he and Mr Ballmer had wanted for more than a decade to persuade him to join Microsoft. To the outside world, Mr Ozzie's programming prowess is known mainly through Lotus Notes, the e-mail and collaboration software that he masterminded, which was acquired by IBM in 1995.
And we know that if BG says it, it must be true!
There's no doubt that Ozzie has some programming credit and no one will argue (I'm going out on a limb here) that Lotus Notes was genius back in the day, pre-Internet-as-we-know it. But despite his desire to streamline programs, reduce the bloat, and re-establish some respectability, he's not going to get very far. First, he'll have to lock horns with Ballmer and dodge chairs. Then he'll find that Microsoft has become so mired in its own muck that spurring the current crop of programmers who've been indoctrinated in the "Microsoft Way" will prove nigh impossible. He will also have to live in the shadow of BG, who despite the announcement, isn't really going anywhere, and will be haunting the halls of Redmond like some anti-Obi Wan.
I give him 18 months before he resigns in frustration.
GetOuttaMySpace - The Anti-Social Network
I've developed with Notes for 11+ years (I know I feel sorry for me too), and while the UI is gruesome, and it has plenty of quirks, its great for rapid solution development. You can do almost anything with it, fairly quickly. If anything, the reason I think people hate it so much is precisely because it allows just any wanker to come in and crap out a solution without thinking about it. Its WAY to flexible for anyone but experienced developers to do anything reliable with it. 99% of the headaches in a Notes environment are due to admins or developers setting up stuff they don't have an idea how to really do...or like my company, we have 2000+ deployed seats, hundreds of databases all developed by different people, all supported by ONE guy, part time about 10 hours a week. Wow, no wonder theres so many problems.
If anything, its the poster child of why you *shouldn't* make it too easy for people to develop solutions...and why a solution that does everything does none of it *really* well.
1) 11 billion or so shares issued over the years. The significance of this fact seems to elude most people for some reason.
2) Stock in slow decline for over five years
3) Revenue growth continuing to slow
4) open document format movement continues to spread across the computing world
5) Office software has reached a saturation point for features
6) Linux continues to step by step become the de facto choice for computing companies to base their hardware on
7) Attempts to create new revenue streams have been failures like the Xbox/Xbox 360 marketplace disasters
8) Can't attract/keep good employees now that the stock is no longer going up
9) Can't keep current employees happy - it doesn't matter how you treat an employee if their options are going up dramatically in value every day and that hasn't been the case at MS for many years
10) Years of poor engineering choices are making progress nearly impossible for their OS
Taking over a company that is in its decline is no fun.
It's just extraordinary, there's nothing MS won't do to shoot itself in the foot. The only thing they've done since late 2000 that has been remotely constructive has been .NET, and even then it's worth remembering how despite having an excellent product, they rebranded it and spun it and confused the issue until not one manager in ten had any idea what it was. ".NET is XML," remember that? That's MS on marketing, that is.
The popular perception is that they excel at marketing rather than technology, but the reverse is true. They have top-notch geeks and project management, and then above that, suddenly, there's a layer of utter leaden idiocy that -- well, the chair thing. The chair thing.
It seems so obvious, from outside, that there's a layer of deadwood generic-mulitinational-parasite-management people gradually crushing the company and that they need to put someone up there whose focus is on delivering actual value to actual people. And I think a little bit of that awareness has reached MS itself (I mean the MS boardroom -- it's an accepted fact most other places). And so they decided to appoint Ozzie, because he's handled a real product that involved real software.
It's weird how being a tiny bit right, actually makes the decision so much more glaringly wrong. Of course, I've worked with Notes in some detail (anybody else remember the thing where if the server is too fast, the timestamp on everything starts gradually moving forward, becaues the timestamp is used as a unique ID? It was on thedailywtf.com a while ago) and so to me it's extra specially glaringly wrong.
Whence? Hence. Whither? Thither.
The next build of Windows will not be fully backwards-compatible. That's the only solution to the complexity issues MS is facing.
Not to be ridiculously, totally, farcically speculous, but here's a scenario for you:
Vista ships at $$$, with extreme requirements. Adoption is very low, due to all the problems that have been rehashed here at slashdot over the past months. However, Vista is fully backwards-compatible (or as near as possible).
MS releases another OS that looks like Vista but is not backwards compatible (though probably compatible with Vista). Price (at least cost of use) is an order of magnitude (ok, an order of magnitude in binary) lower than Vista.
Users who need interoperability with older Windows versions pay for Vista (these'll be primarily businesses). Everyone else can buy the non-backwards-compatible version.
Of course, Vista would have had to have been built with this in mind. And of course, this would break so much currently-deployed software that it would kill MS in the short run. But, it would help explain MS's interest in ODF.
Finally, this would have to have been in development for years now, and there hasn't been a peep from Redmond (officially or not), so it's pretty much a garbage theory. But, in the long run, the only way MS can get rid of the bloat is to get rid of backwards compatibility.
"Trolls they were, but filled with the evil will of their master: a fell race..." -- J.R.R. Tolkien on Olog-hai
I'd almost guarantee that if you removed the API then .Net would stop working because it's implemented on top of it. It probably is implemented on top of COM as well.
And anyway, the chance that you'd have NO such applications is virtually nil.
I worked in the Exchange group responsible for beating Notes. Its not like Notes made it difficult or anything. Remember VIM? Sure, back in the days when we beat Notes, we thought people were more interested in actually gettting their mail, then whether or not they could all collaberate in trying to figure out where their mail went. Notes sucked early and never recovered. Exchange started out good and only got better. There are 100K+ employee Exchange installations all over the world that work just fine. There has not been a day that Notes existed where it didnt just suck in all kinds of ways. We barely had to pitch Exchange to get businesses off of Notes, we just went down the list of suckage and asked which items applied to their current environment. The rest is history. I wont even go into NotesScript 2.0. My hands might start shaking just remembering the suckage.
Sounds pretty familiar - a kin to a process that a certain fruit company started in 2001 and is pretty well finished with now. OS X with Cocoa (X only), Carbon (9 and X) and Classic (9 emulation) worked pretty smoothly for them and their users, it seems.
Others really should learn from that lesson of how to handle retiring archaic architecture that they don't want to drag along.
- MM