Microsoft wants Windows to play well with others. To do that, it’s recoating the future in Indigo.
Windows gets a splash of Indigo
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
The link is wrong… it should be
http://news.com/Windows+gets+a+splash+of+Indigo/2100-1016_3-5573073…
sorry… i had a timeout first… the link is correct
Indigo is only for MSFT OS’s , it does nothing to talk to and play nice with any other OS.
It’s also ‘intergrated’ into the OS (aka IE) which means a minor security hole(which happens to everyone) will take over a computer.
Well I guess I shouldn’t expect anything less than garbage from MSFT.
I only wonder if this will end up as ActiveX 2.0, there is too much of a focus on integration, and I wouldn’t be surprised to see them try to include some proprietary extras.
Microsoft is ANTI-play-well-with-others and is a dictatorship. It has no interest in working well with others because that does not help their profits. They know nothing about interoperability. Interoperability means unity and oneness and sharing, which is totally the opposite of their ethic.
I thought Indigo was merely the new .NET communications [network/ipc] class library. After reading this article I’m not sure what to think, except that some CEO/COO/CIO will fall for the marketing speak and think that MS will finally solve all their integration problems with this panacea.
Microsoft’s vision is to unify the messaging bus and the average programmer doesn’t have to worry about it–either inside or outside the firewall.
Great. Another generation of programmers who really don’t know how a network functions. The same was promised with DCOM [just focus on the biz logic], which led to slow saturated networks, and VB programmers that did know what TCP was. Aside from that we at least get some more buzz words/phrases to play with:
– Messaging bus
– transportation lane
– Software ecosystem [I know this wasn’t mentioned in the article but it just makes me laugh]
Still, Microsoft is clearly committed to simplifying the process of building distributed applications, through which modular software components send data between the Microsoft and non-Microsoft world
What a revolutionary idea…The IT industry has been trying to do this for how many decades? The problem was solved long ago. Use open standards and publish module interfaces. This industry is still trying to solve problems that have already been solved but with more complex solutions. I remember when XML was going to enable B2B transactions. I guess most technology providers had never heard of EDI. All this from an industry that spews innovation mantra every chance they get.
I think it’s time for me to leave IT.
the new NTFS and how super fantastic it will be for everyone.
Microsoft announces how great windows ME will fix up the codebase.
Microsoft announces how Longhorn will do everything in a whole new way.
Sorry if I am a little snarky regarding promises.
I stopped reading after finishing the 2nd page, because all I saw was marketspeak of how Indigo will fix everything – but it didn’t even offer a blurb as to WHAT it is.
this was my thought exactly… there are no technical details of exactly what this is going to do. can anyone fill in some details?
and utter and disgusting garbage is coming out from Microsoft. I cannot believe this will be the future of Windows as we know it. I would rather take XP and rather actually buy a good copy of XP with all the service packs slipstreamed into it just in case MS stops supporting XP. There is no way at this moment from what I am reading about the crap coming out from MS that I am going to upgrade to the next gen. I seriousyly hope by then game designers realize that they need to focus on other OSes like Linux, and so forth. God what kind of people run Microsoft?!?!
well, check it out… all of it’s there too
http://www.perkigoth.com/home/kermit/stuff/bullshitbingo/
If you want a more technical oriented article about Indigo, read this:
Introducing Indigo: An Early Look (David Chappell)
http://msdn.microsoft.com/longhorn/?pull=/library/en-us/dnlong/html…
Peragrin:
“Indigo is only for MSFT OS’s , it does nothing to talk to and play nice with any other OS.”
Ever heard of web services/soap?
I’ve read the article above, I’ve read the Microsoft article off the website, and my conclusion is this; its a messaging system that is same regardless of whether the messaging is local or accross a network.
Rather than have two seperate technologies, one from local messaging and network, there will be one, meaning, as a programmer, in theory, will be able to create programmes, and if at a later date, the programme needs to be expanded support ‘network centric’ applications, it will be a matter of tweaking a few things rather than re-writing large chunks.
My take on this; alot of theory behind it, but we all know what will happen in pratice. All very nice coming up with these ideas. This isn’t the first time that it has been attempted nor will it be the last.
Take ActiveDirectory, for example, very few companies actually use the vast amount of features available. Most simply use it as a glorified login server; the same thing could have been done using a UNIX system running Novell eDirectory or LDAP.
I’ll put money on it, with in a few years, it will be pushed to the side. Ultimately, what Microsoft is proposing is a complete overhaul of Windows, which is nice, but the result is requiring companies to completely overhaul the software products they sell. Ultimately there will be companies who will weigh it up and simply decide that the cost of embracing those new features equal that of poring their application to an alternative platform – in the end, they might say, “lets keep the application on life support, create a port, and once the time is right, gradually push out the port in replacement”.
What do you do when your market is saturated?
What do you do when you want to sell more? Even if your customers don’t need more?
What do you do??
Well… you sell an advantage that makes them feel good about (re) purchasing your product. You do not really improve the product, you just make them FEEL good about spending more money.
Look at McDonalds and the fast food industry in general.
Look at the obesity crisis in the US.
The fast food industry made its customers feel good to buy combos and double or triple burgers with maxi-extra-large fries or cola presenting those fat menus as the best bang for the buck. Customers did not need them naturally, but they felt good about buying them….felt good….at least for a while.
Now Microsoft is in the same situation. They want to make sure you will come back to their shop and buy the Windows version du jour, with more fries and cola. Even if you don’t need it. And so to make sure you will waste your money on them, they just revamp things that already exist and that you already own, but present it in a different way. They just change the color, and today, it’s painted Indigo.
The desktop already had its fresh lick of paint in Windows XP (a la TeleTubbies), now it’s the turn of OLE/COM/DCOM/ActiveX/.NET to have another coat (Indigo).
That’s value for money… right?
Is it possible to get any technical insight not MICROSOFT bashing?
I’m just going to give up on the site as you have to dig through 12 off topic, flame bait posts to get 2 that are actually relevent.
If you want to rant, go some where else, it’s getting old, you’re ruining the internet.
>>Ever heard of web services/soap?<<
This is Microsot were talking about. Everything they do will only render in IE. microsoft is KNOWN for settings programs to run only their way. Are you really naive enough to believe this time will be any different? Microsoft hasn’t changed businesses practices in 20 years, and 2 anti-trust lawsuits. So tell me what is really different?
Apple is the Computer company that Thinks different. Except for locking down their software it’s very true.
I take your reply as “no”
Despite the name “web” in Web Services they have nothing to do with IE or any other product.
Web Services offer applications a standard way of communicating through a network. They are operating system and platform independent (protocols are built on http and xml).
This means that you can easily make a Web Service in .NET that could be called (think of RPC) from Java and vice-versa. Most other platforms support them, too. Sounds like interoperability to me.
For years it has been possible to use Web Services and Indigo will just make utilizing them even simpler (when configured to offer/utilize enpoints as web services). Of course, an application using Indigo can be configured for inter-Windows communication only, but that’s the developers choice.
Oh and Microsoft has been the biggest driving force for Web Services from the start.
So, that makes the original claim (“Indigo is only for MSFT OS’s , it does nothing to talk to and play nice with any other OS.”) just typical FUD.
Good lord
By P (IP: —.sportsinteractive.co.uk) – Posted on 2005-02-16 11:01:50
Is it possible to get any technical insight not MICROSOFT bashing?
I’m just going to give up on the site as you have to dig through 12 off topic, flame bait posts to get 2 that are actually relevent.
If you want to rant, go some where else, it’s getting old, you’re ruining the internet.
The internet was already ruined. You showed up too late if you think it’s still any good.
There are two main observations here-
1] It is an effort for compatibility with non-compliant applications rather than diverse operating systems, which seems like a counter measure to Linux’s strategy of compatibility with Windows applications.
2] Indigo is supposed to be built into Windows, which further swells the Windows kernel space, possibly making it more sluggish and less secure.