Where is Microsoft going today?
-
Or rather, in the future. I have an idea... Ditch legacy and create a lean system (that you can still dual boot to legacy or includes a decent VM) then you should be able to come up with an OS that will fly. Long term yes, with some risk yes, but otherwise I think Microsoft is well down the path of diminishing returns on desktops. Elaine (slightly provocative fluffy tigress) The tigress is here :-D
(a) No Apps / No Users death trap (b) Absolutely short term, unless you don't update the "new, lean system" Sorry kitty :cool:
Some of us walk the memory lane, others plummet into a rabbit hole
Tree in C# || Fold With Us! || sighist -
(a) No Apps / No Users death trap (b) Absolutely short term, unless you don't update the "new, lean system" Sorry kitty :cool:
Some of us walk the memory lane, others plummet into a rabbit hole
Tree in C# || Fold With Us! || sighist -
Or rather, in the future. I have an idea... Ditch legacy and create a lean system (that you can still dual boot to legacy or includes a decent VM) then you should be able to come up with an OS that will fly. Long term yes, with some risk yes, but otherwise I think Microsoft is well down the path of diminishing returns on desktops. Elaine (slightly provocative fluffy tigress) The tigress is here :-D
Trollslayer wrote:
Ditch legacy and create a lean system
Good God, no. The main reason people even use Windows is the backward compatibility. The "clean start" solutions create more problems than they solve.
My programming blahblahblah blog. If you ever find anything useful here, please let me know to remove it.
-
So you think it's best to continue the bloat? For how long? "If the world should blow itself up, the last audible voice would be that of an expert saying it can't be done." - Peter Ustinov
Given that quad-core chips and 1GB memory are going to be standard desktop equipment in next to no time "bloat" is not really an issue. '--8<------------------------ Ex Datis: Duncan Jones Merrion Computing Ltd
-
Or rather, in the future. I have an idea... Ditch legacy and create a lean system (that you can still dual boot to legacy or includes a decent VM) then you should be able to come up with an OS that will fly. Long term yes, with some risk yes, but otherwise I think Microsoft is well down the path of diminishing returns on desktops. Elaine (slightly provocative fluffy tigress) The tigress is here :-D
Trollslayer wrote:
Ditch legacy and create a lean system (that you can still dual boot to legacy or includes a decent VM) then you should be able to come up with an OS that will fly.
One might have said that competition and a free market would eventually create the conditions for that to happen, but I don't think that will happen. Yes, Microsoft is well down the path of diminishing returns on desktops and there's no way to avoid that, even with the bubble that will occur now that you can dual boot a Mac with XP, and with the forthcoming release of Vista. So instead, what Microsoft needs to do is to eventually move out of the desktop OS business and figure out what the next revolution is going to be. I honestly don't think thin client is it. There's too many people working without highspeed connections, working off the net (and also off the grid) becomes difficult, and security is a perceived problem. Personally, I feel it's going to be information management and retrieval. There's a glut of information out there, and it's hard to search, categorize, index, cross reference, maintain, and re-access. If I were Microsoft, that's what I'd focus on. Because soon, we're going to transition from being information creators to becoming information analyzers. Sure, there will be still be people who create information, but there will most likely be big business in searching, combining, and processing the glut of information already out there. I guess the Empire known as Microsoft is reaching a Seldon Crisis. :) Marc Pensieve Functional Entanglement vs. Code Entanglement Static Classes Make For Rigid Architectures Some people believe what the bible says. Literally. At least [with Wikipedia] you have the chance to correct the wiki -- Jörgen Sigvardsson -- modified at 9:11 Thursday 6th April, 2006
-
Given that quad-core chips and 1GB memory are going to be standard desktop equipment in next to no time "bloat" is not really an issue. '--8<------------------------ Ex Datis: Duncan Jones Merrion Computing Ltd
Duncan Edwards Jones wrote:
Given that quad-core chips and 1GB memory are going to be standard desktop equipment in next to no time "bloat" is not really an issue.
It's not purely a matter of performance. Added complexity can cause all sorts of unexpected interactions, security problems and glitches. "If the world should blow itself up, the last audible voice would be that of an expert saying it can't be done." - Peter Ustinov
-
Given that quad-core chips and 1GB memory are going to be standard desktop equipment in next to no time "bloat" is not really an issue. '--8<------------------------ Ex Datis: Duncan Jones Merrion Computing Ltd
Imagine if other industries took this stance. :omg: Just because CPUs are faster and they have more RAM at their disposal, that in no way should mean sloppier programs.
"Let us be thankful for the fools. But for them the rest of us could not succeed." - Mark Twain
"There is no death, only a change of worlds." - Native American Proverb
-
Or rather, in the future. I have an idea... Ditch legacy and create a lean system (that you can still dual boot to legacy or includes a decent VM) then you should be able to come up with an OS that will fly. Long term yes, with some risk yes, but otherwise I think Microsoft is well down the path of diminishing returns on desktops. Elaine (slightly provocative fluffy tigress) The tigress is here :-D
That's why they made .NET. Except for the lean bit. And the bit about it flying. OK, aaaand some of the legacy bits too. cheers, Chris Maunder
CodeProject.com : C++ MVP
-
That's why they made .NET. Except for the lean bit. And the bit about it flying. OK, aaaand some of the legacy bits too. cheers, Chris Maunder
CodeProject.com : C++ MVP
-
So you think it's best to continue the bloat? For how long? "If the world should blow itself up, the last audible voice would be that of an expert saying it can't be done." - Peter Ustinov
You mean like .Net? ------- sig starts "I've heard some drivers saying, 'We're going too fast here...'. If you're not here to race, go the hell home - don't come here and grumble about going too fast. Why don't you tie a kerosene rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt "...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
-
Trollslayer wrote:
Ditch legacy and create a lean system (that you can still dual boot to legacy or includes a decent VM) then you should be able to come up with an OS that will fly.
One might have said that competition and a free market would eventually create the conditions for that to happen, but I don't think that will happen. Yes, Microsoft is well down the path of diminishing returns on desktops and there's no way to avoid that, even with the bubble that will occur now that you can dual boot a Mac with XP, and with the forthcoming release of Vista. So instead, what Microsoft needs to do is to eventually move out of the desktop OS business and figure out what the next revolution is going to be. I honestly don't think thin client is it. There's too many people working without highspeed connections, working off the net (and also off the grid) becomes difficult, and security is a perceived problem. Personally, I feel it's going to be information management and retrieval. There's a glut of information out there, and it's hard to search, categorize, index, cross reference, maintain, and re-access. If I were Microsoft, that's what I'd focus on. Because soon, we're going to transition from being information creators to becoming information analyzers. Sure, there will be still be people who create information, but there will most likely be big business in searching, combining, and processing the glut of information already out there. I guess the Empire known as Microsoft is reaching a Seldon Crisis. :) Marc Pensieve Functional Entanglement vs. Code Entanglement Static Classes Make For Rigid Architectures Some people believe what the bible says. Literally. At least [with Wikipedia] you have the chance to correct the wiki -- Jörgen Sigvardsson -- modified at 9:11 Thursday 6th April, 2006
-
Or rather, in the future. I have an idea... Ditch legacy and create a lean system (that you can still dual boot to legacy or includes a decent VM) then you should be able to come up with an OS that will fly. Long term yes, with some risk yes, but otherwise I think Microsoft is well down the path of diminishing returns on desktops. Elaine (slightly provocative fluffy tigress) The tigress is here :-D
I disagree. This is the stance that Netscape took, which ultimately made them a nonplayer - they went from Market dominance to being an ankle bitter. Rewriting a large system from scratch is rarely a good idea, and if attempted, those attempting had better continue to allocate resources to the old system. Here are a few reasons why I think doing so is a bad idea: 1) The system is too big for a small group of people to understand well, so there is probably a LOT of small, seemingly insignifant lines of code that addressed one of the numerous bugs discovered over the years. That code is the product (albeit not perfect ;-) of years of realworld use. 2) Developing from scratch drastically reduces a business's ability to adapt to changing market conditions; a certain foundational threshold would have to be obtained before a lot of the feature set could be built. 3) Inevitably it would have an incremental release where funtionality is lost, possibly alienating users accustomed to having that functionality. 4) Nothing is any good until version 3 anyway, at which it would be bloated and time for yet another rewrite. ;-) Daniel Wilson
-
Or rather, in the future. I have an idea... Ditch legacy and create a lean system (that you can still dual boot to legacy or includes a decent VM) then you should be able to come up with an OS that will fly. Long term yes, with some risk yes, but otherwise I think Microsoft is well down the path of diminishing returns on desktops. Elaine (slightly provocative fluffy tigress) The tigress is here :-D
One of the problems I can see with ditching "legacy" support is that they would then be open to much more competition. If with Vista MS decided that it would not support any of the previous code/applications, instead requiring either a dual-boot or running a VM system, then there would be no advantage to running Vista over any other OS - and considering Windows' main competitor is essentially free, I don't think MS would be willing to take the risk. That said, it would be amusing to see Vista running all it's apps in a port of WINE :laugh:
-
Or rather, in the future. I have an idea... Ditch legacy and create a lean system (that you can still dual boot to legacy or includes a decent VM) then you should be able to come up with an OS that will fly. Long term yes, with some risk yes, but otherwise I think Microsoft is well down the path of diminishing returns on desktops. Elaine (slightly provocative fluffy tigress) The tigress is here :-D
MacOS? (hides) -- Help me! I'm turning into a grapefruit! Buzzwords!
-
Trollslayer wrote:
Ditch legacy and create a lean system (that you can still dual boot to legacy or includes a decent VM) then you should be able to come up with an OS that will fly.
One might have said that competition and a free market would eventually create the conditions for that to happen, but I don't think that will happen. Yes, Microsoft is well down the path of diminishing returns on desktops and there's no way to avoid that, even with the bubble that will occur now that you can dual boot a Mac with XP, and with the forthcoming release of Vista. So instead, what Microsoft needs to do is to eventually move out of the desktop OS business and figure out what the next revolution is going to be. I honestly don't think thin client is it. There's too many people working without highspeed connections, working off the net (and also off the grid) becomes difficult, and security is a perceived problem. Personally, I feel it's going to be information management and retrieval. There's a glut of information out there, and it's hard to search, categorize, index, cross reference, maintain, and re-access. If I were Microsoft, that's what I'd focus on. Because soon, we're going to transition from being information creators to becoming information analyzers. Sure, there will be still be people who create information, but there will most likely be big business in searching, combining, and processing the glut of information already out there. I guess the Empire known as Microsoft is reaching a Seldon Crisis. :) Marc Pensieve Functional Entanglement vs. Code Entanglement Static Classes Make For Rigid Architectures Some people believe what the bible says. Literally. At least [with Wikipedia] you have the chance to correct the wiki -- Jörgen Sigvardsson -- modified at 9:11 Thursday 6th April, 2006
Marc Clifton wrote:
There's too many people working without highspeed connections, working off the net (and also off the grid) becomes difficult
As one of the few who has a LARGE set of computers off the net, and a few off the grid completely (self contained power to the building/vehicle, no interlink but sneakernet), I agree! _________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb) -- modified at 10:32 Thursday 6th April, 2006
-
Trollslayer wrote:
Ditch legacy and create a lean system (that you can still dual boot to legacy or includes a decent VM) then you should be able to come up with an OS that will fly.
One might have said that competition and a free market would eventually create the conditions for that to happen, but I don't think that will happen. Yes, Microsoft is well down the path of diminishing returns on desktops and there's no way to avoid that, even with the bubble that will occur now that you can dual boot a Mac with XP, and with the forthcoming release of Vista. So instead, what Microsoft needs to do is to eventually move out of the desktop OS business and figure out what the next revolution is going to be. I honestly don't think thin client is it. There's too many people working without highspeed connections, working off the net (and also off the grid) becomes difficult, and security is a perceived problem. Personally, I feel it's going to be information management and retrieval. There's a glut of information out there, and it's hard to search, categorize, index, cross reference, maintain, and re-access. If I were Microsoft, that's what I'd focus on. Because soon, we're going to transition from being information creators to becoming information analyzers. Sure, there will be still be people who create information, but there will most likely be big business in searching, combining, and processing the glut of information already out there. I guess the Empire known as Microsoft is reaching a Seldon Crisis. :) Marc Pensieve Functional Entanglement vs. Code Entanglement Static Classes Make For Rigid Architectures Some people believe what the bible says. Literally. At least [with Wikipedia] you have the chance to correct the wiki -- Jörgen Sigvardsson -- modified at 9:11 Thursday 6th April, 2006
The next thing is TV. And Media. Thats why MS are putting so much into Windows for TV.
Marc Clifton wrote:
information management and retrieval
Google and others are already there. But, they are going to distibute Media in the future too, TV, music etc. Nunc est bibendum
-
I disagree. This is the stance that Netscape took, which ultimately made them a nonplayer - they went from Market dominance to being an ankle bitter. Rewriting a large system from scratch is rarely a good idea, and if attempted, those attempting had better continue to allocate resources to the old system. Here are a few reasons why I think doing so is a bad idea: 1) The system is too big for a small group of people to understand well, so there is probably a LOT of small, seemingly insignifant lines of code that addressed one of the numerous bugs discovered over the years. That code is the product (albeit not perfect ;-) of years of realworld use. 2) Developing from scratch drastically reduces a business's ability to adapt to changing market conditions; a certain foundational threshold would have to be obtained before a lot of the feature set could be built. 3) Inevitably it would have an incremental release where funtionality is lost, possibly alienating users accustomed to having that functionality. 4) Nothing is any good until version 3 anyway, at which it would be bloated and time for yet another rewrite. ;-) Daniel Wilson
Daniel Wilson wrote:
Nothing is any good until version 3 anyway, at which it would be bloated and time for yet another rewrite.
hey!!!! I am at Version 2.94 and I disagree! ;P But we are skipping 3.0 and going to 4.0 just in case.... :laugh: (actually 3.0 will be considered internal release as it already exists, just not at the same scale as 2.94 because it is a redesign) _________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
-
So you think it's best to continue the bloat? For how long? "If the world should blow itself up, the last audible voice would be that of an expert saying it can't be done." - Peter Ustinov
You have to retire old code, but slowly. I would recommend that Microsoft retires old stuff support in the speed of my most conservative customers. :cool:
Some of us walk the memory lane, others plummet into a rabbit hole
Tree in C# || Fold With Us! || sighist -
Imagine if other industries took this stance. :omg: Just because CPUs are faster and they have more RAM at their disposal, that in no way should mean sloppier programs.
"Let us be thankful for the fools. But for them the rest of us could not succeed." - Mark Twain
"There is no death, only a change of worlds." - Native American Proverb
Long time ago I think it was Niklas Wirth who said "Programs get worse faster than hardware gets better"
Some of us walk the memory lane, others plummet into a rabbit hole
Tree in C# || Fold With Us! || sighist -
You have to retire old code, but slowly. I would recommend that Microsoft retires old stuff support in the speed of my most conservative customers. :cool:
Some of us walk the memory lane, others plummet into a rabbit hole
Tree in C# || Fold With Us! || sighistpeterchen wrote:
I would recommend that Microsoft retires old stuff support in the speed of my most conservative customers.
I still have customers using DOS!! :sigh: "If the world should blow itself up, the last audible voice would be that of an expert saying it can't be done." - Peter Ustinov