Slashdot Mirror

So you think VISTA is less secure than XP? Not really the answer I was looking for but a quick Google revels it works if you can work around it: http://www.longhornblogs.com/robert/archive/2005/0 7/29/14247.aspx

This article has already been declared as wrong - see http://www.longhornblogs.com/ and http://www.microsoft-watch.com/article2/0,2180,190 2540,00.asp

XAML is compiled into BAML, so this sort of scenario should never bite deployment scenarios. Rob Relyea, a Program Manager on Avalon (oops, WPF) has much more on his blog.

...I'm guessing Microsoft doesn't fear it as much as you'd like them to. Here' a little extra reading for you, it should clear things up.

Linked from the article: Guess he's using it already. ;)

It's called XAML. It is not a programming language, it is a declarative way to control the user interface of a client application. It's nothing new conceptually, just jumping on the XML bandwagon. You can read more about it on this MSDN Blog.

Oh, and there are already commercial clones of it out, even though it won't be released until Avalan/Longhorn timeframe.

Todd: I'm talking Windows [Division] in general, or Microsoft in general. The Longhorn wave ... we kind of took a year off. We kind of stopped the train, went back and fixed some problems in XP, and now we're gearing the momentum back up. We are getting ready to focus on Longhorn.

As I had previously read this is not a joke, just look at this quote from a Microsoft worker: http://www.longhornblogs.com/robert/archive/2004/0 8/06/4352.aspx:

Now, at the same time all this has been going on, there has been a lot of complaining about the constantly slipping Longhorn release date. I haven't weighed in on that too much yet, but I think it's time to break my silence. Microsoft shifted between 80-90% of the Windows Client Team off Longhorn development and onto Windows XP SP2.



Is not that the SP2 is a bad thing. Is a great improvement, but it took so many time, it was delayed so many times...that's all what Microsoft can do? I mean, they just put all they resources in the SP2 and it took them forever to release it.

Perhaps it's just me, but the open source world evolves much faster and has more resources than Microsoft. Every 6 months I see more evolution in the OSS field than what I saw in SP2 (and again, it's not that the SP2 was bad - it was great! But just look at fedora 3 with its SELinux integrationand all the rest. We're being faster than them IMHO, and how fast can you evolute is more important than "how good are you today"

That said, I don't think that XAML itself is a good idea. Apart from XAML vs XUL/SVG/etc. issues, .NET itself is fundamentally broken. I'm not sure that it will be fixed and serious design issues will not make its way to Longhorn.

Avalon will support remoting at a higher level than DirectX. When remoting we will not rasterize on the server machine but instead we will send higher level graphics instructions to the client machine and then call DirectX on the client machine.

This will enable us to send less data over the network as well as reducing the server load because all graphics operations will run on the client machine. We also will get higher performance and fidelity rendering and animations because we will not need to round trip data across the network for these operations since they will be retained on the client machine.

Hats off to Microsoft for releasing this to the pirates as well.

As stated in longhorn blogs, many aspects of longhorn were piped into this release. The blog entries are interesting that microsoft stopped everything due to the mass amounts of worm damage... and really focused on getting the release done right and quickly.

Who cares if you are a *nix or Microsoft guy... we all are going to have less pain thanks to this decision.

Davak

I can't help notice the completely random accusation that Microsoft thinks blogging is a "potential threat."

Barring the fact it's just another random Slashdot statement with no backing evidence, I guess Longhorn Blogs, Channel 9, and the massive MSDN blogs from actual Microsoft employees are threatening their own company.

In the past few years, Microsoft has become incredibly open as a company. I think Slashdot has greatly underreported that fact, and as a result, people here have a wrong impression about Microsoft's developers. Slashdotters should step outside of Slashdot once in a while for its tech news.

There was a comment left on my weblog, apparently by a manager in the Avalon team, saying that XAML is not XUL.

I dont get it, MS has failed numerous times before with "exciting" new technologies and i dont really understand why they are bound to success now.

And Microsoft has succeeded numerous times with technologies too, such as DirectX and I suppose COM considering its widespread usage throughout the Windows OS. They've failed in the past, they've succeeded in the past. XAML can do either.

XAML might as well just be a failiure. Is it really a threat to linux? Not today and not tomomorrow since its just wapourware on paper as of today.

There are a couple articles on MSDN that discuss XAML and provide sample code, such as this XAML RSS reader. Longhornblogs regularly has XAML-related entries, most of which link to code, a sample executable, and screenshots. XAML is definitely not vapourware. It exists and people are using it.

While HTA is simpler than XUL, there is also the case of XAML
which is the direct mirror (or maybe crazy carnival-mirror) of XUL. Last in the blog someone points out that all these attributes was good at the level of HTML 1.0 but is bad, bad, bad if you are going to make any serious applications out of it. CSS is the way to handle such things, unless of course you have an integrated visual developing program that generates code all over the place. Then it all makes sense, because it will become a pain in the *ss to convert the random attributes into some coherent pattern or transform it to for example XUL. (not that XUL don't have some attributes itself)

Eric Meyer explains why it's a bad thing, even though it might look appealing at first sight.

Other articles, such as this one mention that this is about Avalon.

Avalon, for those of you who haven't been paying attention, is Microsoft's new UI programming paradigm for Longhorn. And it's all based, and written, on ".net". I use ".net" in quotes because what that really means is that it runs in the CLR and is written in C#, managed C++, VB, or anything else that compiles to IL such as XAML. Avalon has also been been described as being much like ASP.NET w/ it's declarative markup syntax. So it's got that going for it too.

So you can be sure that the ".net" technologies are living on, even if the brand may be deprecated (which doesn't necessarily appear to be happening [VS.NET is still alive and well] but who can tell what the MS marketing machine will come up with next).