Microsoft is expected to provide the first public details of the embedded operating system to developers in May at its Microsoft Mobility and Embedded DevCon in Las Vegas.
Microsoft is expected to provide the first public details of the embedded operating system to developers in May at its Microsoft Mobility and Embedded DevCon in Las Vegas.
I just hope the embedded version won’t carry uphill that big fat list of features longhorn has. Or maybe they are expecting embedded hardware to double its power by then? I recently tested the embedded version of an applet I made* in several mobile gadgets, and it runs pretty decent, although not perfect. So I hope longhorn (and open source counterparts) won’t steal that much CPU cycles from apps.
* http://pailachat.pachesoft.com
Microsoft has said little beyond a previous acknowledgement that it hopes to ship Longhorn Embedded roughly six months after the desktop version of Longhorn ships sometime in 2006. ((i.e., Longhorn client will ship sometime in 2006; Longhorn Embedded comes six months after whatever date that is.)) “We are not talking about details,” a Microsoft spokeswoman said.
It isn’t even certain when Longhorn will ship and what is going to be included,what it will be.Up to today they postpone
as usual.Now they extend their base with Longhorn embedded.
For a company it’s important to stay in the news revenue,but with positive news,based on facts not heresay ,rumours and probes.
With so much power in terms of budget,people,etc they should
focus to make something innovative out off Longhorn and throw every resource they have at it.Instead they launch even more projects.Focus on the projects running!One very succesfull project gives more in the end than 10 mediocre ones.
I guess MS is pretty much steerless and in confuse these days,and they lack real vision or simply can’t realise what’s on paper.
Real smart to begin developing the roof when you haven’t build the fundament.
Oh well why do i even care,when i’m a Linux adept in blood and soul.
I guess it’s allways hard to see things go wrong which had o potential to make a difference, instead it turns out to be the gazillionth shareholders wet dream.
http://news.com.com/Microsoft+revamps+its+plans+for+Longhorn/2100-1…
Longhorn had already fallen behind its original schedule. Microsoft earlier this year pushed the date back to the first half of 2006, saying a test version would be delayed until next year.
Why starting another project based on another one that can’t be kept to the reslease shedule?
Copying features of the biggest baddest cat
Because they can develop in parallel and share code amongst disparate groups within Microsoft.
This is the result of good configuration management and an excellent baseline re-usable component library.
Generally, as with all embedded Windows versions, the hardware maker builds a version of Windows with only the features they need for their device.
Because they can develop in parallel and share code amongst disparate groups within Microsoft.
This is the result of good configuration management and an excellent baseline re-usable component library.
Yes thank you that’s the procedure seen from a technical perspective.I remember working on windows 2000 and both XP and MacOSX got introduced to the world.At that time the differences weren’t so akin.If you look now how good MacOSX has cristalised opposed to XP some bells must ring,exept MS’s cash register.With all the postponed release shedules and anouncements of “features” ,components not going to be included in the actual “deal”,it’s better in my opinion to release the fundament (better innovate it first) on shedule,and when that has been done start worrying about missed opportunities.