I don't suppose it occurred to anyone to just do:
Response.ContentType = "text/xml"
Response.Write strXML
Response.End
I don't suppose it occurred to anyone to just do:
Response.ContentType = "text/xml"
Response.Write strXML
Response.End
@AbbydonKrafts said:
Side note: Why would anyone use JScript (do not confuse that with JavaScript) in ASP? If it's server side, why not just use VBScript?
In spite of its shortcomings, it is actually better than vbscript.
Off the top of my head:
There are other reasons, but I can't be bothered to think of them right now. I'm only glad I don't have to maintain ASP code at all any more...
Also, there's no way to make VBScript not suck...
@dhromed said:
@CodeWhisperer said:@smxlong said:Two, If you have to work 12 or 15 hours a day just to meet deadlines or get code working, that means YOUR CODE SUCKS. Code should not take that much work. Putting in long hours every single day isn't a sign of dedication, but of incompetence.
Get your head out of your ass. Some projects exceed the amount of work that can be done in 8 hours a day, regardless of how uber you think you are. If you haven't had one yet, you haven't been in this business long enough.
-cw
It means the planning department sucks, or the sales/PM routinely promises deadlines that are too early.
That is definitely the truth. Developers should not be held hostage to poor planning on the part business side. If you're putting more than 8-9 hours a day, that is a sign either of bad code (like CodeWhisperer says) or really poor planning.
If you're a manager, either "encouraging" or expecting people to put in long hours, maybe you need to examine what YOU did wrong to make everything so tightly scheduled.
I don't suppose it occurred to anyone to just do:
Response.ContentType = "text/xml"
Response.Write strXML
Response.End