Earlier quoted context omitted.
Yeah, dont credit Apple for ipod, iphone or ipad, dont credit Mark Zukerberg for social networking, Bill Gates to bring philanthropy to main stream, a government to find the terrorist of Boston attacks, It was all inevitable!
This childish, sarcastic style of response is increasingly common on here. That isn't a good thing. If you want to specifically address something I've said, stick to that.
Ask HN: Who built XMLHttpRequest at Microsoft in 1999?
41–50 of 59 posts
Re: Ask HN: Who built XMLHttpRequest at Microsoft in 1999?
#42Earlier quoted context omitted.
Yeah, dont credit Apple for ipod, iphone or ipad, dont credit Mark Zukerberg for social networking, Bill Gates to bring philanthropy to main stream, a government to find the terrorist of Boston attacks, It was all inevitable!
This childish, sarcastic style of response is increasingly common on here. That isn't a good thing. If you want to specifically address something I've said, stick to that.
Re: Ask HN: Who built XMLHttpRequest at Microsoft in 1999?
#43Who's idea was it, and who built it? While history generally gets rewritten towards a simplified, single-victor model (e.g. Edison and electricity, Ford and assembly lines), there is no simple answer to this because the need for a scripted way to load and consume content was very widespread. There were a number of solutions at the time. The most prevalent was simply having a hidden iframe (which actually worked quite…
The only HTTP suite that comes to mind is Indy, or WinShoes back then
Re: Ask HN: Who built XMLHttpRequest at Microsoft in 1999?
#44I love getting history like this. I'll add to the question if any Microsoftians are around: who decided to call it XMLHttpRequest?
Re: Ask HN: Who built XMLHttpRequest at Microsoft in 1999?
#45Re: Ask HN: Who built XMLHttpRequest at Microsoft in 1999?
#46Earlier quoted context omitted.
Wow everybody serious on ycombinator. Can't even make a joke about Al Gore anymore.
That's because that joke stopped being funny 10 years ago.
Re: Ask HN: Who built XMLHttpRequest at Microsoft in 1999?
#47It would be remiss to not mention Shawn Bracewell in the discussion. According to Alex Hopmann, Shawn was responsible for adding asynchronous support: "Step one was to bring the code up to production quality so we got Shawn Bracewell, one of the devs on the OWA team to take it over. Being a smart guy he promptly threw away all of my code and rewrote it in a more solid fashion, adding async support, error handling and…
Sounds like Shawn Bracewell is the person to really credit — non-asynchronous XHR is unusable, and unused. Jim's remarks here are a little over the top. At KnowNow in 2000 we were asynchronously getting data from the server and preserving document state on the client by implementing Comet in in Netscape 4 (and IE 4), by using a frameset with zero-height frames. These days long-polling frames that finish loading when…
Re: Ask HN: Who built XMLHttpRequest at Microsoft in 1999?
#48Who's idea was it, and who built it? While history generally gets rewritten towards a simplified, single-victor model (e.g. Edison and electricity, Ford and assembly lines), there is no simple answer to this because the need for a scripted way to load and consume content was very widespread. There were a number of solutions at the time. The most prevalent was simply having a hidden iframe (which actually worked quite…
There were also various java applets which more-or-less did something similar, and had the advantage of being semi-cross-platform. (Microsoft's was called "remote scripting"[1] and was pulled after they lost the Sun lawsuit.) [1] http://www.ibm.com/developerworks/web/library/wa-resc/
Getting an attractive UI was rough going, but I wasn't much worried about that at the time...
An applet could also make JavaScript calls, so it was also possible to pass data back into JavaScript on the page. That was a technology that came from Netscape, but MS copied -- so (strangely enough) there was a Java package included in Microsoft's jview distribution that had "com.netscape.livescript" (something like that) in the name.
Re: Ask HN: Who built XMLHttpRequest at Microsoft in 1999?
#49It would be remiss to not mention Shawn Bracewell in the discussion. According to Alex Hopmann, Shawn was responsible for adding asynchronous support: "Step one was to bring the code up to production quality so we got Shawn Bracewell, one of the devs on the OWA team to take it over. Being a smart guy he promptly threw away all of my code and rewrote it in a more solid fashion, adding async support, error handling and…
Sounds like Shawn Bracewell is the person to really credit — non-asynchronous XHR is unusable, and unused. Jim's remarks here are a little over the top. At KnowNow in 2000 we were asynchronously getting data from the server and preserving document state on the client by implementing Comet in in Netscape 4 (and IE 4), by using a frameset with zero-height frames. These days long-polling frames that finish loading when…
Re: Ask HN: Who built XMLHttpRequest at Microsoft in 1999?
#50It would be remiss to not mention Shawn Bracewell in the discussion. According to Alex Hopmann, Shawn was responsible for adding asynchronous support: "Step one was to bring the code up to production quality so we got Shawn Bracewell, one of the devs on the OWA team to take it over. Being a smart guy he promptly threw away all of my code and rewrote it in a more solid fashion, adding async support, error handling and…
Sounds like Shawn Bracewell is the person to really credit — non-asynchronous XHR is unusable, and unused. Jim's remarks here are a little over the top. At KnowNow in 2000 we were asynchronously getting data from the server and preserving document state on the client by implementing Comet in in Netscape 4 (and IE 4), by using a frameset with zero-height frames. These days long-polling frames that finish loading when…
I wouldn't say this at all. We could have gone in a completely different direction with Javascript, even back then: spawning numerous lightweight processes running userspace code which then sit in a blocking "receive" state whenever they want to wait for the result of an XHR. In other words, Javascript could have been Erlang for the browser, instead of the odd OS7-like cooperative-multitasking abomination we have now.
(What we did get are Web Workers, which are full OS threads you can't even message if they're doing something synchronous. What's even the point of these?)