New shared source CLI (Rotor) shipped

Timo Noko is a Kite Aerial Photographer from Finland.

Take a look at what he did with one of his photos of Helsinki

http://www.flickr.com/photos/timonoko/105717955/

All and all, his photos are beautiful.

lol, why not instead say that “Yes, we at Microsoft have got our software engineers so streamlined we can rewrite 60% of Vista in 9 months. What you see now is all bluff. Give us a year and we’ll give you a whole new Windows!”.

I don’t get where the issue is. Even if they had to rewrite 60% of the code, it would be done. Half-hearted is not Microsoft’s way, as I’ve seen. At least when it’s going to be earning them money.

karan: what you just said demonstrates you know nothing about developing software. There is absolutely no way you can rewrite that much code in less than eight months and have it work properly. Sorry, just can not be done.

You are right scoble. To rewrite 60% of the millions of code and do that within 9 months is impossible.

on a side note, your feed is still just showing an excerpt…a two liner in my bloglines.

I have a hard enough time mowing 60% of my yard by November…

Great job with Rotor. Nor it’s only for Windows. one step forward, ten steps back off a cliff. Well, at least there’s Mono for people wanting to use .Net on not-Microsoft Platforms.

Robert, was this your big interoperability news?

I thought Winer promised to take his ball and go home, freeing the rest of the world from his egotistic rants.

This is the usual much ado about nothing.
So someone put out false information.
Is that a first for the Internet? Hardly.

Looks like most of the concern centers around a possible impact on Microsoft’s stock price if all the investors on earth were gullible ninnies who bought into this story.

John: no, more news was released about WPF/E last week.

The real point that has been missed here as far as I can see is not the nonsensical statements that Vista could be re-written in a few month, but that it is very possible the original ship date for Vista was an arbitrary date rather than one derived from engineering feedback. In reality Vista is probably now going to come out on the true schedule and the original date had no basis, which from the engineering perspective means it is not really behind schedule. If something can be done in ten days and a manager decides to declare it will be done in 5, is it 5 days behind when it ships in 10? I say no. When I see statements that some blogger “doesn’t know anything about software development” (which of course is probably true) I wonder weather the real question being asked should be, “does my management team know anything about software development?”

Four words for Dave Winer: STFU

That guy clearly doesn’t know a thing about good software. His only skills are annoying everyone with his daily rants and badgering them to try out his buggy, low-tech software that doesn’t really revolutionize everything.

I’m surprised that he didn’t work OPML or the fact that he invented RSS into that post.

The world would be soooo less annoying without that guy.

First off, have you spent any time with the build teams and execs here? I have. They have a ton of thinking that goes into release dates. I’m working on a video that’ll show that.

But, why should we even put up with someone named anonymouscoward? What do you know about software engineering? Sounds like not much if you can make an accusation like that without signing your name to it.

Scoble, I’m trying to say that the issue is dead in the water as it is – people know that it couldn’t be done, and business people wouldn’t care so long as it lands on their desk on a day given some time in advance. Investors would be fools if they didn’t consult someone with some expertise in the business.

I’m more amused than anything at the level of reaction this has gotten. And as I work in the industry, I know you couldn’t even rewrite 20% in that time frame. How many millions of lines of code is it up to now anyway?

Robert,

that’s my point. WPF/E is still vaporware. It won’t be a part of Vista until Q3 this year, and none of the non-MS platform stuff will be testable, or available until between January and June of 2007, so it’s not going to be useful to anyone for what, a year?

That’s not news, that’s a dog and pony show. When you can actually write code for WPF/E and run it on a non-MS platform, then it’s real. Not before.

“Anyone who believes that [rewriting 60% of Windows between now and November] is conceivable is someone who hasn’t got the most basic clue about how software development works.”

…or is somebody who doesn’t believe Microsoft’s predicted release dates.

Please ask the Rotor team why their v2 implementation runs only on Windows XP and requires Visual Studio 2005. It seems that after VS 2005 has shipped all new Microsoft developer products eg. SDKs require it (a bad habit). Why should I be forced to upgrate my VS from 2003? And why is not Rotor supported on at least Windows 2000 and on Windows Server 2003, let alone on other platforms eg. FreeBSD, Linux, Mac OSX?
Also, report some mistakes on the download page where the phrase “under a shared code license” is repeated twice and where instead of Visual Studio 2005 they write Visual Studio .NET 2005. Perhaps some employees have not realized that VS has dropped the .NET logo.

Nektar, if you want .Net on other platforms, use Mono, it’s tons better and people are creating real products with it, Apple even featured one on their site.

Very Very nice information here… Thanks