|
Sponsored Links
Resources
.NET Research Library
Get .NET related white papers, case studies and webcasts
|
News
News
News
|
Messages: 10
Messages: 10
Messages: 10
Printer friendly
Printer friendly
Printer friendly
Post reply
Post reply
Post reply
XML
XML
XML
|
 |
Indigo and Avalon Beta 1 Released with New Names
Microsoft has released WinFx Beta 1 containing updates for the Avalon and Indigo technologies. They have also released the official product names for the technologies formerly known as Avalon and Indigo. Avalon has been named Windows Presentation Foundation and Indigo is Windows Communication Foundation.
Avalon is now officially named the Windows Presentation Foundation. This is the system which unifies the way Windows creates, displays and manipulates documents, media and user interfaces, enabling developers and designers to create visually-stunning, differentiated user experiences that improve customer connection.
Indigo is now officially named the Windows Communication Foundation. This is the system that unifies and extends today’s distributed technology stacks to deliver a consistent, composable experience for building connected systems.
The Beta 1 is available for download here
|
|
|
Message #179497
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Indigo and Avalon Beta 1 Released with New Names
For some reason, I think that "Avalon" and "Indigo" will stick around as the official-unofficial names.
|
|
|
Message #179502
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Indigo and Avalon Beta 1 Released with New Names
There was just zero effort in creating these names.
Paul, you should start a poll to see what developers think of these names. I think they suck a**.
|
|
|
Message #179566
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Let's Get Ready to Rumble!
Consider it started! Don't sugarcoat it, tell us what you think of the new names! Personally, I can sum up my feelings in one word... Yawn!
|
|
|
Message #179575
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
What's in a name?
I think Microsoft seriously underestimates the power of a cool name. The media eats up sexy names and repeats them every chance it gets.
Here's a list of names that show how Microsoft's competitors "get it":
Java vs C#
Google vs MSN Search
Firefox vs Internet Explorer
OSX Tiger vs Windows XP
Enterprise Java Beans vs DCOM/Enterprise Services
Apache vs Internet Information Services
iTunes vs Windows Media Player
LAMP vs .NET (the "product suite")
Cocoa vs .NET (the runtime)
Subversion, Vault vs Visual Source Safe, VSTS
Eclipse vs Visual Studio .NET
Aqua vs Windows Presentation Foundation
Alpine vs Windows Communication Foundation
Ajax vs XMLHttpRequest
Notice the "designed by committee" sound of Microsoft's names compared to the competition.
Ajax vs XMLHttpRequest especially irks me because they're the same exact thing, and Microsoft invented it! Yet the name Ajax took off like wildfire, and now journalists have the nerve to refer to it as a core part of the LAMP stack and Microsoft is on the outside looking in, playing catch-up, etc.
Other Microsoft naming flops: ActiveX, ActiveX Data Objects, Data Access Objects, CDONTS, DCOM, .NET My Services
Most of Microsoft's code names are fairly cool, but what's up with Monad? Is that short for Microsoft Gonad? I half expect Microsoft to rename IronPython to something bland like Microsoft Visual Py# 2005 once it reaches 1.0.
I was getting seriously excited about Indigo. Now that it's called "Windows Communication Foundation", my enthusiasm took a major nosedive, even though I know it's still the same cool technology underneath. It makes it harder to market it to my boss and coworkers. Same thing for Avalon: "You want to use what? Windows Presentation Mutilation? I've heard Ajax is pretty hot..." Speaking of that, I hope Atlas keeps its name.
Microsoft's choice to brand all its new technology as .NET seriously crippled our ability to search for it. Google ignores the dot, turning it into "net". Great move! Now we have a harder time finding valuable content that allows us to do a better job using the technology.
Windows Vista is an OK first step toward catchier naming, but it's still pretty bland. Perhaps the next time you're coming up with "official" names for new products you should make a "no suits, no ties, no board room" rule and hold the meetings at a Starbucks. Bounce your ideas off the baristas. Toss anything longer than 7 letters, and disallow multiple words. Ask your kids what they think. Live a little.
It's a shame to see great technology undermined by poor naming.
|
|
|
Message #179577
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
On second thought...
Maybe the suits asked the teams to come up with a "better" name, and they picked the worst names they could possibly think of so that everybody would continue to call them by their code names!
|
|
|
Message #179689
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
What's in a name?
In general, I think MSoft does it backwards. They tend to conjure pretty cool code names and then label the final product with something "drab and cube-farm-like".
"Vista" must have been an accident of some sort (not that I think it's that 'cool', but it's better than "Windows SOA" or some such nonsense).
|
|
|
Message #179709
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
What's in a name?
I agree, the code names for both of these products was fine. Why choose something as bland and unexciting as WCF?
They need to fire some of there marketing people...
|
|
|
| |
|
| New content on TheServerSide.NETNew content on TheServerSide.NETNew content on TheServerSide.NET |
|
|
Language "mashups" will become more prominent, and developers will become polyglots, one programmer suggests.
SearchWinDevelopment.com offers an introduction to the language, performance, testing and data management improvements in VS 2008.
VBCode.com code snippets cover all aspects of application development, from data binding to security to the user interface.
Get up to date on XAML best practices with a variety of articles, tutorials and webcasts. [SearchWinDevelopment.com]
One team's experience with the VSTS DB edition suggests that it can improve workflow for dev teams. It also enhanced Agile efforts.
(June 24, Article)
Microsoft has begun to include DSL tools in the VSTS kit. A new book by Steve Cook and other VSTS team members helps set the stage.
(June 24, Article)
Cartoon: Be it ever so humble there is no place like your home after you get a Microsoft Home Server .
(June 18, Cartoon)
Microsoft's Thom Robbins says new technology to highlight in NET 3.5 includes AJAX, LINQ for both C# and VB, as well as tooling enhancements intended to ease the task of building WPF, WF and WCF apps.
(June 29, Podcast)
Venkat Subramaniam discusses AJAX bottlenecks, the tenets of Agile development and more. He spoke at the Ajax Experience.
(June 25, Tech Talk)
In the second of a two-part series, Michele Leroux Bustamente discusses design decisions related to the claims-based security model. Read the story and walk through the process for creating a set of claims-based utilities to encapsulate claims authorization at the service tier.
(May 24, Article)
Understanding why the Entity Framework exists and learning where it can fit into your projects can get you prepared for the eventual release early next year.
(May 10, Article)
Resource: This learning guide gives you quick access to useful links on Windows Communication Foundation security information.
(April 24, Article)
TSS.NET's Jack Vaughan spoke recently spoke with Microsoft's Brad Abrams to find out what he is seeing in the field and what the chefs in Redmond are cooking. Along the way he discusses patterns of AJAX frameworks.
(April 11, Article)
In a two-part series, Michele Leroux Bustamente explains how claims-based security is supported by WCF, and how you can implement a claims-based security model for your services.
(March 29, Article)
Windows Workflow Foundation is a new technology that many developers will need to get their heads around. In a brief excerpt adapted from Programming Windows Workflow Foundation: Practical WF Techniques and Examples using XAML and C#, K.Scott Allen considers aspects of workflow definition.
(March 22, Chapter Excerpt)
|
|
