I've never really looked into ASP.net, but I know a TON of people that have been turned down for jobs because they don't know it. It's a shame that so many businesses are that hell-bent on being inefficient.
Actually, I'm currently in love with Ruby on Rails. Ruby being the language, Rails being the framework. Ruby is elegant and succinct. Rails plays off that elegance, relies heavily on convention (file paths, server environment, etc), and makes problems a lot of web developers face dead simple.
And I've found out in the past week that Internet Explorer has a lot of cool little doodads that aren't supported by Firefox. or Opera. or the whole friggin W3C. either Microsoft has to stop trying to control the internet, or the rest of the world has to start catching up with the few good ideas in IE's library. >_<
To their credit, Microsoft invented XMLHttpRequest. Although I wouldn't be surprised if that opened up many security holes for them.
If Microsoft wants to innovate, let them! In fact, more power to them. All I would ask is that they do it with the W3C in mind, so they can make it a standard too. Share the wealth, Microsoft!
Yeah, that's what I'm saying. Stuff like outerHTML, which would be really useful for web designers everywhere. But load it into Firefox, and Firefox says "wtf is outerHTML? I'm not going to let your code work." >_< So right now it's the W3C who's trying to catch up with Microsoft, instead of the other way around. Bah.
Isn't XMLHttpRequest the thing that makes AJAX work? Hot shit, if it is. So do all the other browsers support XMLHttpRequest now?
Ack. OuterHTML isn't very safe. I can't think of any good use for it either, unless you want to replace the element or modify its attributes. Replacing it would eliminate that element's ID, rendering it more or less useless if you wanted to modify it in the future. If you wanted to modify it, you may as well just use the other DOM functions to modify the attributes directly, rather than replacing the markup that represents them.
I dunno. Maybe there's some use for it that I'm just not seeing...
I wouldn't mind discussing this further over AIM :)
Comments 6
I've never really looked into ASP.net, but I know a TON of people that have been turned down for jobs because they don't know it. It's a shame that so many businesses are that hell-bent on being inefficient.
As a computer scientist, that grinds my gears. >_
Reply
http://rubyonrails.com
Reply
And I've found out in the past week that Internet Explorer has a lot of cool little doodads that aren't supported by Firefox. or Opera. or the whole friggin W3C. either Microsoft has to stop trying to control the internet, or the rest of the world has to start catching up with the few good ideas in IE's library. >_<
bah! i hate computers!
Reply
If Microsoft wants to innovate, let them! In fact, more power to them. All I would ask is that they do it with the W3C in mind, so they can make it a standard too. Share the wealth, Microsoft!
Reply
Isn't XMLHttpRequest the thing that makes AJAX work? Hot shit, if it is. So do all the other browsers support XMLHttpRequest now?
Reply
I dunno. Maybe there's some use for it that I'm just not seeing...
I wouldn't mind discussing this further over AIM :)
Reply
Leave a comment