5 ms·
I used this and it was incredibly slow. Clicking the arrow buttons moved the map by a fixed amount. In my opinion the breakthrough of Google Maps was the Java
by rwmj 11y ago
I used this and it was incredibly slow. Clicking the arrow buttons moved the map by a fixed amount. In my opinion the breakthrough of Google Maps was the Javascript interface that let you slide around and zoom in and out, plus the engineering behind it that served the map tiles quickly.
- joezydeco 11y agoI used it too and, indeed, it was slow - but I was also using it on a Pentium 90 CPU and a 28.8kbit/sec internet connection. I don't know if gMaps would have run any faster on that hardware back then, especially if it was all jscript-driven.
- rev_bird 11y ago>especially if it was all jscript-driven This is going to reveal an embarrassing lack of historical context, but could Google Maps have run in the Javascript of the '90s? Has the language changed significantly since then, or do we just... use it for everything now?
- ksherlock 11y agoJScript was introduced with IE 3 (1996) Dynamic HTML (modifying the page with javascript) was introduced with IE 4 (1997) iframes were introduced with HTML 4 (1998) I think. XMLHttpRequest was introduced with IE 5 (1999) So 1998 era, maybe, but Javascript had a reputation as being slow and buggy. Flash, Java applets, and even active X were more acceptable technology at the time. (Not trying to dismiss Netscape in my timeline -- I wrote it with respect to Microsoft implementing it.)
- Retric 11y agoClassic embrace, extend, extinguish, JScript(1996) was like JavaScript(1995), but a little late and not quite the same thing. Which made JavaScript seem a lot more buggy than it was because MS implemented something just a little different.
- deleted 11y ago[deleted]
- mcintyre1994 11y agoAs I understand (per Wikipedia [0]) Microsoft invented XMLHttpRequest in 1999 and nothing we now consider Ajax could really exist before that. [0] https://en.m.wikipedia.org/wiki/XMLHttpRequest https://en.m.wikipedia.org/wiki/XMLHttpRequest
- joezydeco 11y agoWe now have the horsepower in the browser to do it. We're a long way from 80586s at 90Mhz with 4MB of RAM and 60MB of disk.
- icebraining 11y agoNot just that, but the current engines are much more efficient as well. For example, when the first JIT engine was released for Firefox, it was an order of magnitude faster than the previous engine, even on the same hardware (for pure computation).
- notahacker 11y agoEven if similar code could have been written, it couldn't have been usable on the average home internet connection at the time...
- johansch 11y agoI also used it just when it was introduced, but with a 2 Mbit/s uplink at work. And a 10 Mbit/s student residential uplink at home connected to a 34 Mbit/s link that the Linköping University had via Swedish University Network (SUNET). (Back then 34 Mbit/s was something fantastic!) I probably used a P133 with Linux at home and a 110 Mhz Sparc 5 at work. And Netscape was the browser in both cases. My vague memory from then is that the server was super slow, and that my connection wasn't the limiting factor. Still, it was fascinating to play with for a few hours. This was before P2P pirating was a big thing. Pirating was mostly done via SMB shares in the local network (no-one was afraid of getting caught since the authorities had no clue at all, and also because it felt like we were spearheading something new and interesting), so the external link didn't suffer. Online video at that time was like 50 kbps RealVideo streams, at most.
- rev_bird 11y ago>Back then 34 Mbit/s was something fantastic! I can't even get 34 Mbps now. This was 20 years ago?
- johansch 11y agoWell, it was shared by like 20k (occasional) users and 1-2k students with campus Ethernet network connections. (Still, it never really got saturated. There wasn't that many interesting AND bandwidth-consuming services out there in the rest of the world.) I think Sweden was quite good at getting people connected at decent speeds. In retrospect, I think this was a very wise way to spend tax money. My personal Internet-connection history goes like this: 1994: 28.8 kbps modem at home in a small village. It cost like $2/hour. 1996: 10 Mbit/s - residential student university network, for like $10/month 2000: 10 Mbit/s - moved away from the student area to an apartment with a commercial connection (Bredbandsbolaget - they got loads of investements, some of it in the form of hardware from Cisco). $30/month 2002: Upgraded to 100 Mbit/s. $30/month 2009: My homeowner association accepts a 10 year deal where all apartments get 100 Mbit/s Ethernet-based access for $10/month (in exchange for "monopoly" - everyone needs to pay $10). (Since 1996, it's been all direct Ethernet, no silly old stuff like DSL or cable.)