• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Future of JavaScript?

 
Lane Liles
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Ok, I gotta get my name in the hat for that book My question is honest though...

My question for the authors concerns the performance, support, and future of JavaScript as a language, and it's implementation in the browsers. Before AJAX, JavaScript seemed to have a bad reputation, or at least was relegated to very minimal tasks in web development, due to concerns over security, non-standard implementations, and a seemingly overall dislike among web developers for a host of legitimate and illegitimate reasons. As such, it seems JavaScript hasn't gotten the love it needs from developers, browser vendors, etc. to really be a good language to develop in... which is probably one of the biggest complaints against doing AJAX now (no standard IDE/debugger or language reference/implementation). Now that AJAX has hit the big time, can we expect to see improvements to the language, the development tools, and the implementations in the browsers? I know that's a big, open ended question, with no definite (or maybe an obvious) answer, but I'm curious what the author's thoughts are on the subject, and if they have any specific knowledge they could share about the future and direction of JavaScript (new tools, announcements from W3C or browser vendors, etc.).
 
Eric Pascarello
author
Rancher
Posts: 15385
6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
There has always been a new version of JavaScript standards out there, 2.0, but no one has implemented them yet. I think Mozilla is moving to 1.6 soon which is their own improvements.

JavaScript has always gotten a bad rap and still does. Reason why is developers are stubborn and too lazy to make things work. I know this for a fact since I been dealing with JavaScript since it basically started 9-10 years ago. It has improved and the tools have improved.

Now I still code all of my JavaScript in notepad. I do nto need intellisense or any of syntax highlighting since I have been coding in it for a long time. Tools like EditPlus2, Mozilla's editor and some other make it a little easier to code, but they are no match for other ides.

People need to learn you are talking about a browser market that was trying to outdo each other from the start. Netscape came up with this, Microsoft came up with that. Since they were fighting for the market, there was no standards. Finally standards started to happen, but the browsers still had to allow their old code to still run. So you still have issues with bad coding out there.

If you pick up a good book, look at some good websites, and bang your head a few times, then you should have no problem. I say if you do not win the book, pick it up and it will show you that JavaScript can be OO in nature and give you an easy way to add Ajax to any web page.

I would say that most people out there have no clue how to write a prototype with JavaScript. With that, it makes developing so uch fun.

I could talk all day about this stuff.

Eric
 
Stephen Cote
Greenhorn
Posts: 9
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I think JavaScript has a lot of hidden and untapped potentional. I also think that potential has been already tapped, and only awaits rediscovery. Asking where it is going makes me wonder whether we need to re-examine the entire principle of the Web. The more we move JavaScript and Flash and XML and ActiveX towards a programming environment, the closer we return ourselves to a mainframe culture. How is improving JavaScript, et al, to the point that it becomes its own uber-language any different than the same mainframe environment that existed thirty years ago?
 
David C. Crane
author
Ranch Hand
Posts: 59
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Yup, Doug Crockford says it all in his essay "The world's most misunderstood programming language". I'd been using it for several years before I realised what it was capable of. IMO prototype.js has helped a lot here, by writing in a style that's initially so unfamiliar to the casual JS programmer, but that leverages the natural advantages of the language so well.

Dave
 
dema rogatkin
Ranch Hand
Posts: 294
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
JavaScript had always a good reputation especially in hands of web designers. Developers seem ignored it for awhile, so I understand your concerns. I wish JS had more power to eliminate completely client side programing using heavy stuff as applet, activex or flash.
 
It is sorta covered in the JavaRanch Style Guide.
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic