Porky Microsoft Visual Studio way over the hill

The latest incarnation of Visual Studio had a difficult gestation, with critics pointing to the slowness and instability of the beta release. Installation was an eye-opener: the 2GB ISO was quicker to download than it was to install - not even counting the several reboots required. When moving files around locally takes longer than downloading them over the net, something's gone seriously wrong.

But was the result and the waiting finally worth it? Hardcore Windows C++ developers will welcome the new release, and Java developers will doubtless be heartbroken to miss out on the 2GB download. But the main focus is .Net, and .Net is an also-ran. Serious systems work will continue to demand Java and C++, leaving .Net bouncing merrily on its Silverlight kiddie-cloud. Seriously, if you want to create a server-side system with demanding performance and scalability requirements, you just don't use .Net.

For everyday use, Microsoft Visual Studio 2010 is pleasant enough. Open up a C# Windows Forms project and you can drag-and-drop components onto a visual form. But the problem I have here - and this isn't just a criticism leveled solely at Microsoft Visual Studio; it's against all the modern IDEs out there - is that this is not so different from what we were doing with the first version of Visual Basic 19 years ago. Somehow, Microsoft managed to fatten Visual Studio up to porcine levels and yet using the product feels like you're trapped in the 1990s.

Java IDEs suffer from the same problem, to an extent. IDE evolution has become a game of feature creep, each new release touting bold new features, drawing in concepts well outside an IDE's core competency - half-baked UML support springs to mind - and packing it all into a single frame. The notion of "doing one thing, and doing it well" has been laughed out the window.

The time is ripe for a brand-new contender to stroll in with something fresh and steal developer mindshare from beneath the leaders' pipe-yellowed moustaches - just as a young Eclipse once did to NetBeans.

The bubblicious Code Bubbles IDE could be just that new contender. It puts a leash around Eclipse to do the donkey work for it, but invents an entirely new front-end so that programming becomes more like playing with Matey in the bath. A prototype from Brown University in New England and video about Code Bubbles has passed the frothy developer test, with viral emails flying around the workplace.

Code Bubbles itself uses an Eclipse plug-in - though you wouldn't think it to look at it. But creator Andrew Bragdon has taken the braver route of keeping Eclipse at arm's length, running Bubbles in a separate process (using C#, ironically) so that Eclipse itself is generally off-screen. Trying to shoehorn the UI into Eclipse would have watered down the whole concept and cluttered the user's workspace with general-purpose distractions.

Whether or not Code Bubbles turns out to be the future kingpin IDE, or whether it's simply the precursor to something more commercial or pragmatic, it does represent the "doing the thinking for us" paradigm. That is, a pattern that development languages and environments have been following for decades, of hiding layer upon layer of implementation detail so developers can focus on what really matters, delivering fit-for-purpose, maintainable software that doesn't bring stock exchanges crashing down.

Code Bubbles, not bloat, for .NET and Java.

View Article



Comments

  • There are no comments yet. Be the first to comment!

Leave a Comment
  • Your email address will not be published. All fields are required.

Top White Papers and Webcasts

  • On-demand Event Event Date: September 10, 2014 Modern mobile applications connect systems-of-engagement (mobile apps) with systems-of-record (traditional IT) to deliver new and innovative business value. But the lifecycle for development of mobile apps is also new and different. Emerging trends in mobile development call for faster delivery of incremental features, coupled with feedback from the users of the app "in the wild." This loop of continuous delivery and continuous feedback is how the best mobile …

  • Packaged application development teams frequently operate with limited testing environments due to time and labor constraints. By virtualizing the entire application stack, packaged application development teams can deliver business results faster, at higher quality, and with lower risk.

Most Popular Programming Stories

More for Developers

Latest Developer Headlines

RSS Feeds