Slashdot Mirror
New MS Shell Will Not Be In Longhorn
sootman writes "Remember that new Windows shell? Looks like it'll be yet another technology that won't make it into Longhorn. 'It will take three to five years to fully develop and deliver,' said Microsoft Senior Vice President Bob Muglia this week at Tech Ed 2005. However, it's not dead yet--despite not shipping in Longhorn in 2006 or Longhorn Server in 2007, the article says 'Exchange 12 administration functions will be built atop Monad, which would enable users to do everything from the command line that can be done from the graphical interface.'"
Maybe MS could just make it easier by letting us know what actually *will* make it into Longhorn...
I swear I was going to get first post on this one, and then decided... "Meh. Do I want first post in an article as blah and predictable as this one?" I just couldn't bear to be marked redundant while writing first post.
My little site.
Redmond, WA
Microsoft (TM) announced to day that it's new graphical user interface, code-named Avalon (TM) will not ship with Longhorn (TM), it's next operating system. However, Avalon with be an integral part of Windows 2010.
I read Slashdot for the articles
Microsoft just doesn't have the Monads...
^_^
____
~ |rip/\/\aster /\/\onkey
welcome our new longhorn overl - what? Oh nevermind, they're not here yet.
Maybe MS could just make it easier by letting us know what actually *will* make it into Longhorn...
The usual... trojans, worms, clippy...
...That Longhorn updates won't come out nearly as regularly after Longhorn's release as they do now.
With all the features being removed, and the release date getting pushed farther and farther back, Longhorn will end up as nothing more than an expansion pack for Duke Nukem Forever!
- shadowmatter
The RSOD ;-)
Microsoft Barbie says "Writing Operating Systems is HARD!"
What the hell is still in Longhorn?
The code, mind you it's still very much beta... void main()
{
printf("Hello wolrd");
}
Windows Longhorn? How about some other names:
A feeling of having made the same mistake before: Deja Foobar
I hate to say that your mistaken. Microsoft is dropping the "My" from "My computer". This is a revolution of operation system technology.
The next thing that Microsoft will announce is that Longhorn won't run on the new Mac-Intel machines.
"which would enable users to do everything from the command line that can be done from the graphical interface"
I'll belive it when I see it
Sure, see it here, now
Robert Bindler
A Computer Science student's views on technology.
Soon to be announced: the Kernel will not make it on the first incarnation of Longhorn, and will be released in a subsequent version..
SeqBox
Why does it take so long to compile Cygwin and Bash for Windows?
Life is just nature's way of keeping meat fresh.
People, let's try making a list of that which we do know that (for now at least) will be in Longhorn. Each person who replies just has to copy paste the previous list and add his content :P
Let me start with:
* RSOD (red screens of death)
* Dropping the prefix "My" from "My computer", "My network places", etc
The AACS key is NOT 0xF606EEFD628B1CA427BEA93A9CA9773F
XP was to Win2K what Win98 was to Win95.
I'm thinking WinME = Longhorn.
if you steal from one source, that is plagiarism, if you steal from many, well, that's just research.
I say this somewhat tongue in cheek.
Longhorn is going to be packed with golden goodies which are so wonderful that nobody will be able to see them. It will take the few years following for their opacity to set in.
It's not that odd, once you understand the MS indoctrination program. See, MS believes fear is the best control device. Teach the user that computers are scary, dangerous things, and the users will not attempt "complicated" manuevers like you suggest.
My guess is that most users, upon hitting the right click button (via bumping their mouse against their cappacino cups early in the morning), fly into a panic, slam the power button, and grab the phone to call their favorite guru. The guru (if a hired hand), carefully crafted in the spirit of "reinstall, reinstall, reinstall," reinstalls the software, and "fixes the problem."
Until the next latte...
Microsoft has just released their much anticipated hands-free cordless mouse. Warning, it may hurt a little at first.
That'll get fixed in a service pack.
"A language that doesn't affect the way you think about programming, is not worth knowing" - Alan Perlis
Looks like guys who work for MS can't do anything right. Your website is broken (transcript below) ... so tell me again why should we trust you?
.NET Framework Version:1.1.4322.2032; ASP.NET Version:1.1.4322.2032
It just works my ass
Server Error in '/' Application.
This is an unexpected token. The expected token is 'NAME'. Line 21, position 13.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Xml.XmlException: This is an unexpected token. The expected token is 'NAME'. Line 21, position 13.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[XmlException: This is an unexpected token. The expected token is 'NAME'. Line 21, position 13.]
System.Xml.XmlTextReader.SetAttributeValues() +323
System.Xml.XmlTextReader.ParseElement() +138
System.Xml.XmlTextReader.Read() +94
DigitalDudSite.BlogViewer.LoadBlogEntries(String fileName) +939
DigitalDudSite.DefaultPage.OnInit(EventArgs e) +51
System.Web.UI.Control.InitRecursive(Control namingContainer) +241
System.Web.UI.Page.ProcessRequestMain() +197
Version Information: Microsoft