Get ready because I'm about to rant about why I dislike asp.net! I'm sitting here at work developing another dynamic page that's using gridviews and let me tell you, who ever designed the gridview aspect of the .net framework needs to be hit upside the head with a THICK php book because the whole design is completely horrible in my opinion. It's completely ridiculous to me why something that would take a programmer 30 minutes to finish in php takes ALL DAY to do using a gridview, and the code output is so sloppy it's near un-readable (which i suppose isn't a bad thing for security reasons but for developers it's just god awful). Honestly to work with a gridview you have to meticulously plan, re-plan, plan some more, and then whenever you realize you just can not do what your wanting to do with it, develop a hack to work around it.... I almost feel like I'm missing something? Is there ANY reason for this control to be such a pain to work with? Or is it just another Micro$oft flaw that we must work around?...If anyone could shed some light on this subject It'd be greatly appreciated. I just feel like I'm wasting A LOT of time with this .net garbage
.Net was written by people who write system programs (and get paid to write what they're told to write), not people who have to use them. PHP was written by people who write websites. It shows. And, yes, I share your desire to FTP whoever thought of .Net to a disconnected server.
Sounds about right! I'm just trying to come up with a logical reason why ANY company would PAY to use such a disgusting framework??? Yeah people that work with Micro$oft products generally work for less then people who work in a LAMP stack but...the ends just don't justify the means....it doesn't make sense.... *EDIT* I can't believe I spelled "ridiculous" wrong in the title...FAIL... >_<
To paraphrase an old copout, "You can't get fired for specifying Microsoft." It's the Age of Mediocrity.
LOL I had a networking administration instructor tell us that whenever we moved from linux to windows server and everyone in the class was asking "Why would anyone use windows server?"...Must be a pretty common quote lol I'm developing for a government agency and they have strict standards in which one must follow....trust me, I would have created a work around by now if they'd allow it...having to follow guidelines when programming really blows...takes away from ones creativity
Microsoft isn't a bad choice for server side stuff. I wouldn't use old school asp.net though. That's using 10 year old technology. The newer MVC stuff is a lot easier to work with. The problem really isn't that you are using Microsoft, it's that you are using 10 year old Microsoft.