|
humm, yeah heard lot about longhorn, they say its some kind of new OS from microsoft. Really? humm, time to upgrade my machine i guess.
I'll write a suicide note on a hundred dollar bill - Dire Straits
|
|
|
|
|
.NET is enabling the creation of distributed Request-Response systems to us with relative ease. However, currently event driven distributed systems still require a lot of custom "plumbing" code. This communication plumbing usually has robustness issues (lacking guaranteed delivery, caching/logging, reconciliation, synchronization, etc.). Other issues involve network friendliness - needing to open up ports for a wide range of custom protocols. Then, debugging what has gone wrong is a challenge as well.
Indigo should alleviate many of these problems and allow us to get back to focusing on the features our customers want.
Dale Thompson
|
|
|
|
|
Mainly for XAML as I hate they way WinForms describes the UI in code 
Of course, MyXaml[^] has already solved this problem for me in .NET and WinForms. Not to mention solving a lot of problems, that I don't think Avalon will cover.
WinFS would be nice, but only because I've been waiting for this since before Windows NT was released.
Indigo, sounds really cool but I don't think I'd find a use for it in my current development plan.
Michael
CP Blog [^]
|
|
|
|
|
Michael P Butler wrote:
Indigo, sounds really cool but I don't think I'd find a use for it in my current development plan.
Michael P Butler wrote:
Mainly for XAML as I hate they way WinForms describes the UI in code
Michael P Butler wrote:
Of course, MyXaml[^] has already solved this problem for me in .NET and WinForms. Not to mention solving a lot of problems, that I don't think Avalon will cover.
using this in a commercial product are we?
Michael P Butler wrote:
WinFS would be nice, but only because I've been waiting for this since before Windows NT was released.
With foresight, you should work for Microsoft. You could of laid the foundation 10 years ago , I'll give you Dave Cutlers email address.
Which is? Sticking with a ten years on Windows client application, from what I gather in the last thread.
|
|
|
|
|
Realistic wrote:
Michael P Butler wrote:
Mainly for XAML as I hate they way WinForms describes the UI in code
I'm a big believer that user interface shouldn't be constructed by code. UI is meta data and should be described as such.
Realistic wrote:
Michael P Butler wrote:
Of course, MyXaml[^] has already solved this problem for me in .NET and WinForms. Not to mention solving a lot of problems, that I don't think Avalon will cover.
using this in a commercial product are we?
Yep. Building several apps with it.
Realistic wrote:
With foresight, you should work for Microsoft. You could of laid the foundation 10 years ago , I'll give you Dave Cutlers email address.
Don't you remember Cairo and the rest. Not to mention all the stuff that Dave Cutler wanted to do, but was lost because of backwards compatablity and the ever changing relationship with IBM and OS2 at the time.
Michael
CP Blog [^]
|
|
|
|
|
Of course, MyXaml[^] has already solved this problem for me in .NET and WinForms. Not to mention solving a lot of problems, that I don't think Avalon will cover.
So when Longhorn finally does roll around, will you still use MyXaml or use the native Avalon? (They are at least supposed to be somewhat compatible, right?)
An expert is somebody who learns more and more about less and less, until he knows absolutely everything about nothing.
|
|
|
|
|
Navin wrote:
So when Longhorn finally does roll around, will you still use MyXaml or use the native Avalon? (They are at least supposed to be somewhat compatible, right?)
I'm using MyXaml as the base for a range of applications and as I hope to be still maintaining these apps when Longhorn is released, I'll be sticking with MyXaml. If you read through the MyXaml blog[^] you'll see Marc's thoughts on XAML and MyXaml compatability.
To be honest, there isn't a lot to XAML/MyXaml. There are just a simple parsers that build objects. It is the value added stuff with MyXaml that Marc has created that has made me plump for MyXaml over my own parser or Xamlon. The Workflow, State-machine, EventPool and MvC extensions to MyXaml have given me a new way of developing software.
There is no reason why XAML can't do this in the future, but for right now and for the non Longhorn platforms (including Mono and Pocket PC) - MyXaml is the only choice for me.
Michael
CP Blog [^]
|
|
|
|
|
|
The poll is more about which of the three features is most important to you, rather than a general poll about Longhorn. (As Chris pointed out to me).
Michael
CP Blog [^]
|
|
|
|
|
When MS finally finishes whatever their next technology is and releases it, I'll start reading the docs. By the time I'm done, they'll have released the update that adds the promised features and makes it work. That will probably be at least 4 years from now.
So I have to admit I'm completely unconcerned with Longhorn at the moment.
|
|
|
|
|
This seems to be exactly what I am thinking as well.
C++ - Pure, Simple, Makes Sense.
C# - Microsoft's idea of Pure and Simple
|
|
|
|
|
Hopefully, this will make Windows more stable. Hopefully....
|
|
|
|
|
Hi,
from what I've learnt about Longhorn it will not be THAT managed OS - instead the NATIVE services provided by the Windows OS (and consolidated to the 3 pillars mentioned in the poll) will be accessible from .NET managed code by default (this will be the preferred programming style in the Longhorn timeframe).
But there is no reason why to not program native apps using ATL, Win32, MFC or whatever library is used.
Also Microsoft is still programming software in native code - e.g. SQL Server 2005 does still have a native kernel, Visual Studio 2005 also. What is currently written in managed code are UI parts like PlugIns in VS 2005 or the Workbench in SQL Server 2005 (I guess cause it's a lot easier to write extensible, pluggable apps in managed code).
Just my 2 cents
andi
|
|
|
|
|
Very true,
There is still a performance hit on the managed vs native code. Microsoft would like developers to start programming in managed code, but for performance critical applications (IE. Games, financial software etc..) it will be in native code.
But remember you can mix native and managed code. Although their is draw backs that a developer must pay attension to when doing this.
As for the poll, I believe the WINFS team is the most important in the longhorn family. As a Unix/Linux/Windows developer I have been paying attension to this the most.
|
|
|
|
|
Anonymous wrote:
Also Microsoft is still programming software in native code - e.g. SQL Server 2005 does still have a native kernel, Visual Studio 2005 also. What is currently written in managed code are UI parts like PlugIns in VS 2005 or the Workbench in SQL Server 2005 (I guess cause it's a lot easier to write extensible, pluggable apps in managed code).
This is true, and why people keep saying "COM is dead, COM is dead" should take their f***ing heads out of the sand and wake up. UI written in managed code - good, backend number crunching - done in COM objects or even win32 dlls.
To other people reading this thread who think com is dead, should take a look at the videos at channel9.mdsn.com[^] , and see that most of the internal works is .net and COM.
|
|
|
|
|
|
Given the fact that I'm unlikely to see Longhorn in use by my client base this decade, it doesn't matter which feature is most important. Sure Avalon looks good and Indigo sounds nice. Sadly, I won't be able to use them practically for many years.
Even putting these features into Windows XP won't make much impact as most clients I know prefer to run Windows 2000, mainly because they like to keep all their machines running the same software and a mass upgrade to XP is outside of most IT budgets.
Even new machines are downgraded from XP to 2000, because it makes the user and the IT departments life easier to be all running the same platform.
Michael
CP Blog [^]
|
|
|
|
|
I agree with you.
In fact I think MS agree you too, it's why they plan scaled down version of those 3 technologies on Windows XP!
|
|
|
|
|
Or maybe MS figures they should give the client a taste of what "could be".
Best,
Jerry
I Do Whatever My Rice Krispies Tell Me To.
Toasty0.com
|
|
|
|
|
The 'who cares' option means people will vote on whether or not Longhorn is important - not on what features are important. Like it or not if we stick with MS products we'll all be using it in 10 years.
cheers,
Chris Maunder
|
|
|
|
|
Chris Maunder wrote:
The 'who cares' option means people will vote on whether or not Longhorn is important - not on what features are important.
Fair point. Perhaps you need to do what SlashDot do and add a "Don't complain about lack of options. You've got to pick a few when you do multiple choice. Those are the breaks." text 
Michael
CP Blog [^]
|
|
|
|
|
we'll all be using it in 10 years.
Now that's optimistic... you really think it'll be out that soon?
An expert is somebody who learns more and more about less and less, until he knows absolutely everything about nothing.
|
|
|
|
|
Avalon: A nice toy. So what?
Indigo: Works with XP and Server 2003 as well.
WinFS: When is it going to be available for all editions?
This is not meant to be MS bashing. I'm just looking for the ultimate reason why everybody needs Longhorn. What makes Longhorn so special?
|
|
|
|
|
Corinna John wrote:
What makes Longhorn so special?
Because it will take extra long long time for you to realize that you must have it, of course by that time the OS MS thinks you must have will be totally different.
As for me, I must have the one that comes after Longhorn, whatever it is. 
|
|
|
|
|
The only significant benefit I can see in Longhorn is a more efficient storage model. Indigo is a useful enhancement, and Avalon is a nice-to-have, but without WinFS there's no reason to switch. It would be far better if Microsoft waited until they can deliver a complete package than to parcel it out in dribbles. But it seems, as in so many companies, that Marketing is in charge instead of people who produce and use real products.
"My kid was Inmate of the Month at Adobe Mountain Juvenile Corrections Center" - Bumper Sticker in Bullhead City
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
[/Edit]
