Another Belated Microsoft Memo 232
fiannaFailMan writes "Bill Gates has sent out another memo heralding the latest big development in the industry, as he sees it. This time it's web-based software using technology such as AJAX (that MS 'invented but failed to exploit'). The Economist says 'As in previous cases, what is new is not the idea itself, but the fact that Microsoft is taking it seriously.' Zach Nelson of NetSuite decided against writing a memo. 'Writing memos is cheap,' he says, whereas 'writing software is a whole lot harder.'"
Memo (Score:5, Funny)
Re:Memo (Score:5, Funny)
Addendum: Make sure someone fucking buries the next NetSuite and fucking kills the next Zach Nelson before the lunch with Ballmer. Buy stronger chairs, too.
Re:Memo (Score:2)
Re:Memo (Score:2)
Re:Memo (Score:5, Insightful)
It's not cheap - its easy. He's writing memos now because, like a LOT of people who used to code, he can't write software any more.
This has happened to a lot of former coders - they hit a certain age, and they just can't see themselves writing code any more. They don't want to learn yet another language or 5. This doesn't happen to everyone (hey, I just pulled a 9-5 ... that's 9 AM to 5AM, and I'll be hitting the half-centry mark next year), but it does seem that a lot of coders are gone well before they hit 40.
You could probably divide coders into 2 groups - those who code because they can, and those who code because they're curious. The ones who code because they can, eventually, they can't.
But curiosity never stops. When you've been coding for 16 hours, and you figure you're all done, but it would be neat to "write a quick little program to write a program" (because programs that write programs are the happiest programs in the world), and you go and do it because you WANT to and you're curious as to how well its going to work out and you know you won't be able to sleep until you "scratch that itch" . . . if you're still doing that a couple of decades later, you aren't the memo-writing type.
This phenomenum (people peaking in their 30s and then they drop out) isn't limited to just IT. Look at how many "management types" simply can no longer do the grunt work in their own problem domains. They've lost their edge. Sure, they make up for it with experience, in a lot of cases, but there's no replacement for a sharp edge AND experience.
Re:Memo (Score:3, Insightful)
If you find it laboring to read an algorithms book then you might want to find a different field.
On the same note. If you don't understand al
Who owns it? (Score:3, Interesting)
Re:Who owns it? (Score:3, Insightful)
Re:Who owns it? (Score:2, Informative)
Re:Who owns it? (Score:2)
It is NOT an example of a time that they have done so. All speculation.
Re:Who owns it? (Score:4, Interesting)
BTW, the utility of this patent has to do with backwards compatibility with OSes that only understand the 8.3 file format, which nobody gives a shit about anymore. However, the particular way that long filenames are kludged into VFAT are now cast in concrete, and any implementation is stuck infringing the patent claims regardless of whether anybody will ever access the 8.3 filenames. In other words, the patent no longer has any valid technical use other than creating market barriers and collecting licensing revenue.
Re:Who owns it? (Score:3, Insightful)
Re:Who owns it? (Score:2)
And the way I figure it, Microsoft probably doesn't want to be convicted of monopoly practices again - becuase there IS a limit to how far companies are allowed to take capitalism.
Re:Who owns it? (Score:5, Informative)
However look here [gnome.org] and here [redhat.com].
You don't need to sue someone so stifle progress as evidenced by the fact their Mono patents are currently stifling progress by the risk of lawsuits where Microsoft could easily remove that threat.
Re:Who owns it? (Score:2)
constantly (Score:4, Interesting)
In general, merely having a patent stifles progress and is an anti-competitive practice because it forces competitors to work around it, in particular given that Microsoft has threatened to enforce its portfolio and clearly has the means to do it.
Microsoft also uses its patent portfolio to negotiate patent cross licensing agreements and they use patents in the negotiation of individual business deals. And Microsoft uses patents to threaten countersuits when they are threatened with a legitimate patent lawsuit, usually resulting in a cross licensing deal and settlement.
Re:Who owns it? (Score:4, Funny)
Colgate-Palmolive Company, New York, NY 10022.
Re:Who owns it? (Score:2, Informative)
When has Microsoft EVER leveraged a patent to stifle progress? Hell even their FAT and other crap they made is widely used for free, and they have sought NOTHING from it.
Myths are like Rancors, hard to kill, even though they don't exist.
Re:Who owns it? (Score:5, Informative)
MOD PARENT UP. (Score:2)
Re:Who owns it? (Score:2)
Re:Who owns it? (Score:4, Informative)
Microsoft sued lindows for trademark infringement. They also sued a 16 year old boy who had the temerity to register a domain name with his name in it.
Microsoft has repeatedly said they intend to agressively defend their intellectual property.
What makes you think MS will never sue anybody for patent infringement after their top level executives have said they fully intend to?
AJAX and Comet (Score:5, Insightful)
I'm a web developer, and right now I am really getting into the stride of making very good apps, very quickly.
With AJAX, the expectations will rise considerably. The development effort will go way up...all to do the same things we are doing now.
I know that this sounds stupid to a lot of you...but think about games. Better graphics increase development time and effort, but don't necessarily make a better game.
Soon, EVERY web app will need to be an AJAX app...even if it doesn't need to be.
The age of simple software is once again coming to a close.
Re:AJAX and Comet (Score:5, Interesting)
Thats the scary part...
Gregor
Re:AJAX and Comet (Score:2)
Re:AJAX and Comet (Score:5, Insightful)
fuck you, buddy
Really, it's not about making some gigantic labyrinthine application... it's about accomplishing the end goal for the user as quickly, efficiently, and correctly as possible. The web happens to provide some tools that enable massive return on very little code, but that doesn't mean that ALL those who work with it are unable to program larger systems, given a reason to do so.
Re:AJAX and Comet (Score:5, Interesting)
Personally I felt that age of simple web pages slipped away when javascript started becoming popular.
Now to be a web developer its gotten to the point that its difficult to know fewer than 3-4 languages. And its nearly on par with desktop development; but soon will be the day when desktop and internet will be seamless.
Re:AJAX and Comet (Score:3, Interesting)
Re:AJAX and Comet (Score:3, Interesting)
Now that goes right to the heart of why I hate web development. Each of the languages of web design are poky little scriptlets, weak beyond belief, so that to actually *do* something, you need three or four just to get you through it. It's really saying something when you needed four languages to design the page that your web browser displays, but you only needed one to write the web browser itself.
The
Re:AJAX and Comet (Score:5, Interesting)
But I've implemented a few shiny upgrades to older web apps that we run, and people love 'em, and want AJAX in everything. There are a few applications that we maintain that make significant use of JavaScript, and people want to 'upgrade' the JS to AJAX. I've explained over and over again that AJAX is just a particular thing that you can do with JS, it's not something that you replace JS with.
AJAX is a really cool development method, but it's like any other tool--there are certain situations where it helps, and others where you just don't need it.
Re:AJAX and Comet (Score:4, Insightful)
And unfortunately, I'm starting to see sites use it in the same bad ways.
Anyone that decides ajax, java, or flash is a replacement for website navigation is an idiot.
These technologies have plenty of uses to enhance web applications, but as soon as they render my browsers controls unusable, something is wrong.
Re:AJAX and Comet (Score:2)
I'm afraid you may well be right. Most users never touch command-line programs today, even though the command-line is, for many tasks, easier and faster than the GUI equivalent (not to mention the fact that programming for the command line is far simpler). So, yeah I hope it doesn't happen, but it wouldn't be the first time
Re:AJAX and Comet (Score:3, Interesting)
As a user who has had to endure every application being a web application, even if it never needed to be, you're not going to get my sympathy. You're part of the group that created this problem.
I've got no problem with distributed applications, but the idea that everything should be HTML/CSS/Javascript sitting in front of a database is just wrong.
Re:AJAX and Comet (Score:2)
Re:AJAX and Comet (Score:4, Funny)
Re:AJAX and Comet (Score:2)
1st of all, if the calendar system did change, the same change you do to the server can be easily done to the html file.
2nd, there are gazillions of situations one can make up so that it'd be better to have one than the either, but I'll give you the simplest scenario why it's better to do simple things w/o AJAX. Often times a webserver can be up while the database may have crashed or too many users have connected to it. Why update at semi-real-time when you can update at real-time? Why ris
Re:AJAX and Comet (Score:2)
Yes, it' simple (but I wanted something simple to get the hang
Re:AJAX and Comet (Score:2)
Re:AJAX and Comet (Score:2)
With AJAX, the expectations will rise considerably.
I think I'd call tha
Re:AJAX and Comet (Score:2)
What makes you think that AJAX won't be made simple?
For example, how hard is it going to be to detect and download new posts in forums (such as
And it won't be needed for everything, by any means. Just a certain class of web apps which need to be able to run on multiple browsers (and also on dial-up/cell phones).
Re:AJAX and Comet (Score:3, Interesting)
Right now they have flat, nested, no comments, and threaded.
Take something like threaded, then instead of refreshing the whole page when you drill down, just the pull down the comments for that thread.
Re:AJAX and Comet (Score:2)
Kuro5hin [kuro5hin.org] have two dynamic comment modes available. They were written years ago before the AJAX hype, and use inline frames, if I remember correctly.
Re:AJAX and Comet (Score:2)
Re:AJAX and Comet (Score:2)
In our experience, exactly one of the five clients how initially demanded AJAX in a two month period actually required us to do it.
Probably a prelude to changing the way it works (Score:3, Insightful)
Re:Probably a prelude to changing the way it works (Score:3, Informative)
It's true that in the upcoming Internet Explorer 7, the method by which you instantiate the XMLHttpRequest object will change. But you have it completely backwards - they are changing it to be a native object, to be compatible with all the other browsers that implement it, instead of its original ActiveX implementation found in Internet Explorer 5.x and 6.0.
Web 2.0? (Score:3, Interesting)
Memos as Press Release (Score:3, Informative)
Re:Memos as Press Release (Score:3, Insightful)
Please, with the 360 launch, this isn't even a blip on anybody's radar.
Re:Web 2.0? (Score:2)
I for one welcome our new light-blue site of doom overlords.
In other news... (Score:2, Insightful)
These guys are so far behind the times it's not even funny. The next thing you know they'll be talking about how we really need something to search the web with, or an online way to look up an address. Hey, here's an idea, we'll make a website that contains information about stuff and make it editable by everyone.. We can call it a Wiki!
Re:In other news... (Score:5, Funny)
We can only hope.
Re:In other news... (Score:4, Informative)
They already have. [microsoft.com] It also plays video. [microsoft.com] And it was released over a year ago. [engadget.com]
Re:In other news... (Score:2, Informative)
Once again another case of back to the future. Unfortunately I'm sure they will be like all the other SharePoint features - worst of breed in everything that they do. (If you don't believe me just go and have a look at the 'discussion boards' features of SharePoint)
Just imagine... (Score:3, Funny)
Re:Just imagine... (Score:5, Interesting)
Just imagine how...status quo or diminished...Microsoft would be if they weren't intentionally five years late to the party. Seriously.
5 or 6 years ago Microsoft was hugely pushing a lot of very advanced web technologies, including remote scripting, behaviours, client-side XML data islands and heavily programmatically controllable transformations, and even the much-maligned ActiveX. These enabled some remarkable web applications (ActiveX, for instance, allowed you to have auto-updating rich client on the desktop, but retaining all of the advantages of the document model of HTML).
It really was a fantastic platform that they created, and they were light years ahead of everyone else. Of course it was entirely tied to Microsoft's platform and browser, which was why you didn't see it much on public websites, but for internal teams that were up on their chops (most aren't, unfortunately), there were some amazing solutions created.
However Microsoft has a so-called-problem that shops like Salesforce don't - they are pulling in billions upon billions a year from their, err, "legacy" products, and often they're their own biggest competitor. The last thing they want to do is pull the carpet out from under their cash cows and enter into a new competition as a new entrant of sorts, eliminating a huge source of income, and a competitive advantage. It's for this reason that the IE team was disbanded years ago, after they shot far ahead of everyone else.
The revisionist history where people imagine that Microsoft is behind because they're just not as advanced as their competitors really is laughable. Microsoft was a mile ahead and then decided they really wanted to run the 20K instead of the 100m.
Re:Just imagine... (Score:5, Interesting)
Er, "behind" and "less advanced" are synonymous.
If anything that's backwards. Microsoft sprinted to get halfway decent Javascript and XML support, and then decided they'd won the race and stopped dead. There hasn't been an Internet Explorer rendering engine update for over four years now.
Meanwhile, Gecko/Presto/KHTML have made steady progress and had the majority of the capabilities of what will be in Internet Explorer 7 years ago. Microsoft have acted like the hare racing against the tortoise - arrogant enough not to take the competition seriously, and have been overtaken while they weren't looking.
Problems (Score:4, Insightful)
Some of the logic along the way is... problematic.
Microsoft introduced ActiveX to ensure the web was tied to their platform. The reason ActiveX was "much maligned" is because it was just DCOM wrapped up in web semantics. Since DCOM was poorly-designed, ActiveX inherited many problems, including extremely poor security. At the time, CORBA was the standard for remote execution, and although it was a standard, it had many drawback when compared to DCOM-- namely, poor implementations that often didn't work together properly, naming service issues (still a problem, though its getting better), and huge bloat / performance issues.
Their platform was hardly fantastic. It was cobbled together, riddled with stability and security issues, and was tied intimately to the MS-Windows platform. The primary reason nobody adopted it on the web, outside of the compatibility nightmare, was that ActiveX controls required a Microsoft server on the other end, meaning exposing an important service to the internet. I believe that was Microsoft's intent-- get application developers to use ActiveX (most app developers were MS-Windows developers), and force the sysadmins to install MS-Windows servers to support them. But that might just be paranoid delusions on my part.
I'm glad you remember to glory days of ActiveX and IIS servers with such a warm fuzzy glow. All I remember were the serious ActiveXploits [cigital.com], IIS worms [com.com], and performance problems created by this "fantastic platform."
Re:Problems (Score:2, Insightful)
The reason ActiveX was "much maligned" is because it was just DCOM wrapped up in web semantics.
ActiveX was a visual component standard that was really created for Visual Basic. ActiveX had nothing to do with DCOM (of course ActiveX uses COM as the communication method, but in no way does it imply that it's talking to the master via DCOM), but rather was a COM based component that implemented a particular set of visual interfaces t
Re:Just imagine... (Score:3, Insightful)
Actually I think it was b/c of the much-maligned ActiveX security vulnerabilities. There are plenty of ActiveX-less websites that are coded solely for IE anyway, so lack of platform-independence is not really the issue.
Re:Just imagine... (Score:3, Insightful)
Late to the race doesn't make Microsoft a loser. (Score:4, Insightful)
Slashdotters are quick to laugh at Micro$oft, but Microsoft is the one laughing all the way to the bank.
Re:Late to the race doesn't make Microsoft a loser (Score:2)
Re:Late to the race doesn't make Microsoft a loser (Score:2)
Re:Late to the race doesn't make Microsoft a loser (Score:2)
Now if they could just learn ( say catch up a bit ) and
stop acting like they have to own everything software,
maybe slashdotters will stop treating them so terribly.
I thank M$ (Score:3, Insightful)
There you have it Slashdotters. Here, Microsoft has some innovation to show. Sincerely, I have been slashdotting for a long time and can say I have seen very little if anything about M$ being recognized for its innovation.
This I believe, is one of them. Thank you M$.
Re:I thank M$ (Score:2)
I wouldn't really call it innovation. People were doing the same sort of thing beforehand with inline frame hacks. XMLHttpRequest is nicer, sure, but it's a refinement of existing practice rather than something brand-new.
About the only thing I can think of that comes close to being innovative from Microsoft regarding browsers was their "channel" support in Internet Explorer 4, which was subsequently discontinued when the "push" fad ran out of steam. Of course, it was highly derivative of other non-br
Re:I thank M$ (Score:2, Interesting)
As the major advantage of 'AJAX' is that doesn't need that stuff, I guess you could say they invented AJAX...except for the actually useful part of it working cross-platform and transparently. Because of this rather obvious limitation, it failed to actually be used anywhere except intranets.
Part of this wasn't MS's fault, as it was pre-standard DOM, IIRC.
Any idiot can create interesting web technology that operat
unseen memo by Bill Gates (Score:4, Funny)
Stop writing memos.
Failed to exploit? Nah. (Score:4, Funny)
Oh, they managed to exploit it [microsoft.com], albeit indirectly.
Hmmm... (Score:2)
http://www.microsoft.com/windows/default.mspx [microsoft.com]
I'd say they've managed to exploit it fairly directly.
Conflict (Score:4, Interesting)
Take MS vs. Google. Now Google still IMHO does everything before MS, and then MS goes "me too" and issues something similar but yet worse than Google offering. In normal situation - meaning MS has no money to pump from OS/software revenue into new markets they would not get a chance against Google - they will simply bankrupt. Right now they pump the money but I doubt they get any revenue (even to go on zero line) from their web services.
Now as far as I understand they wan't to couple web-based software (more like service) with shrink-wrappedsoftware like Windows and Office. I base that on various interviews with MS execs about MS product line I've read. But this is like flawed idea from the begining. The most valuable part (IMHO) about web software is that it only needs a browser and server infrastructure on the other end. So in fact you do not need to pay any special attention to the client side (as you would have to with shrink-wrapped software). So for e.g. you could have a big extranet with 5000 clients across the world, using one sophisticated application by web and only thing you need is decent server architecture and on client side - commodity: standard browser running on any OS, maybe a printer or smth. to get the job done.
This is completely the opposite of having fat clients loaded with bloated OS and software suites - the MS way.
So I see a conflict here.
Re:Conflict (Score:2)
I had to respond because you bring up a really good point here. I don't have the original author's name, but someone on /. posted about software services a few years ago, comparing Apple to Mi
AJAX good for large services , not small (Score:2, Interesting)
Re:AJAX good for large services , not small (Score:2)
-Rick
Re:AJAX good for large services , not small (Score:4, Informative)
1. Use an existing RPC library, like JSON-RPC for java, to translate your objects and methods. Don't re-invent the wheel.
2. Use an existing AJAX library to wrap the XMLHttpRequest object, like Sarissa.
3. Sprinkle wherever it fits.
It is quie simple actually. I was able to AJAX-ify a few pages of an exisiting app in under a day, giving them quite a more responsive feel.
Never stay up past 11:35am (Score:2, Funny)
Re:Never stay up past 11:35am (Score:2, Funny)
Re:Never stay up past 11:35am (Score:2)
No. Nobody read it as "Baleeted"
That's not even a word
Can't you people just leave me alone?
Re:Never stay up past 11:35am (Score:2)
"'Everything is fine, nothing is ruined'
Another memo (Score:5, Funny)
lmao @ Mark Benioff (Score:3, Funny)
I hate AJAX (Score:4, Interesting)
Re:I hate AJAX (Score:2)
Re:I hate AJAX (Score:2)
I think you mean Java applets. Java is alive and well on the server.
Re:I hate AJAX (Score:2)
It's called 'Atlas' (Score:5, Informative)
Writing code.... (Score:3, Interesting)
They developed the XmlHttpRequest (Score:3, Insightful)
Why not use Java applets? (Score:3, Interesting)
I think that Sun missed the boat on this one. Instead of working on a lightweight JVM for every platform, they kept bloating the language and the implementation. I don't see many Java applets anymore, it's mostly Flash and now AJAX.
What's new about 'AJAX' (Score:2)
I don't recall using any ActiveX; just JavaScript and a little
Belated? bahaha (Score:3, Insightful)
I tired of fud... and this is a big one. (Score:3, Informative)
Ajax = Asynchronous Javascript and XML.
XML is a subset of SGML which existed before M$.
Javascript is a child of LiveScript, both were created by Netscape. Nothing in what is Ajax was ever created by M$ period. The fact that they are able to see the value and talk it up is cool, but they invented none of it.
Now I'm sure someone will bring up M$ Remote Scripting. It like LiveScript where basically in house products. Remote Script did not exist in the public realm. However at the time of it's "creation", M$ was lacking a viable browswer (Definition of Viable is it works.) IE 1.0 and 2.0 where total jokes, 3.0 was the equal of Netscape 1.0 and 4.0 began to work. By this time however both MS and Netscape were fully supporting LiveScript/JavaScript (Sometimes in name only, as each tried to extend beyond the other.)
But in short Please, stop say M$ invented Ajax. This is like claiming that Honda invented the Car. They build them yes but they did not invent them.
Now according to wikipedia something called. Remote Scripting supposedly pre-dated HTTP requests. (according to Wikipedia.) Nope.. sorry didn't. The concept of HTTP requests etc had been layed out for a long time before M$ existed (pre-dating the Altair) But it took Berners-Lee to be able to make it usable and, Stanford Linear Accelorator to do the most important step. Create a Distant End. In fact at the time the ONLY usable OS for this was
Since Remote Scripting required a Java applet to work
So no, I had more to do with Ajax than M$ did. And I had nothing at all to do with the concept.
Re:Open Love Letter To Bill Gates.. (Score:3, Funny)
Let me just say that—
Sorry, Billy got a BSOD. He'll send his message momentarily.
And by momentarily, I mean in no less time than 72 hours.
Re:Another dupe (Score:3, Funny)
Re:Microsoft invented AJAX? (Score:5, Informative)
Do you know what "AJAX" is? It's a term coined by some overpaid design guru talking head to describe technology that has been around, and in heavy use by non-public webapps, for many years.
Microsoft pioneered this whole way of thinking, even if they didn't implement it very creatively on many of their sites, and many of their better ideas (CSS expressions & behaviors, XML data islands) have still not become standards, while others have.
And, yes, I am posting this from Firefox, running on an Ubuntu distro. I am not a Microsoft apologist, but mindlessly parrotting off commonly-believed falsehoods just pisses me off. When IE 5 was first released, it was a groundbreaking app, better than anything else on the market, and many of its innovative features are still unknown to most of the A-List, blogorati circle-jerk web-brochure designers who think making a glorified to-do list is "changing the face of the web".
Re:Microsoft invented AJAX? (Score:2)
Re:Microsoft invented AJAX? (Score:3, Informative)
Re:More MS BS? (Score:2)
Innovation in Unix is expected to be duplicated and improved upon, and is licensed as such.
MS says "Oh, ya, we have that too now." And copies it.
Re:More MS BS? (Score:2)