Brad Wardell's views about technology, politics, religion, world affairs, and all sorts of politically incorrect topics.
The future of extensibility...
Published on May 23, 2004 By Draginol In Windows Software

I'm not sure what to think about Longhorn yet. On the one hand, it looks like it will potentially be a truly revolutionary new version of Windows that has all kinds of new potential built into it. On the other hand, it looks like it could be made into the most proprietary operating system ever. One in which only Microsoft can extend or do anything meaningful to it.

Windows has historically been pretty good about letting developers mold it.  If you didn't like something in the way Windows ran or if Microsoft didn't think of some feature, you could add it in. Windows OSes have always had all kinds of hooks in there for developers to tap into to add features to the base operating system.  Without these "holes", anti-virus programs would be virtually impossible to do and we would never have had instant messaging (which hooks into the mouse and keyboard to see if you're active).

But Longhorn could go either way. Microsoft has made occasional noises that "nearly half of reported crashes are caused by third party programs". As if that is a bad thing.  One would hope that all crashes on Windows were the result of third party programs and not bugs in the OS itself. But this leads me to worry that maybe Longhorn will be Microsoft's way of closing the door on everyone. Longhorn could be simply an application launcher with a "take it or leave it" philosophy behind it.  I suspect the Linux advocates of the world hope very much that Microsoft's "security" initiatives end up killing extensibility since they would be the primary beneficiary of such a move.

The new compositor is the source of much of our excitement but also a lot of my fear.  If the Windows desktop is rendered much like a game is today in DirectX, all kinds of things become doable. Fears that customization might "slow down your computer" become moot.  But customization requires openings in the OS at a sufficiently low level where developers can extend the feature set of the operating system. And that's where I worry. Will Microsoft take the time to put this kind of thing in there.

For example, in Longhorn's alpha, when you hit Alt-Tab the open windows actually show up shrunk and rotated and you can quickly pick your way through it. That's pretty cool. But imagine if I, as a developer, want to have hot keys that do other visually appealing things to the windows. Say I want to have a mode where inactive windows are gray scaled. Or maybe have Windows key-I scale the inactive windows by 50%.  I'm just making things up here but I, as a developer, want to be able to add that kind of functionality into the OS.  We can do this on Windows XP (but it's not practical from a performance point of view - no compositor).

The same is true on skinning. Will Longhorn be as visually customizable as Windows XP and before? It's way too early to tell but hopefully Microsoft will keep the door open to those who want to put in the work to make Windows look and feel however they want. With the compositor, third parties could potentially create entirely new ways of doing the user interface. I'm not talking XAML, we're talking ways where companies or individuals can customize the entire OS at once (I have mixed feelings about XAML, I don't want my apps as poorly designed as many websites I visit!).

I think XAML and other technologies are good, but I want users to have the ability to control the overall look and feel of their own computers. That's why I'm into skinning in the first place - I want to be able to decide how my computer works because I know how I work.

And for those who thinking skinning is some toy or some hobby, don't kid yourself. Next time you buy a new computer or a new piece of hardware that comes with custom software, notice how much of it is "skinned" with its own custom UI.  Make no mistake, without programs like WindowBlinds and DesktopX and Litestep and Winamp, I am quite certain that this whole move to programs with their own branded customized interface design would never have happened. One of the major innovations in computer software over the past year can find its roots in the whole customization "niche" (a niche of millions of active users).

So that's where I stand with Longhorn. On the one hand, I'm very excited about its possibilities. But on the other hand, I worry that I'm going to be locked into having to use it exactly as Microsoft decides I can use it. I want to be able to use alternative shells, have desktop objects and widgets, skinned windows, integrate more functionality into my Start bar or Longhorn dock, etc.  I suspect all these things will become possible. I just want to make sure that it doesn't require massive effort to do it and that on day 1 when Longhorn is released, I am able to do all sorts of neat new things with Longhorn that didn't necessarily originate out of Redmond Washington.


Comments (Page 1)
2 Pages1 2 
on May 23, 2004
I just read the article... I too have mixed feeling on it... not so much as development goes for Im not a developer... Im the web page nerd that does all the stupid HTMLing in my pages that others cant because I DO know the coding involves as for Longhorn... if it doesnt allow me to do all that I can do with XP, and that specificly targets skinning it with SD skins and WB skins, for one... Im gonna be massively pissed, that is one thing I have to have if I get a new computers... is my skins. Im sorry to make it blantant but the developers that thought up the Green taskbar button for Xp style on XP... I want to choke them, its hidious damn it.
So therefore if Longhorn does not allow its endusers to customize and control it to there liking... I can only say one simple rule. Boycott.

Thomas
on May 23, 2004
That would not be good at all.  Half the fun of having your own personal computer is the customization that goes into.  It's personalized just how you want it.  Thanks for the info Brad.
on May 23, 2004
This article is horrible. If you have been following the progress on any of the longhorn pilliars, WinFS for example, you would know that third party developers will be able to fully 'tap in' in many ways including their own meta data in files. This is extended to the entire system. If you have watched some of the longhorn tech videos especally the ones with XAML you'll know that visual appearance is fully customizable. I recomend you turn your attention to the section of the one video which shows a sample logon screen, and depending on the picture that is selected a totally different 'skin/appearance' is presented. This is just an examply of the possible extensibility that will be available to third party developers.
on May 23, 2004
Forget the "skinning" crap. Corporate use drives Windows and corporations don't skin. The lock-in MS intends will be driven by a completely proprietary file system that can't be easily reverse engineered - even NTFS is not fully reverse engineered by the Linux community yet - WinFS will be worse. You also had better worry about the horsepower needed to drive this beast. MS is talking about 3GHz processors, 2GB of RAM, and a terabyte of hard disk! You think the average corporation -even in 2007 - is going to upgrade to that just to run Longhorn? The 20 million small businesses? ! Only large corporation CIO idiots are going to do that. And the bugs? The security holes? Oh, please, this is going to be disaster for the entire IT community! And a blessing for Linux!
on May 23, 2004
Quoting you: That's why I'm into skinning in the first place - I want to be able to decide how my computer works because I know how I work.

Reply: Obviously you have no clue what real skinning is like. Being limited by 30 or so premade skins in a skinning program sucks. You cant change the shade of anything. the size of anything. Its locked in. Try using KDE once. Then you'll know what real skinning is like.
on May 23, 2004
Wow a very transaparent Penquinsta troll there.. they are not even bothering to create accounts anymore! Do idiots like that actually expect that we will beleive they are 3 different people?
on May 23, 2004
greywar; you have hit the . . . . on the head.

It is clear that Vannos, Hack, and SuperCat are either the same person or just a couple (three) linux users that think that they already know everything. I pretty much suspect they picked up on the article Brad wrote off of Neowin (it was linked to joeuser). It is also perfectly clear they do not know who Brad is, or they wouldn't be saying the things their attempting to pick forward.

Pam
on May 23, 2004
I hope that it will be still open, so we can still customize windows.
on May 23, 2004
Somewhat off-topic: which version number does Longhorn return? What does "ver" tell you?
on May 23, 2004
You've got me pinned wrong. Im not the same person as Hack or SuperCat... i simply have not registered because i've never visited this page before. Also, i'm a strong Windows/Microsoft supporter and i do not run linux/unix/OSX. I even have my copy of XP skinned with StyleXP. This is all great and whatnot, but off topic from the article. My main intended point was that the author's concern over less extensibility to third party users in Longhorn was unfouned. Longhorn will offer more of what modders, skinners, programmers, artists and enthusiasts want. Consider the alternative, closing up and locking down will potentially only drive people to what Microsoft considers its only threat, linux. Many people have sterotypical views of Microsoft, but if you actually look into what they do, they actually do listen, learn and support people like i mentioned above (the enthusiasts).
on May 23, 2004

A few quick answers:

1) I'm pretty familiar with KDE. It is nothing compared to what you can do with Object Desktop. Object Desktop blows it out of the water when it comes to customization. 30 pre-made skins, what a joke.

2) WinFS, meta data, and XAML have NOTHING to do with developers making use of the compositor for their own use. I recommend reading up on XAML and then re-reading my article.

3) Corporations drive some development. But not all. Feel free to explain the corporate "need" that drove having skinning in XP in the first place, a skinnable Windows media player, themes, etc.  Also, feel free to explain the corporate need in Longhorn to have shadows, transparent windows, and other effects.  The fact is, sizzle drives things pretty heavily.

on May 24, 2004
I have read at some MS developer blog site (forgot the adress) that longhorns UI is supposedly able to be exstensible via shells and such. But I too have shared your concern about how customisable by third parties it will be. I myself like using customising software I use object desktop plus litestep together (barebones litestep with objectbar, desktopX and mobydock as well as windowblinds) to skin my windows which gives me lots more flexibility than with the software MS provides. Using that combination of software you can do pretty much any look you desire.

I can just imagine some people (mostly MS style users) jumping up and down like monkeys hoping for the death of stardock but what they don't realize is that without them and developers like the ones who made litestep there probably wouldn't be windows customisation as we know it today.
on May 24, 2004
AAlthough this has been a concern of mine (when i was on a pc, now on Mac) I do not believe this would actually be the case For one specific reason. Monopoly Lawsuit Micrrosoft has been battling for years, If MS was to make such a radical move as to proprietize its new O,S then it would be against everything they were originally in court for therefore risking more heftier lawsuits on their horizon.

Just a thought but a good one i think.
on May 24, 2004
I agree with the article. Even if Microsoft's Chief Software Architect also agrees with the article, there may be less customizability than Windows XP or Windows ME. All those hooks that you also refer to as "holes" can be used by developers of legitimate programs as well as the viruses and worms like Nimba, Code Red, Slammer, Sasser, etc. I hope that the care is taken to be sure to include the former and greatly restrict the latter. Both the OS and Visual Studio.NET 2005 (Whidbey) are crucial. I understand that direct calls to memory locations will be forbidden. I think this is good. C and C++ are way too friendly to buffer overflows and other attacks. I also am watching Longhorn alpha and beta reviews with equal measures of excitement and concern.
on May 24, 2004
I've been thinking the same for a time now. But I think that MS will actually acknowedge the big amount of skinners. And considering that MS has given SD "Microsoft Gold Certified Partner Status" I'd assume that they are well aware of the importance. I mean, they've even licenced SD products.

I look on XAML with great worry though...
2 Pages1 2