Comments on: Why JavaScript Sucks http://www.searchengineoptimizationjournal.com/2008/10/31/javascript-sucks/ Search Engine Optimization Journal is an SEO Blog that contains usefule articles, tips, resources and news about SEO. Thu, 02 Feb 2012 18:02:06 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Nick Stamoulis http://www.searchengineoptimizationjournal.com/2008/10/31/javascript-sucks/comment-page-1/#comment-106001 Nick Stamoulis Tue, 29 Jun 2010 18:36:11 +0000 http://www.searchengineoptimizationjournal.com/?p=1653#comment-106001 Hi Ryan, Great points and thanks so much for sharing your thoughts! Hi Ryan,
Great points and thanks so much for sharing your thoughts!

]]> By: Ryan http://www.searchengineoptimizationjournal.com/2008/10/31/javascript-sucks/comment-page-1/#comment-105958 Ryan Tue, 29 Jun 2010 15:18:14 +0000 http://www.searchengineoptimizationjournal.com/?p=1653#comment-105958 This article focuses solely on using javascript for menus as a bad option. While that maybe true, there are more reasons than just using it for menus that javascript is bad in general. For one it's way too forgiving. While, I realize there was some intent there, but it increases coding time playing around with it. It's also a non-standard "standard". Meaning, it does technically have a standard to follow. But implementers implement things anyway they feel like. So you can never be guaranteed anything will work the way you think it should. Even between versions of web browsers. Granted, I suppose that can be said about for most languages. Look at C/C++. There are probably thousands of variants and not all of them work basically the same way. But usually, the associated compiler can tell you if you've done something wonky. There is no such device for javascript. So your code gets littered with a buch of if that browser in that one version or that other version style code. For web 3.0/4.0 or whatever, what we need is a complete redesign. HTML is great for displaying documents. But it's not great at doing things like displaying forms or applications. Which is what we are moving too. You have all these technologies which were designed separately and never really designed to work together well all duct taped together. It's looks horrible and to do anything "cool" you have to hack around design flaws and use tricks. An obvious sign that we are stretching the capabilities of the language(s). Anyway, I can rant on and I'm sure not everyone agrees with me and that's fine. But if you take a moment to look at all the html/javascript/asp/php/etc out there. What you'll see is a bunch of junky spaghetti-style code like what you would see from the 70's. Our modern programming languages may still have there flaws, but real coding is a lot more elegant today than a few years ago. I just would like to see the web get out of the 70's. I doubt you can make a serious argument against that. This article focuses solely on using javascript for menus as a bad option. While that maybe true, there are more reasons than just using it for menus that javascript is bad in general. For one it’s way too forgiving. While, I realize there was some intent there, but it increases coding time playing around with it. It’s also a non-standard “standard”. Meaning, it does technically have a standard to follow. But implementers implement things anyway they feel like. So you can never be guaranteed anything will work the way you think it should. Even between versions of web browsers. Granted, I suppose that can be said about for most languages. Look at C/C++. There are probably thousands of variants and not all of them work basically the same way. But usually, the associated compiler can tell you if you’ve done something wonky. There is no such device for javascript. So your code gets littered with a buch of if that browser in that one version or that other version style code.

For web 3.0/4.0 or whatever, what we need is a complete redesign. HTML is great for displaying documents. But it’s not great at doing things like displaying forms or applications. Which is what we are moving too. You have all these technologies which were designed separately and never really designed to work together well all duct taped together. It’s looks horrible and to do anything “cool” you have to hack around design flaws and use tricks. An obvious sign that we are stretching the capabilities of the language(s).

Anyway, I can rant on and I’m sure not everyone agrees with me and that’s fine. But if you take a moment to look at all the html/javascript/asp/php/etc out there. What you’ll see is a bunch of junky spaghetti-style code like what you would see from the 70′s. Our modern programming languages may still have there flaws, but real coding is a lot more elegant today than a few years ago. I just would like to see the web get out of the 70′s. I doubt you can make a serious argument against that.

]]> By: Chris McElroy aka NameCritic http://www.searchengineoptimizationjournal.com/2008/10/31/javascript-sucks/comment-page-1/#comment-27009 Chris McElroy aka NameCritic Mon, 03 Nov 2008 13:46:37 +0000 http://www.searchengineoptimizationjournal.com/?p=1653#comment-27009 The poster is obviously talking about using javascript in the code for the nav menu rather than putting the code into an external file and calling it from the code. In that case, the poster is absolutely correct. A lot of people, including me, do not recommend windows servers. There are good reasons for that. If windows servers are so great, why do you have to use a LAMP to make things work on it? The poster is obviously talking about using javascript in the code for the nav menu rather than putting the code into an external file and calling it from the code.

In that case, the poster is absolutely correct.

A lot of people, including me, do not recommend windows servers. There are good reasons for that. If windows servers are so great, why do you have to use a LAMP to make things work on it?

]]> By: Neal G http://www.searchengineoptimizationjournal.com/2008/10/31/javascript-sucks/comment-page-1/#comment-26860 Neal G Fri, 31 Oct 2008 16:34:28 +0000 http://www.searchengineoptimizationjournal.com/?p=1653#comment-26860 I fail to see any relationship between ASP and SEO/a bad site. The server side code has little to do with the quality of a website. " you guessed that ASP is littered with code that bogs down your website, you’d be right. Just like the Windows server, it’s got all kinds of useless code added in that makes it more difficult for the search engines to crawl your website. Build your website in HTML. It will get crawled better and will be more likely to get indexed by the search engines." ASP is not HTML. You can output HTML with ASP but that statement makes no sense. When you said "Build your website in HTML" i think you meant to say php, jsp or some variant. I fail to see any relationship between ASP and SEO/a bad site. The server side code has little to do with the quality of a website.

” you guessed that ASP is littered with code that bogs down your website, you’d be right. Just like the Windows server, it’s got all kinds of useless code added in that makes it more difficult for the search engines to crawl your website. Build your website in HTML. It will get crawled better and will be more likely to get indexed by the search engines.”

ASP is not HTML. You can output HTML with ASP but that statement makes no sense. When you said “Build your website in HTML” i think you meant to say php, jsp or some variant.

]]>