Quote:
Originally Posted by CeciL  Uhh no.
You CAN use VBscript within ASP.
You can also use VBscript client side. (THIS usage is the commonly referred to VBscript, in web dev)
ASP is only server side.
Instead of using VBscript you can use Javascript.
Anyway the point is you were talking about how php is written along side the HTML, that is why you switched. That is one of the main reasons ASP was created. |
Somehow we are talking past each other, Cecil. I didn't say you can't use VBScript within ASP. My point was exactly the opposite.
Yes, in classic ASP you can also use VBScript client side, but virtually no one does, in part because the only place that will work is in Internet Explorer.
Yes, I was talking about how PHP is written within HTML, as is VBScript in classic ASP. I switched AWAY from classic ASP / VBScript for that reason.
Sure, ASP was created for that purpose ... that wasn't my point. My point is, it has its limitations, and I liked ASP.NET much better for non-trivial applications.
All that said, you can write great software (or crap) in any language. The language and platform are not the biggest variable in software quality / viability, not by a long shot. The best advice overall is probably, pick what you're most comfortable with and pursue excellence with it.
The only fly in that ointment is that some clients have Religious Beliefs and if you want to work with those clients you generally have to use the Majick that they believe in. If they think for example that Java is the One True Server-Side Language, then you either move on, or nod solemnly and use Java.
The hedge here is that you can easily be proficient in several languages. Once you're learned one or two, additional ones are no big deal. In fact to do web development you have to know:
HTML
JavaScript
At least one server-side language
... so it you have the spare time and energy, consider learning 2 or 3 server side languages. You'll be more marketable, if not necessarily more competent. By and large, businesses are still pretty unsophisticated in hiring software development talent, and tend to use useless criteria like "years of experience" in specific languages rather than looking at much more important things like problem-solving chops, your approach to the craft, your QA techniques, and the points of similarity between the project(s) they want you to work on and the project(s) you've done in the past.
And then there is the question of platform (.NET, classic ASP, Tomcat, etc). Learning a platform and the popular libraries that work with it can be a bigger job than learning the language(s).
--Bob