OK, I fully admit the history of javascript is something I'm not extremely knowledgeable about. I also am aware people are using javascript outside of the browser these days. However, since to date, javascript is primarily a browser based language, why don't they use some of the fundamentals that the browsers use?
Simply, make the new version (and future versions) declare their version to the browser, and the browser can then handle how to run. Microsoft can treat it like a new language, Mozilla can handle it they way they want to, and people running older browsers will be oblivious to it all (as long as however it identifies itself doesn't break the previous version).
So the new version would have something like//ECMAScriptv4.00
at the top of every line of javascript that needs the new interpreter. True, we spend more bandwidth, but in todays age of gzip compression everywhere, is it really going to matter?
Can your dev tools be tuned to be more efficient with memory use? I'm not sure what you mean by "dev tools", but if we're talking IDE's and such, a lot have bells and whistles that you may not even be using, that you can turn off.
I'd also look at your own work habits and see what you have running that can be turned off. For example, on my laptop I was frustrated with the long boot time when I had apache and mysql installed, when I wanted to use it for purposes other than development. What I did was created a developer account which turned those applications on, and a generaluse account for when I just wanted to surf or play games.
Try exiting out of things when you don't need to be in them. Unless you're really pushing your memory limits with a single application, chances are the applications you close will be cached to load quickly enough for use without becoming too much of a time sink.
If all that doesn't help, it might just be time to stop and realize that you're using a system developed for portability and lower power consumption, when you in fact need a system tuned specifically for performance.
Well maybe not so simple, I guess I'll leave that up for you to decide. The answer though, whichever system is easier for you (and your team) to work with and maintain.
On many small projects where I'm the only developer, doing both logic and layout, I had no problem keeping everything embedded. Now, for me personally html is a lot easier to look at in blocks, for example
However, I also have worked with people I didn't want anywhere near my logic. So I'd use templates and only give them access to those (helps when you're both sysadmin and developer).
Much like the various languages out there, your development style is often something that falls under the category of "right tool for the job".
Embedding everything in your code will make it more difficult for people to come behind you and make updates, especially to layout. Maybe even more difficult for you to edit them yourself after not touching it for a few months/years.
Slashdot Mirror
They tend to have a little less American diplomat blood though
OK, I fully admit the history of javascript is something I'm not extremely knowledgeable about. I also am aware people are using javascript outside of the browser these days. However, since to date, javascript is primarily a browser based language, why don't they use some of the fundamentals that the browsers use? Simply, make the new version (and future versions) declare their version to the browser, and the browser can then handle how to run. Microsoft can treat it like a new language, Mozilla can handle it they way they want to, and people running older browsers will be oblivious to it all (as long as however it identifies itself doesn't break the previous version). So the new version would have something like //ECMAScriptv4.00
at the top of every line of javascript that needs the new interpreter. True, we spend more bandwidth, but in todays age of gzip compression everywhere, is it really going to matter?
Can your dev tools be tuned to be more efficient with memory use? I'm not sure what you mean by "dev tools", but if we're talking IDE's and such, a lot have bells and whistles that you may not even be using, that you can turn off. I'd also look at your own work habits and see what you have running that can be turned off. For example, on my laptop I was frustrated with the long boot time when I had apache and mysql installed, when I wanted to use it for purposes other than development. What I did was created a developer account which turned those applications on, and a generaluse account for when I just wanted to surf or play games. Try exiting out of things when you don't need to be in them. Unless you're really pushing your memory limits with a single application, chances are the applications you close will be cached to load quickly enough for use without becoming too much of a time sink. If all that doesn't help, it might just be time to stop and realize that you're using a system developed for portability and lower power consumption, when you in fact need a system tuned specifically for performance.
Well maybe not so simple, I guess I'll leave that up for you to decide. The answer though, whichever system is easier for you (and your team) to work with and maintain.
On many small projects where I'm the only developer, doing both logic and layout, I had no problem keeping everything embedded. Now, for me personally html is a lot easier to look at in blocks, for example
print EOF
blah blah blah
blah
blah blah
EOF
instead of
print "blah blah blah\n";
print "blah\n";
print "blah blah\n";
So I'd often do that.
However, I also have worked with people I didn't want anywhere near my logic. So I'd use templates and only give them access to those (helps when you're both sysadmin and developer).
Much like the various languages out there, your development style is often something that falls under the category of "right tool for the job".
Embedding everything in your code will make it more difficult for people to come behind you and make updates, especially to layout. Maybe even more difficult for you to edit them yourself after not touching it for a few months/years.
Is javascript using some of the more well known frameworks/scripts (ie: dojo or prototype) allowed?