Slashdot Mirror
C Programming Language Back At Number 1
derrida writes "After more than 4 years C is back at position number 1 in the TIOBE index. The scores for C have been pretty constant through the years, varying between the 15% and 20% market share for almost 10 years. So the main reason for C's number 1 position is not C's uprise, but the decline of its competitor Java. Java has a long-term downward trend. It is losing ground to other languages running on the JVM. An example of such a language is JavaFX, which is now approaching the top 20."
but shouldn't it really be at number 0?
Any sufficiently advanced technology is indistinguishable from a rigged demo. -- James Klass
Go ahead, read it for yourself, and tell me how this is supposed to give any meaningful results. They aggregate together things of all kind, to the point where an aggregate doesn't make any sense at all (I mean, hits such as "programming in PHP sucks" or "you must be an idiot to write production code in VB" would count as +1 for PHP and VB, correspondingly!). You can have one language having many job postings, another having many books, and yet another having many basic "how to?" questions and dumbed-down tutorials, and they'd all get the same rating.
In any case, most certainly, at these numbers (Java 18.051%, C 18.058%), speaking of one overtaking another is completely pointless, given the margin of error.
Anyway, if you want to know how popular a particular language/technology is, the simplest - and much more accurate! - way of doing so is to check any popular job search web site. Just keep in mind that preferences vary in different regions, so if you are making career choices, stick to local/national postings, and if you want to see an overall worldwide trend, you have to aggregate data from enough sources.
Your anecdotal evidence it irrefutable.
I expect Java to gain ground again as developers create apps for Android phones.
Although the bare-bones Nexus One hasn't sold in huge numbers, HTC have already produced several superb Android-based alternatives, such as the Legend and the Desire. If/when Android becomes the commonplace operating system in the smartphone market, this will lead to a rise in Java development.
In fact, to join in with the recent Apple-bashing (which I whole-heartedly agree with), I'd suggest that mobile app development will move away from the iPhone, in favour of Android phones. When you are investing time and money in app development, there is simply more certainty in developing apps that will live or die on their merits, as opposed to Apple's 'approval' process.
It is now over 2 weeks since Opera Mini was submitted to Apple for approval:
http://my.opera.com/community/countup/
The index is updated once a month. The ratings are based on the number of skilled engineers world-wide, courses and third party vendors. The popular search engines Google, MSN, Yahoo!, Wikipedia and YouTube are used to calculate the ratings
I feel so much confidence in these numbers.
C and Java are for different things.
C is a great systems language, it lets you get great performance, interact directly with the hardware and still stay fairly portable. Java is a great applications language, it lets you get work done quickly, runs very fast and is extremely portable and secure (which is getting more important everyday as Microsoft's grip on the desktop industry is on a slow but seriously downward trend).
It makes sense that these two would be at the top, popularity wise.
Mod me down, my New Earth Global Warmingist friends!
FTFA:
Philistines! Heathens! There is nothing more beautiful than a good piece of assembly code.
Haha, you're young (and a douchebag).
Yes, I will take the karma for that.
For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
C rising due to global warming. Film at 11.
And nothing more nightmarish than bad assembly.
Have you seen a thorough Spring implementation?
The cesspool just got a check and balance.
Java is extremely portable. A Java application can be run anywhere someone wrote a VM for it in C or C++.
The cake is a pie
As a long time C++ programmer who recently went back to C, I can tell you that C feels like a different language if you use it with all the skills you acquired from other languages. As a language C is almost perfect. It's the libraries that makes all the difference.
And nothing more nightmarish than bad assembly.
(I (disagree (there (is (a (missing) (parenthesis (somewhere)) in)) (your Lisp code)))
C has become the English of computer languages. There are so many derivatives - C++, C#, 'Objective-C', Java, and all those other web scripting languages like Actionscript and PHP -- that I can't even keep track of them all. Their syntax are so similar, yet their libraries are from different planets. As for K&R's C, it is probably like the Queen's English - rarely spoken well and often slurred.
Remember when languages really looked different - COBOL, PL/1, Fortran, Lisp? I date myself.
That was partially my point. Java's security track record for applications is amazing. Look at the current generation game consoles, the only console that has yet to be exploited for piracy in a practical fashion has a Java based security framework.
Java also powers most of the major internet applications available today.
But Java isn't great at everything, C fits in places Java doesn't.
Mod me down, my New Earth Global Warmingist friends!
Yep, as I pointed out, it's an application language not a systems language.
reading comprehension++
Mod me down, my New Earth Global Warmingist friends!
Your point is?
What I think you're being snide about (how Java still depends on C) is misguided. That's the point - nobody's saying your system programming languages are dead. At the end of the day, something needs to be a straight sequence of 0s and 1s that the processor can just run, and that's where C dominates. There's a lot of things (like scheduling algorithms) that really can't be written in a higher level language, either.
But at this point, the only reasons you'd need to use C would be for low-level systems programming, as a base for another language (interpreter/JIT VM), or anywhere where you *really* need to manage your own memory or get close-to-assembly performance. (not) Coincidentally, this covers just about everything C is used for nowadays. Many small utilities are now written in Python, particularly small accessory GUI programs on Linux.
Fact is, a higher level language like Java is just faster to program in, and for a basic application it's more than fast enough. But we'll never lose C, at least because all these higher-level fancy applications need to run on something, and nobody wants to write that "something" in straight assembly.
I have developed a truly marvelous proof of this comment, which this signature is too narrow to contain.
K&R's book on C is wordy. The true classic is the Revised Report on the Algorithmic Language ALGOL-60. In its original typeset form, it is 19 pages.
Languages which need 1000-page books are badly designed.
Robot programming has become very big lately, and the overwhelming number of microcontrollers out there only use C/C++ (well, and Assembly, but that doesn't count).
Well it could have been worse.
If the only reason you have the IoC code in your code is to facilitate testing, then the IoC code is test code.
MVC (in Spring3)? Really? You mean MVC in Spring 1.x or Spring 2.x sucked? Say it isn't so! So now MVC in Spring 3 is the cat's meow? Excuse me while I take a pass.
Spring's transactions are a massive headache when you need to alter or overload a specific operation. Yeah, it seems "cool" when a simple annotation will give you a "transaction", but later on, when you need to modify one bit of code somewhere in the stream or if you're really daring, have a transaction with rollbacks across multiple operations that weren't envisioned in the original design.... let's just agree to disagree and you can deal with all the crap that Spring heaps on you while you cut and paste code and debug it a week later when individual operations change due to changing requirements and I'll be at the bar sipping something cold and enjoying myself after an hour or two's work.
You didn't even mention Spring Security (ie, Acegi) which was so horribly broken 1.5 years ago that it is completely unusable in anything resembling a commercial application. Why, you ask? (I just know that was on the tip of your tongue) Because Acegi as of the current release at that time uses a token held by a thread, and limited the ability of a token to be held to a single thread. In layman's terms - there's only a single lane on the highway, folks.
I still stand by my statement of years ago: Spring is a solution in search of a problem and is a source of not so subtle bugs which most will only realize once they're in far too deep to easily pull out. It truly deserves a picture next to the kool-aid in the wikipedia story about project killers.
I will agree that JUnit4 is pretty darn decent all by itself. Without Spring.
And just in case you think I haven't worked with it - I've dealt with 4 separate large projects and analyzed the problems in various external codebases in 3 different companies that bought into the Spring kool-aid all the way back to before Spring 1.0. I shamefully admit I was even a proponent in the early days, before I actually used it in a big project. Now Spring has joined Apache Commons in the list of libraries to remove asap.
The cesspool just got a check and balance.
> Film at 11.
You're off by 1. The film is actually at 10.
Meh. When I want to show people how bad perl is, I just open up a text editor. Mash my face against the keyboard a couple of times. Then point out that the resulting gibberish is valid perl.
I write ISAPI filters to serve up WebGL enabled sites you insensitive clod!
Suggested title: An Inconvenient Knuth
"I get the point, but a lot of people get the idea to use Java if you want your apps to run anywhere, which is just idiotic, if you want it run really almost anywhere and are ready to make an extra effort, C is a far better choice than Java."
No, it's really not. Java apps are portable because they're write once, run anywhere there's a JVM. C apps are only portable if you write for every single different platform providing a suitable C compiler exists for each of those platforms.
The issue is that you're confusing a portable application, with an application that can be ported, and having to specifically port for each platform is expensive as it requires much more development time, and it creates more headaches in terms of debugging etc. as you face platform specific issues more often.
The extra effort to go cross platform on C isn't trivial, if you've got to write an IO, networking, graphics, threading abstraction layer and so forth, as well as multiple implementations of for those abstractions layers to get your app to run on multiple platforms then it's likely going to be equivalent to re-writing your entire app a few times over. What's worse is you do not get the inherent security benefits of a language like Java either, meaning the end result is a lot more work, much harder debugging of platform specific issues, much higher chance of security flaws and for what? certainly no worthwhile performance gain.
This is why C is best kept as a systems language- creating things like JVMs, drivers, kernels and so forth it's just fine for. But replacing Java for cross platform application development if Java is an option? that's insane.
Part of being a good developer is using the right tool for the job, anyone recommending C when Java is an option for cross platform development cannot possibly be classed as a good developer, advocating C over Java where Java is an option is simply the sign of a developer who is not capable of picking the right tool for the job.
I'm not even advocating Java as the be all and end all of languages, I don't use it at work, I use C# and .NET because we're a Microsoft based company and C# and .NET simply offer much better development tools, albeit at the expense of portability. It really is about using the right tool for the job to get the best balance of cost, features, and quality possible, and languages like Java have simply matured to offer a far superior solution to many of the more classic languages like C and C++, even if those languages do deserve a special place in our hearts in terms of the behemoths they once were- the languages which you could pretty much just do everything in.
Of course, it's not a new situation either, assembly programmers said about C, what C programmers say about Java. Unfortunately, those who say these are those unable to keep up with the times rather than recognise and sensibly weigh up the benefits and disadvantages of each option.
"anyone recommending C when Java is an option for cross platform development cannot possibly be classed as a good developer,"
Very few systems (especially in house ones) require true cross platform development so that's generally irrelevant anyway.
"advocating C over Java where Java is an option is simply the sign of a developer who is not capable of picking the right tool for the job."
Or maybe its a developer who doesn't have a knee jerk reaction that the tool that leads to the quickest prototype is the best. I've developed back-end trading apps in the past that required the fastest possible throughput of data (we're talking down to milliseconds being shaved off here) to beat the competition and for that Java simply was not an option. We went for a mixture of C and C++ using the standard sockets API and the system was blazingly fast.
Not every "app" is some floppy piece of GUI code that sits there doing bugger all 99% of its life - some apps are back end systems that are maxed out all the working day and for that you can't beat C and C++.
"Very few systems (especially in house ones) require true cross platform development so that's generally irrelevant anyway."
That's too blanket a statement to be valid in the general case, it's certainly true for some companies. As I stated however, our company is Microsoft based, however even here we want to expand some of our apps onto mobile devices and we have a combination of them such that Java is the only real sensible option. Of all the companies I've worked in I've yet to work in one that only ever has a single platform throughout the entire company, they've all had the odd Linux server between their Microsoft servers, a combination of mobile devices and so forth. It's certainly not an uncommon situation to want apps to be portable. There's also the issues of larger companies which have different operating subsidiaries who have to share some apps and data, but who also are given autonomy on IT decisions from subsidiary to subsidiary- Java absolutely excels here, it acts as a common language that just works between subsidiaries pretty much whatever their platform choices.
If you're not developing in house applications and are developing to sell Java makes sense too, because there's no point writing say, a piece of helpdesk software in C# .NET, or C/C++ with multiple binaries to sell when you can just write once with Java and inherently have a product that works across Windows, Linux and Mac OS X greatly expanding your potential clientbase.
"Or maybe its a developer who doesn't have a knee jerk reaction that the tool that leads to the quickest prototype is the best."
Whose talking about prototypes? I'm referring to real working apps.
"I've developed back-end trading apps in the past that required the fastest possible throughput of data (we're talking down to milliseconds being shaved off here) to beat the competition and for that Java simply was not an option."
Really? Apparentlyy the NYSE doesn't agree with you:
http://www.nyse.com/tradingsolutions/transacttools/1204674243385.html
"Not every "app" is some floppy piece of GUI code that sits there doing bugger all 99% of its life - some apps are back end systems that are maxed out all the working day and for that you can't beat C and C++."
Simply put, you're wrong. Java performs just as well as C/C++ in many cases, better in some, slightly worse than others. This is largely because the JIT compiler is better suited to optimising per platform, rather than per architecture like classic compilers. Plenty of case studies here for Java use in HPC for example:
http://www.sun.com/customers/index.xml?soln=31a8487e-0f60-11da-99bc-080020a9ed93&page=1&sort=date&asc=false
The fact that you talk about Java being faster simply for prototyping, the fact you are not aware of the fact that Java performs just as well in many cases as C/C++, and the fact that you do not think Java is used for high load back end processing demonstrates one thing- you do not know enough about Java to be able to correctly evaluate whether it is the right tool for the job or not in the face of C/C++ and are a good example of the type of developer I was referring to as not being a great developer for this reason. It may well be that C/C++ was in fact the right tool for your particular solution after all (i.e. if you had some custom hardware to take advantage of), but as you clearly don't know much about Java, you cannot possibly say for sure whether that was the case or not, despite the fact you are attempting assert otherwise.
The likes of eBay runs on Java and much of Google's back end work is done with Java also. There's a good reason it's the most prominent language in business still today and has been for a while. It's because it does offer advantages, it is versatile, and yes, it ca