Mar 21, 2010 06:01 AM|gunteman|LINK
But from a team lead perspective, "drag and drop and controls" may sound like something that can boost RAD in terms of productivity
I think the key word here is"may". Drag and drop can definitely be a productivity booster in many environments, but when it comes to web development and HTML it tends to get in the way instead. The reason is simply that the complexity that the WYSIWYG, Drag
and Drop and Components attempt to hide, isn't very complex at all, and even novice developers with very basic application scenarios will very soon want access to the innards of the rendering process. Even WYSIWYG HTML editors, such as Adobe DreamWeaver, have
a very limited market penetration, simply because the things they hide are things most developers actually want access to. They're great tools, but more often than not they're used as text editors with powerful HTML support, and the WYSIWYG/Designer modes
are left unused.
While WebForms have indeed succeded in many areas, the abstraction layer that it had to introduce certainly didn't come without sacrifice. On these forums, questions like "how to include a link in a grid?" or "how to post to a different page?" or "how to
make one table row in a different color?" are not uncommon. Ask the same questions on a PHP forum and the response will be "Huh? You're kidding, right?". We're spending a worryingly large amount of time solving issues that has never been an issue in (most)
other environments and the time we were supposed to save by using a smart framework is eaten up.
That said, if someone wants to build an MVC view engine with some kind of component support and maybe even a bit of design time support, I'm all for it, but I don't think that Microsoft should introduce more complexity into the framework, only to get more
stuff that looks fabulous on the product demos but end up becoming hurdles instead.