JavaScript - what will be the substitute for java script

what will be the substitute for java script.

Is there any. please do not say VB.Script

pallav

hello

according to me Ajax/Atlas is partial subtitute for javascript.

JavaScript Alternatives
Published January 3rd, 2006 in Programming. Tags: CSS, JavaScript, Programming.
If you read my article on AJAX & JS yesterday, you know I hate JS with a burning fury. But I am not so crass as to just say “Don’t use JS.” and leave it at that. Believe it or not, there are many enough alternatives to JavaScript; at any rate, there are enough to make it possible to have a beautiful and responsive JS-free site.

In a nutshell, my biggest problem with JavaScript is that it tries to do too much, it has too much buggy code, it is largely not XHTML 1.1 compliant (don’t even think about XHTML 2.0!), and almost never displays the same or even properly across the major browsers. So I’m going to try to find a viable alternative (or mix of alternatives) that will let us accomplish what we need in a way that will display on the major browsers (here taken to be IE7, Firefox 1.5, and Opera 9) in a code-compliant manner, and more importantly in a simple and bug-free shape. Starting from the most “all-in-one” solutions:

Java Not JavaScript obviously, but just Java. The idea may seem laughable now, but was one of the most popular ‘fads’ back in the day to make sites entirely out of Java. And why not? After all, it is server-side script, but it runs in a JVM, which means that in an all-code environment you can modify almost anything you want, from mouse-clicks to mouse-cursors, from new windows to closing old ones; it is all possible. Don’t get me wrong however. I’ll make my stance on Java very clear: Only use Java to make small applications not websites or forms. It loads slow, it runs slow, and users hate it.
Flash Almost exactly like Java, except it is used as a media presentation format rather than a programming language due to its lack of OOP and hooks. Flash applets are generally smaller than Java applets, and are more common and acceptable in the currnet time. Its usage also ranges from entire sites written in Flash (even the NSA!!) to forms, intro movies, interactive games, etc.
Both Java and Flash have the distinct advantage of displaying 100% as-is on any browser or platform with Java or Flash support. It means that every single button will be in the same exact place, it means that roll-overs will be spontaneous and pretty everywhere, and most importantly it means that the web knows no borders or operating systems.

But there is a catch (you should know that by now…)! Both Flash and Java are large, slow, and non-indexable. Skipping over slow and large in todays mostly-broadband world; it is important to realize that they are not machine readable.

Google has no idea what is on your 100% Flash or Java site, and even if you have keywords here or there, there is no content. Also, the two aren’t globally appreciated. For one thing, it is remarkably harder to code a site in Flash or Java than in XHTML + CSS. End users also would rather a quick-loading site that they can search through with ctrl+f without issues, and that they can cut and paste reports from…

Flash and Java are not the ideal solutions we are looking for. Enter the year 2000 (and 6), and with it a web-revolution. Think of it as the dot-com-bust cleanup team. W3C, CSS, HTML 4.0.1, IE6, and the birth of Firefox as a true challenger.

reference

http://neosmart.net/blog/archives/53

Erm -- why do we need a substitute?

Firstly, the neosmart resource that you point to as a reference is quite ill-informed. I don't know whether you are the author or not. Very simply, DHTML = HTML DOM + Javascript.  Apparently the writer needs to do some reading up on the use of the DOM and script to provide a UI experience. And, Javascript has absolutely NOTHING to do with XHTML, although the author clearly states that javascript is "largely not XHMTL compliant". If you read (or write) misinformed stuff like this and mindlessly quote it in response to somebody's question, you are doing them and yourself a disservice.

And finally, Javascript is the PRIMARY ingredient in Atlas / Ajax. To expect Remote Scripting / AJAX to "work" without Javascript is like expecting your car to get you to work with no gas. The fact of the matter is that Javascript, whether used in a web page or as a server-side scripting language, has many features and is highly customizable. And, it will be around for a long time, regardless of "replacement" technology.