Linked by Thom Holwerda on Thu 14th Jul 2005 11:53 UTC
Windows Sunday night saw the release of several screenshots of Longhorn Build 5203. Many questions arose, in particular on Microsoft's Longhorn newsgroups. Mike Brannigan from Microsoft has taken the liberty to have tried to answer everyone's questions, questions often repeatedly asked.
Thread beginning with comment 4264
To read all comments associated with this story, please click here.
by markw on Thu 14th Jul 2005 14:22 UTC
Member since:

I don't think you understand perfectly. Longhorn will do much more than OSX. Does OSX have something like Avalon? No. How about something like Indigo? No. Those are two huge things Longhorn has that OSX doesn't. And there are many more little things.

Reply Score: 1

RE: ...
by nivenh on Thu 14th Jul 2005 14:41 in reply to "..."
nivenh Member since:

Indigo = Webobjects
Avalon = InterfaceBuilder

Both have been around for a very long time. Of course if you mean "OSX doesn't" in the terms of .NET integration, you're right, but why would you want that if you weren't developing on/for a MS platform?

Avalon will be nothing more than a gussied up window designer ala VS.NET's dialog editor, except with 5000 more options, and much more arcane xml syntax to go along with it.

And of course, it will be in all managed code rather than native (like WO and IB/Xcode). A true accomplishment.

Reply Parent Score: 4

RE[2]: ...
by on Thu 14th Jul 2005 18:39 in reply to "RE: ..."
Member since:

> Avalon = InterfaceBuilder

Avalon = Macromedia Flex, which isn't yet available for Mac OS X...

Reply Parent Score: 0

RE: ...
by omnivector on Thu 14th Jul 2005 14:45 in reply to "..."
omnivector Member since:

actually os x has had something like avalon since mac os x jaguar. it's more commonly known as quartz extreme.

what exactly IS indigo? i don't think i've met anyone who can say no only what it is, what it does, but what is it even good for or what problem does it solve?

Reply Parent Score: 1

RE[2]: ...
by JCooper on Thu 14th Jul 2005 15:52 in reply to "RE: ..."
JCooper Member since:

Indigo is basically an API to generate web service applications. Its basically the next incarnation of Web Services in the .Net Framework.

From Microsoft:
Advanced Web services support in Indigo provides secure, reliable, and transacted messaging along with interoperability. Indigo's service-oriented programming model is built on the Microsoft .NET Framework and simplifies development of connected systems. Indigo unifies a broad array of distributed systems capabilities in a composable and extensible architecture, spanning transports, security systems, messaging patterns, encodings, network topologies and hosting models. Indigo will be available for Windows "Longhorn" as well as for Windows XP and Windows Server 2003.


Reply Parent Score: 3

RE[2]: ...
by jayson.knight on Thu 14th Jul 2005 21:46 in reply to "RE: ..."
jayson.knight Member since:

I've been using Indigo for a while now; having been exposed to WebObjects in the past I can safely say that Indigo is much broader and deeper in scope than WebObjects. Indigo is much more than web services; it's a fully managed library that wraps up MSMQ, Remoting, Web Services, Sockets, and some aspects of COM+ into a single unified programming interface/API rather than the disparate namespace mess we have now. It's pretty impressive actually. Of course it won't have much impact on a normal home user, but from a development standpoint it's a godsend (for .Net at least); businesses will gain a lot from this.

Reply Parent Score: 1

RE[2]: ...
by CPUGuy on Fri 15th Jul 2005 00:06 in reply to "RE: ..."
CPUGuy Member since:

QE is not even comparable to Avalon. QE would be more comparable to the desktop compositing engine (and the Longhorn one, at this point, is more advanced than QE).

Indigo is basically a communication layer for applications, services, etc...

Reply Parent Score: 1