Linked by David Adams on Fri 4th Jul 2008 15:47 UTC, submitted by Caffeine Deprived
Microsoft This article by Shane Schick looks at changes Steve Ballmer should consider making at Microsoft now that Bill Gates is out the door. A couple of the most interesting: making user education a priority and establishing an open source project.
Permalink for comment 321400
To read all comments associated with this story, please click here.
RE: What he should make
by google_ninja on Fri 4th Jul 2008 20:24 UTC in reply to "What he should make"
google_ninja
Member since:
2006-02-05

I agree with abolutely nothing you said.

Gather a team to develop another operating system that is lean and fast and depends on proven technology; and I highly recommend dropping NT, and using a different core like BSD, Linux or solaris. Meanwhile work on a very good emulation project for windows programs, ie exactly like what Apple did with their OSX.


Why? NT is a great kernel. God didn't hand down the perfect kernel to Dennis Ritchie. There are alot of idea's outside of the UNIX way, and there have been alot of things learned since UNIX.

Now MS showed us how they never overcome viruses and security problems


You must not have been around pre XP SP2.

and how badly their graphics engine is compared with the others in mac and linux platforms.


Are you talking about GDI or DirectX? How/why is it bad compared to mac/linux?

[/q]why to deviate from openGL [/q]

because directx is cleaner, faster, and more stable

why not use linux desktop composition engines


because out of the three major operating systems linux has the most bloated and least stable of the bunch?

why not use a proven core like BSD or solaris, why.... many things


by core I take it you mean kernel, because windows has a full unix userland http://technet.microsoft.com/en-us/interopmigration/bb380242.aspx

Look at MS windows explorer how frequently it crashes in Vista and XP. I never encountered any Finder crash in OSX and I see 1/10th the amount of crash when using Nautilus, 1/5th with Konqueror; so why not adapt one of those.


I very, very rarely get file manager crashes in any of the three big operating systems, certainly not enough to measure.

Also I thing within the development team there should be a design team to judge the developers sloppy work and to force them to adhere to standards of good roots. Eg, the team will watch for nested windows and prevent them.. No more than 2 windows deep for any settings, I mean consolidate all windows in one location and go from there with tab systems; get a clue from System Preferences in Mac.


While I agree that apple sets the bar in polish and usability, the windows team has far too MUCH of this kind of crap to deal with. MS needs to reduce burocracy and streamline process, not bloat it.



What MS needs to do is continue what they are doing. Polish UIs and don't listen to the old users who complain where something isn't where they expect it to be, rewrite crufty APIs and don't listen when companies complain that their ancient apps don't work.

The culture and process is where the shift needs to happen. Get an agile-ish process going with a new point release every month or two, and major releases every year. Get tight feedback cycles with the users. Make the development process more transparent, so that people can give feedback before things get too far. Make requirements flexible and within a smaller scope.

Just because they are a big company with a massive market does not mean they cant go agile (or scrum or whatever), it just means it is hard due to the defined culture and inertia internally.

Reply Parent Bookmark Score: 2