The next big programming language ... will not be a programming language
The industry seems to be in one of its "Gee, I wonder what's next? What's the next Big Thing?" phases at the moment in the field of software development.
Why this should be happening now is an interesting question in itself. Let's spend a minute on that one before proceeding. It could simply be that the big guns of Cobol/Java/C++/C#/PHP/ASP/Perl/Python and so on have been around long enough for the industry to appear to be on some sort of stable plateau. If there is one thing that this restless industry is always bent on destroying, it is those nasty stable plateaux. The grass is always greener on the other side. Even if it isn't greener, it might be profitable so let's go there... (Apologies, cynicism crept in there for a moment!)
Another reason could be that market forces are driving developers to build certain types of systems that are proving too hard to build with existing tools. Some would argue that the new crop of CPUs emerging with multiple processors per core is forcing a significant re-think [1]. Others would argue that to get the best out of Agile Programming practices [2], you need to re-think your core tools.
Personally, I think it's a little simpler than that. Squint to the point where most of the extraneous detail is blurred and you will see that most new systems development is happening in one of three, largely stable foci: The Java ecosystem, the .NET ecosystem and the LAMP ecosystem. All three are very large, quite stable and readily compared one to the other. At a high enough management level, there is little reason to pick one over either of the other two. They all do the same job (essentially), all have readily available tools and developer communities. How to choose?
That, I think, is what is driving the "next big thing" noodlings. Competitive forces are at work to attempt to differentiate these offerings at a level your average developer can appreciate. Whichever one of these three stable "stacks" incubates the next big thing, will probably win big. It may completely win, striding ahead of the competition. Alternatively, it might just remove one of the other two contenders, resulting in bi-polar rather than tri-polar competitive environment for application development stacks.
Regardless of the reason for the search for the next big thing, it is certainly well under way. What will it be? What is the next big programming language? Will it be some sort of Java++ or maybe Ruby [3] or maybe Python [4]? Maybe Perl [5] will make a triumphant return on the wings of a parrot [6]? Hey, how about Erlang [7] or Fortress [8] or Haskell [9]?...
Sign up for ITworld's Daily newsletter
Follow ITworld on Twitter @IT_world
jfruh
Apple syncing patent can't come soon enough
pasmith
New Twitter features borrow from 3rd party clients
Esther Schindler
Open Source Changes the Software Acquisition Process
mikelgan
How to set up continuous podcast play on the new iTunes
David Strom
Five important Windows 7 mobility features
sjvn
Guard your Wi-Fi for your own sake
Sandra Henry-Stocker
Grepping on Whole Words
Sidekick: The Good News & the Bad News
Either way you look at it Microsoft Data Center management did not follow standards or best practices in this failure. In which case it makes me wonder more about the outsourcing of corporate data much less personal data.
- mburton325
Join the conversation here
Quick, practical advice for IT pros. Made fresh daily.
Want to cash in on your IT savvy? Send your tip to tips@itworld.com. If we post it, we'll send you a $25 Amazon e-gift card.













