Discussion Locked

Web tools blaze trail to the past

0 helpful
13 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

While Microsoft and other industry giants continue to devise new systems for delivering desktop-like applications over the Internet, Google uses older technology to build its newest applications, such as Google Maps and Gmail. This has prompted developers to reexamine technologies that have been around since the 1990s, such as JavaScript and Dynamic HTML.

Read this story from News.com:
https://www.techrepublic.com.com/2100-10548_11-5621010.html

Then, tell us what you think about this renewed interest in older technologies.

13 replies

by stress junkie

I have, for as long as I can remember, been SICK TO DEATH of seeing some new network "protocol" created for every stupid little thing that anyone wants to do over a network. One of the things that I liked best about creating software was figuring out how to accomplish the goal using the limited set of tools avaiable in the programming language and the platform that the software would run on.

by johnofstony

Why the endless drive for 'new technology' (in all aspects of computing)? Why not work on an existing system until it's solidly reliable? Every time a new operating system (or version) is released, it is guaranteed that there will be new bugs not present in the software it's designed to replace. Moreover, in the case of Microsoft, the look and feel and even the terminology keeps changing. Why? If an international law was passed making it obligatory for operating systems to reside in ROM in a PC (i.e. the O.S. couldn't be updated without physically opening the PC and changing the ROM chip(s)), the creator of the O.S. would have to get it right before release, purely on economic grounds. Carry on Google!

by peter_es_uk

Some of lifes developments are really good but 'upgrades' based more on the need to keep an industry giant's balance sheet looking good frequently are not.

by bhunsinger

Funny how when it is not done my someone for money the words 'stitch, force, kludge' are used to define an improvement. So google lead the way and helpped show other what can be done, without buying somone elses kludge. Great

by not again

Good for Google. I, too, am tired of the deluge of "newer and better" stuff. Add the increasing number of markup languages to that as well.

by jaqui

advocating getting rid of clientside scripting and all these other bells and whistles for a long time.
with server side techniques, specially with xml/xhtml you don't need to steal processing from site visitors to do these fancy tricks.

by iver

Although significant develompments are made from time to time, I feel that the value of really knowing your language and tools in most cases outweigh the advantages of implementing new stuff by far. You end up spending so much time just getting to know yet another technonogy or language and that time could in most cases be better spent on doing actual development. It should at least be several years between every time you have to start from scratch with a new technology! Don't let the big companies trick you into thinking otherwise. They just want to make money on new products.

by sremiger

I think javascript and DHTML is great. I use it all the time even in the ASPDOT application. Without DHTML the number of round trips to the server would get way out of hand. I think the client would be frustrated and the Company supporting the application would be frustrated. To me javascript makes an internet application a little closer to a desktop application. I wish Microsoft would spend on tenth of it Marketing budget on Tools to enhance deloveping javascript for both IE and Mozilla standard scripts. It would save the development world a lot of money not having to test in two differnet environments.

by soeki

putting the incorrect claim about Google Maps aside.
Gmail stands out alone... still its a great
acomplishment for something as Old(relatively speaking) as JavaScript.

by grantwparks

...for instance, if JavaScript is "a potential threat to...Java" - uhm, which came first? There is also very little "new" technology in .NET. It is a new focus for MS platforms, but from my POV it is mainly wrapping a class system around a bunch of methods that have been used successfully in the past by those who dug around a little.

To me, the real difference is: giant, monolithic, monotechology application development within a vendor's framework vs. structured layers of elegant, simple components built using mostly open standards. XML technologies - in their native
incarnation, not all wrapped up in a language's class hierarchy - give a level of transparency, reuse and light weight to an application that is unattainable with the former method.

And while it may be "...really, really, really hard to build something like Google Maps", with their preloading of tiled images, etc., I was using client-side JavaScript objects and XMLHttpRequests through hidden frames over three years ago to fetch and repaint only those page components that needed to be changed. I'm sure there are other developers who were, too. It's not rocket surgery.

I keep saying to those who will listen: "It's not the technology being used that's crucial. It's the people using it and whether they fully exploit its capabilities."

by jaqui

they should use server side code.

clientside is theft of computer services under laws passed in support of distributed computing for .net framework.
so any clientside code means pay client ( site visitor ) for cpu usage.

javascript/dhtml is not good in that respect.

xml/xhtml is server side work.

aww no clientside no fancy aniated meues.
that's okay, they aren't needed anyway.

by algernon28

By the way... javascript is out in a number of version, and not all of them are compatible with all of the browsers.
And what about browsers with javascript disabled? DO you mean they should be forced to keep it enabled to have anything working?

by grantwparks

Compatibility: The only compatibility issue I'm familiar with is non-standard uses of the DOM to access page elements and for event handling. In those cases the code can be written that will work on all popular browsers. E.g. document.getElementById('X'); instead of document.all.X;. There are already plenty of compatibility issues regarding IE's non-standard HTML/CSS rendering - so if you are having to overcome that already... Jacqui is right in saying that if *everything* is done on the server and *only* static X/HTML is sent to the browser, most issues are protected against, but even then you have the above-mentioned problems with rendering in the browser and a pretty weak user experience. Sites that just "sit there" are not very popular with most Web surfers.

Script enablement: If a page uses Flash, or a Java applet or certain other technologies, their engines have to be downloaded and enabled for them to work. In Google maps' case, I haven't tried it without javascript enabled, but a page may lend itself to coding for "graceful degradtion" - where, say, the map would be displayed with all the pretty stuff, but you couldn't drag it/zoom it without going back to the server. And I'm wondering: is the reason most people disable JavaScript to prevent pop-ups? To remedy that, I recommend switching to a better pop-up blocking browser like Firefox.

This discussion is closed to new replies.