Slashdot Mirror


2011's Fastest Growing Language: Objective-C

mikejuk writes "Every January, it is traditional to compare the state of programming language usage as indicated by the TIOBE index. So what's up and what's down this year? The top language is still Java, but it's slowly falling in the percentages. Objective-C experienced the most growth, followed by C# and C. JavaScript climbed back into the top 10, displacing Ruby. Python and PHP experienced the biggest drops. If you like outside runners, then cheer for Lua and R, which have just entered the top 20. However, I have to wonder why Logo is in the top 20 as well. I know programming education is becoming important, but Logo?"

356 comments

  1. Objective-C growth by bonch · · Score: 5, Interesting

    Objective-C's growth in popularity coincides with the Flurry Analytics study that showed most mobile developers targeting iOS, with support for Android dropping by a third over 2011. C# will probably continue to see increasing interest because of WinRT. Lua is unsurprising because of its popular use in games, and they just released 5.2 last December. What I find most interesting is that plain old C is set to overtake Java.

    Of course, if you don't take the Tiobe rankings seriously, than all of this is moot, but I guess it's something to talk about on a Friday.

    1. Re:Objective-C growth by shutdown+-p+now · · Score: 1

      C# will probably continue to see increasing interest because of WinRT.

      Given that WinRT offers a choice of C++, C#/VB and JS, isn't not really a given.

    2. Re:Objective-C growth by Joce640k · · Score: 4, Insightful

      If all that index does is count web pages that mention a language then isn't it more likely to be a measure of how many problems people are having with a language? Languages which "just work" would get fewer hits than those which don't.

      --
      No sig today...
    3. Re:Objective-C growth by Cthefuture · · Score: 1

      Plain Lua is nice and all but LuaJIT is where the fun is. It blows the doors off of any other scripting language (and many compiled languages) in terms of performance. I actually have some LuaJIT financial data processing code that runs faster than anything I have been able to code in C. It also has an incredibly awesome and fast FFI interface so you don't even need to write native code to interface with most native libraries.

      Lua's Achilles Heal is string performance. It does have awesome tools like LPeg and has powerful string handling functions but if you're handling massive amounts of string data then it starts to bog down because of the string interning. It's still very fast and usually faster than other scripting languages like Python (not as fast as Perl though) but it is a long standing problem that pisses me off considering how fast it is otherwise.

      --
      The ratio of people to cake is too big
    4. Re:Objective-C growth by BasilBrush · · Score: 4, Insightful

      It's a good hypothesis, but it's pretty easy to test. The TIOBE Index searches the top search engines for the name of the language, followed by the word programming, as a phrase. e.g. "BASIC programming", "C programming".

      I've just searched Google for "Objective-C programming" and most of the results are related to language related books, web tutorials and other related resources. Not problems.

      The guys at TIOBE perhaps aren't so stupid.

    5. Re:Objective-C growth by AmbushBug · · Score: 5, Insightful

      Objective-C's growth in popularity coincides with the Flurry Analytics study [flurry.com] that showed most mobile developers targeting iOS, with support for Android dropping by a third over 2011.

      The Flurry Analytics study is flawed in that it only counts devs using Flurry. As others have pointed out, most Android devs use the free Google Analytics. This biases the Flurry study towards iOS.

    6. Re:Objective-C growth by Smallpond · · Score: 5, Interesting

      Let's compare it to the number of unanswered questions on stackoverflow.com for various language tags:

      c# 31971
      java 28099
      javascript 26978
      php 26755
      objective-c 11749
      python 9078
      c++ 8024
      ruby 5080

      C, Perl, Basic, Lisp, etc - none

    7. Re:Objective-C growth by Joce640k · · Score: 4, Insightful

      I'm not saying the list isn't accurate ... it's just that I can imagine too many plausible ways of skewing it.

      eg. Book publishers might be looking at that list when they decide what books to publish each year. This creates a feedback loop where their own books push a language up the list.

      --
      No sig today...
    8. Re:Objective-C growth by Massacrifice · · Score: 3, Insightful

      Somehow, I trust your metric much, much more than any other "analystics" website - usually nothing more than a PR firm in disguise.

      --
      -- Home is where you eat your heart out.
    9. Re:Objective-C growth by xTantrum · · Score: 1

      Of course, if you don't take the Tiobe rankings seriously [timbunce.org], than all of this is moot, but I guess it's something to talk about on a Friday.

      It's so funny to see so many taking the Tiobe index as an actual indication of a language's true popularity. I remember a few years back as a noob, when the site hackers.com was still around. I used Tiobe to show just how popular C was... circa 2002 - and I was laughed off the board. One senior member just systematically tore me a new one and why Tiobe was a crock of ish....sigh. sure wish that site was still around. :/

      --
      $action = empty(PHP) ? backToC() : unset(PHP) ; "when the concrete cases are understood, the abstractions are readily
    10. Re:Objective-C growth by plopez · · Score: 1

      I thought .Net was on the way out? Or am I mistaken?

      --
      putting the 'B' in LGBTQ+
    11. Re:Objective-C growth by recharged95 · · Score: 1

      C set to overtake Java?

      Must be Friday... the 13th

    12. Re:Objective-C growth by adamdoyle · · Score: 3, Insightful

      The problem with this is that you're not considering the total number of questions per tag. The tags you said "none" for at the bottom are (1) not actually "none", and (2) not very popular tags.

      Here is a full table with percentages, where you can see that there isn't much of a difference between languages with respect to the percentage of unanswered questions: (in order of ascending percentage)

      Objective-C Unanswered: 11,735 / 68,034 = 17.25% Javascript Unanswered: 26,932 / 165,543 = 16.27% BASIC Unanswered: 10 / 67 = 14.93% PHP Unanswered: 26,697 / 181,413 = 14.72% Java Unanswered: 28,050 / 195,957 = 14.31% Ruby Unanswered: 5,074 / 37,266 = 13.62% C# Unanswered: 31,934 / 255,266 = 12.51% Python Unanswered: 9,065 / 88,496 = 10.24% C++ Unanswered: 8,012 / 104,647 = 7.66% C Unanswered: 3,006 / 48,720 = 6.17% Perl Unanswered: 879 / 15,600 = 5.63% Lisp Unanswered: 28 / 1,629 = 1.72%

      Also, who's to say that Objective-C questions are the same level of difficulty as all of the others. Also not considered is the type of programmer who answers questions on Stack Overflow. Perhaps it's mostly professional C++ and C# developers (which would explain why there are lots of C# and C++ questions with a small percentage of unanswered questions) that mostly answer languages they know but occasionally answer some of the other languages that they may not know as well.

    13. Re:Objective-C growth by CapOblivious2010 · · Score: 1

      WinRT? I prefer WinRG

    14. Re:Objective-C growth by Anonymous Coward · · Score: 1

      Interesting, but keep in mind that StackOverflow was originally aimed at .NET developers so there will always be a slightly larger percentage of .NET developers there.

      Java makes sense, by scale alone it should be in the top 3.

      What I find especially interesting is that while Javascript and PHP still rank relatively low in relation to the leaders, they still get an inordinate amount of questions on StackOverflow. My take on this is that these are both languages that can be easily picked up by new programmers, and heavily utilized by morons who have no business calling themselves software developers.

    15. Re:Objective-C growth by AlanS2002 · · Score: 1

      I actually have some LuaJIT financial data processing code that runs faster than anything I have been able to code in C.

      I call shenanigans.

      --
      Not all conservatives are stupid,
      but it is true that most stupid people are conservative.
      - Hume
    16. Re:Objective-C growth by Anonymous Coward · · Score: 0

      >> I actually have some LuaJIT financial data processing code
      >> that runs faster than anything I have been able to code in C.

      > I call shenanigans.

      You don't think it's possible to write dog-slow C code? :)

    17. Re:Objective-C growth by Smallpond · · Score: 4, Insightful

      I think it reflects the activity in the language and the number of new, untrained programmers starting out on it.

    18. Re:Objective-C growth by Anonymous Coward · · Score: 0

      Not surprising. Everyone knows that C# programmers are dumbest :P

    19. Re:Objective-C growth by Anonymous Coward · · Score: 0

      I'd like to suggest that the following warning be attached to the eula of apps:

      "Like all mobile apps, this is for entertainment purposes only - and like all apps it is a self-imposed fine on stupidity. It is aimed at mindless idiots with a tendency to fall for hype, and those individuals that are foolish enough to pay for each and every one of their favorite web pages."

      i know that devs are making a lot of money out of these zombies and a lot of apple people come to this site nowadays, but hey it's only fair to let the customer know what they're paying for!

    20. Re:Objective-C growth by Stevecrox · · Score: 2

      They said anything faster than they have been able to code. I've met some pretty poor developers over the years who can't cope with C.

    21. Re:Objective-C growth by fatphil · · Score: 1

      I've long considered trying out LUA for some semi-serious home projects - in particular for a website. That would involve a fair amount of string processing, so you've made me nervous. A quick search for ``lua string processing slow'' didn't yield anything particularly informative - can you provide some pointers to where the issue is discussed, so that I can arm myself better before committing.

      --
      Also FatPhil on SoylentNews, id 863
    22. Re:Objective-C growth by gbjbaanb · · Score: 1

      Chances are C# will see a drop next year as Microsoft stops pushing it everywhere and starts concentrating on their "C++ renaissance". WinRT was introduced as a means of getting all the good stuff they've been working on to a C++ audience after all.

      Oh, and the fact that MS is now pushing HTML5+js clients with C++ backends will be interesting (ie if they can pull it off and everyone agrees that Metro apps for Win8 is a good idea).

      I'm still surprised that C is up at the top, but I guess there's a lot of defence and embedded development going on, with Java king of the enterprise.

    23. Re:Objective-C growth by ansible · · Score: 2

      Lua does intern all strings, which has many, many nice benefits.

      However, if you are dealing with hundreds of megabytes of strings that are being mutated a lot, then this interning process may be a performance problem. However, there are usually good solutions to these kinds of problems. Hop on over to the Lua mailing list or Lua SubReddit and ask for advice. Many other languages often need high-perfomance byte string implementations that for some situations.

    24. Re:Objective-C growth by fatphil · · Score: 1

      That does look like a nice active mailing list. I'll scan back through the archives and see if I can see relevant threads. Not seeing any speed-related comments jump out implies I shouldn't fret about it.

      --
      Also FatPhil on SoylentNews, id 863
    25. Re:Objective-C growth by BasilBrush · · Score: 1

      Google Analytics is basically a web tool. It can be used for Android apps, but it's not going to do the job as well as the purpose made Flurry Analytics. It doesn't have the ability to collect nearly as much information as Flurry.

      *If* most Android developers are using Google Analytics, they're stupid. I suspect they're not that stupid, and your assertion is wrong.

    26. Re:Objective-C growth by BasilBrush · · Score: 1

      ... because the opinion of someone on a web forum 10 years ago is obviously definitive.

    27. Re:Objective-C growth by macs4all · · Score: 1

      If all that index does is count web pages that mention a language then isn't it more likely to be a measure of how many problems people are having with a language? Languages which "just work" would get fewer hits than those which don't.

      Citation?

    28. Re:Objective-C growth by adamdoyle · · Score: 1

      If all that index does is count web pages that mention a language then isn't it more likely to be a measure of how many problems people are having with a language? Languages which "just work" would get fewer hits than those which don't.

      Citation?

      The GP brought up a perfectly rational argument. If you find it flawed, then, in a constructive way, tell us how it's flawed. Don't complain about a lack of citation. This is not Wikipedia.

    29. Re:Objective-C growth by adamdoyle · · Score: 1

      Another possible source of skew could be that the subset of programmers who create these materials happen to prefer language X over language Y. The entire set of all programmers (which is much larger than the aforementioned "writers" subset) might all be learning language Y, but since the "writers" prefer writing about X, it's possible that X would be at a higher position on the TIOBE index than the actual fastest growing language Y.

    30. Re:Objective-C growth by Cthefuture · · Score: 1

      I have been programming in C for 25 years so it's not my lack of experience. It's a very simple algorithm anyway, there isn't any more optimization that I can do, it's all in the compiler and LuaJIT just does it better than GCC.

      I can't explain it either because until now I didn't think it was possible. This algorithm almost 100% pure math operations and LuaJIT is apparently really fast under certain circumstances.

      --
      The ratio of people to cake is too big
    31. Re:Objective-C growth by noTimeAtAll · · Score: 1

      Unfortunately, unanswered PHP questions tend to be plain stupid. So that doesn't count.

    32. Re:Objective-C growth by nikanth · · Score: 1

      Java(Android) is still No.1 by a huge margin. And I don't think Android/iOS is the reason for Java's -0.29% decline. It is probably the C# that is causing it.

    33. Re:Objective-C growth by Anonymous Coward · · Score: 0

      It is surprising that IOS is being accepted by so many devs, using the term lightly since I bet most are untrained monkeys like PHP primates.

      Anyway, Apple has made such a developer-hostile deployment environment, it is amazing anyone develops on it. It brings a risk that Apple will reject it outright and it puts up barriers to quick bug/feature patches.

      Objective-C is just dandy, playing in Apple's walled garden, no matter how pretty is filled with traps.

  2. C# by Anonymous Coward · · Score: 5, Interesting

    How is the real story not that C# is 3rd up from 6th!

    1. Re:C# by antitithenai · · Score: 3, Interesting

      I suspect that both C# and Objective-C market share will only continue - probably even taking the top spots. Windows Phone 7 uses mainly C# and so will Metro apps on Windows 8. Frankly, it is a really good language and beautiful to work with. Likewise Objective-C is strong because of iOS and OS X. Java is slowly dropping from enterprise usage and is being replaced by C#.

    2. Re:C# by Anonymous Coward · · Score: 1

      I suspect that both C# and Objective-C market share will only continue - probably even taking the top spots. Windows Phone 7 uses mainly C# and so will Metro apps on Windows 8. Frankly, it is a really good language and beautiful to work with. Likewise Objective-C is strong because of iOS and OS X. Java is slowly dropping from enterprise usage and is being replaced by C#.

      If Metro apps are your argument, then surely JavaScript will be #1 in no time (as it rightfully should be.)

    3. Re:C# by PhrostyMcByte · · Score: 1

      Windows 8 Metro apps will use C++, C#, or HTML5/JavaScript. I suspect HTML5 will get the largest use, though I'm sure C# will be a close second.

    4. Re:C# by Nerdfest · · Score: 4, Insightful

      So the rosy future of software development directed and controlled by Microsoft and Apple? Awesome. I'm sure that will work out well for all involved.

    5. Re:C# by epyT-R · · Score: 1

      yes about as well as the political duopoly has for the US. can't wait!

    6. Re:C# by samkass · · Score: 5, Insightful

      I suspect that both C# and Objective-C market share will only continue - probably even taking the top spots. Windows Phone 7 uses mainly C# and so will Metro apps on Windows 8. Frankly, it is a really good language and beautiful to work with. Likewise Objective-C is strong because of iOS and OS X. Java is slowly dropping from enterprise usage and is being replaced by C#.

      Your argument about C# is spot-on on the client side, but I have yet to see any significant movement from Java to C# on the enterprise side. If anything, enterprises are continuing to build larger and larger installed bases of Java software that's further locking them in. In addition, I see a general distrust of Mono and a liking for Linux that biases them against C#.

      --
      E pluribus unum
    7. Re:C# by idontgno · · Score: 1

      I suspect your observation about the enterprise space is valid (and somewhat agrees with my observations in government/military enterprise deployments). However, the shift in percentages probably isn't based in migrations in existing deployments, enterprise or otherwise. Instead, I suspect that the overall space is becoming dominated by mobile devices, driving up the use numbers of the languages in that arena while other endeavors hold mostly stagnant. Hence, the shift in percentages.

      Just a theory.

      --
      Welcome to the Panopticon. Used to be a prison, now it's your home.
    8. Re:C# by Bryan-10021 · · Score: 5, Interesting

      Java is slowly dropping from enterprise usage and is being replaced by C#.

      Really? Show me where C# is slowly replacing Java in the enterprise? On the server side Java has no competition. If C# is replacing Java then that would mean companies are also replacing UNIX with Windows as it's the only platform that supports C# (forget Mono). That's definitely not happening.

    9. Re:C# by Anonymous Coward · · Score: 0

      How is the real story not that C# is 3rd up from 6th!

      Check out the graph later down the article. While C# is up a bit, PHP only because PHP fell fast. Also, if C++ hadn't lost ground. C# wouldn't have passed it either. Objective-C passed a number of rising languages. It's absolute gain (I hate relative gains) over the last few years is pretty amazing. If that trend continues another year, Objective-C will pass C# too.

    10. Re:C# by JoeMerchant · · Score: 1, Insightful

      Interesting how both Objective C and C# are walled garden languages - sure, they're both "open" but in reality, you use them inside walled gardens.

    11. Re:C# by tlhIngan · · Score: 1

      I suspect that both C# and Objective-C market share will only continue - probably even taking the top spots. Windows Phone 7 uses mainly C# and so will Metro apps on Windows 8. Frankly, it is a really good language and beautiful to work with. Likewise Objective-C is strong because of iOS and OS X. Java is slowly dropping from enterprise usage and is being replaced by C#.

      So Objective-C is rising because of iOS. And C# is rising becaues of Windows Phone 7. And Java is dropping.

      What about Android? You have to code in Java - and Android is the top mobile OS out there, outselling iOS. There should be huge buzz for people writing Android apps - a huge market awaits.

      The drop in Java makes no sense if the rise in C#/Obj-C is due to mobile OSes, because Java is huge in the mobile space, especially since the top-selling mobile OS uses it for app development.

    12. Re:C# by grub · · Score: 1

      IIRC, gcc compiles Objective-C. You don't need Apple's devkit to compile.

      --
      Trolling is a art,
    13. Re:C# by Nethemas+the+Great · · Score: 2

      If you think JavaScript can or should replace strongly typed, compiled languages then you are severely deluding yourself. Just because it's popular with the sweat-shop monkeys doesn't make it a good choice. It just makes it a choice for those that don't know (or incapable of) any better or must fulfill a specific requirement revolving around web based GUIs. At present C, C#, Objective-C, and Java are still your best bets for most purposes not related to web based GUIs. If Microsoft would stop insisting on supporting only their platforms for .NET and the CLR, C# could quite easily catch up to if not stomp Java into the dirt.

      --
      Two of my imaginary friends reproduced once ... with negative results.
    14. Re:C# by Nethemas+the+Great · · Score: 1

      If you're willing to consider widgets and the various mini-apps that have proliferated in the mobile space then that's probably true. However, I think it very unlikely that anyone will move away from C#/XAML (WPF) for everything else.

      --
      Two of my imaginary friends reproduced once ... with negative results.
    15. Re:C# by Nethemas+the+Great · · Score: 1

      Java's WORA, has made it the go-to language for all things not Apple. If you constrain things to the enterprise though you're more likely to find Java and C# close to neck and neck.

      --
      Two of my imaginary friends reproduced once ... with negative results.
    16. Re:C# by MBCook · · Score: 1

      Objective-C was a really tiny language until after the iPhone exploded. You can see on the graph that it was basically a rounding error until mid 2009. The same thing could be happening with Android/Java, but covered up.

      Let's assume that because of Android there are 20k new Java programmers every year. But if server use declines, no one is writing applets and Java in low end mobile phones is dying... Java may lose 35k programmers a year.

      The numbers would show a net decline of 15k Java developers, even though Android is driving a bunch of growth.

      --
      Comment forecast: Bits of genius surrounded by a sea of mediocrity.
    17. Re:C# by cyfer2000 · · Score: 1
      --
      There is a spark in every single flame bait point.
    18. Re:C# by Anonymous Coward · · Score: 0

      It's an excellent demonstration of how out of touch the Slashdot zeitgeist is with the real world.

    19. Re:C# by Noughmad · · Score: 3, Informative

      No, it's the real world that is out of touch with Slashdot.

      --
      PlusFive Slashdot reader for Android. Can post comments.
    20. Re:C# by bertok · · Score: 3, Interesting

      If C# is replacing Java then that would mean companies are also replacing UNIX with Windows as it's the only platform that supports C# (forget Mono). That's definitely not happening.

      That is definitely happening! Maybe not where you are, but I'm a consultant that gets to see a wide range of corporations, and everywhere I go I see NetWare and UNIX getting replaced with Windows. It's cheaper than either of those options, and having a single OS family across all servers is a huge win for support and training costs.

      The days when you had to have a "big iron" UNIX box to be able to handle an enterprise application workload are over. You can get a Windows compatible server with more CPU cores than you can use for peanuts these days. There just aren't that many business problems that need more than ~256 CPU cores and 2 TB of memory. Keep in mind that a CPU core these days is about 10x faster than a CPU core used to be just a decade ago!

      The only area where Microsoft still hasn't won is in reliability, even though they have the technology to do so. Window supports hot patching, but no patch management system that I'm aware of actually applies the patches that way. Windows Server Core needs (supposedly) fewer patches, but still requires a reboot once a month in practice. The have cluster support, but still can't do active-active disks, except for some special cases like Hyper-V virtual disk storage. This is getting less important though as applications these days tend to use load-balanced clusters instead of a single highly reliable server.

    21. Re:C# by Anonymous Coward · · Score: 0

      Yeah, that's meaningful...

      (CAPTCHA is "betters" so... go figure, huh? Even the site knows you're a bunch of elitists)

    22. Re:C# by phantomfive · · Score: 3, Interesting

      And C# is rising becaues of Windows Phone 7.

      Honestly I don't think C# is rising because of WP7. If you want to write software that runs on Windows only, C# is the best way to do it. Especially since in Visual Studio 2010, support for C++ has been waning (you can't use intellisense in C++ CLR environments, for example). My guess is that's why C# is rising, because of plain-old Windows Desktop.

      --
      "First they came for the slanderers and i said nothing."
    23. Re:C# by Rubinstien · · Score: 5, Informative

      Indeed this is so. You can also compile Objective-C using clang/llvm . See: http://clang.llvm.org/compatibility.html#objective-c . The clang implementation is at feature parity with the Mac OS X 10.7 version of the language, and based on my limited understanding of some comments I've read in various announcements, supports some additional features as well. Use of those features requires the GNUStep Objective-C runtime (libobjc2), rather than the GCC runtime. A high degree of Cocoa compatibility is available using the GNUStep Base (Foundation) and GNUStep GUI (AppKit) libraries, for numerous Unix platforms as well as Windows. A version of CoreFoundation is also available which wraps GNUStep Base, with a rewrite coming very soon that implements CoreFoundation in plain C. Various other Cocoa and iOS-compatible libs are available in disparate states of implementation. As always, GNUStep could use more developers and more users. Companies wishing to port their MacOS software to other platforms are encouraged to investigate GNUStep; previous porting efforts have positively contributed to the project by discovering and reporting bugs and sometimes by providing direct improvements.

      GNUStep was recently used to port the Mac-only racing game CoreBreach to Linux: ( http://corebreach.corecode.at/CoreBreach/About.html ). Other visible examples of Cocoa/Objective-C applications ported to Linux from MacOS include the 'eggPlant' automated testing tool from TestPlant ( http://www.testplant.com/ ), and plenty of previously Mac-only Free/Open-Source software such as Bean.app ( http://1.bp.blogspot.com/_2qH5zqXu7wQ/TRi6sNiNZjI/AAAAAAAAADM/i8RwqzQ6OYE/s1600/bean-gnome-theme.png ).

      The parent is correct that you do not need Apple kit to develop in Objective-C. To work with most examples you will find, you will need Cocoa-compatible development libraries and tools, though. Interesting starting points include the Windows Installers, which include all of the components you would need to get started ( http://www.gnustep.org/experience/Windows.html ), or the GNUStep Core packages ( http://www.gnustep.org/resources/downloads.php ) for other platforms. The Étoilé Project http://etoileos.com/ is also interesting. Those of you in Europe who are interested and intend on attending FOSDEM should stop by and visit the talks and devroom sponsored by these projects.

    24. Re:C# by Anonymous Coward · · Score: 1

      Absolutely. That's why sales of linux servers have been falling for a decade.

    25. Re:C# by Anonymous Coward · · Score: 4, Interesting

      "I see NetWare and UNIX getting replaced with Windows. It's cheaper than either of those options"

      O rly?

      It's weird: I'm seeing Solaris and other Unices being replaced with Linux. Rock-stable solid and 100% free Linux distros btw.

      There are even entire *continents* now (cough, Europe, cough) where announcements are made that countries should favor open-source and free software over commercial OSes making $$$ fly to the U.S.

      Despite the fudged TCO studies sponsored by M$ and linked by astroturfing M$ shills here, lots of people deciding the IT budget are starting to realize that they do not have to pay the M$ tax.

      "The only area where Microsoft still hasn't won is in reliability" -- Add price, security and performances. And you may be on to something...

    26. Re:C# by bsane · · Score: 4, Insightful

      If you think JavaScript can or should replace strongly typed, compiled languages then you are severely deluding yourself.

      At present C, C#, Objective-C, and Java are still your best bets

      You realize that one of those four isn't strongly typed, and doesn't resolve method calls until runtime?

    27. Re:C# by Anonymous Coward · · Score: 4, Informative

      My observation has been the very opposite. I have seem very large windows deployments get replaced by Linux at several businesses especially with the movement to virtualization where one can get very lean headless Linux VM's that use minimal resources that allow better h/w scalability at much lower operating costs for running server software.

    28. Re:C# by cthulhu11 · · Score: 1

      Objective-C is strong because of iOS and OS X.

      ... and because most devs have never had to work with Brad Cox.

    29. Re:C# by Pengo · · Score: 1

      Where do you consult? The City of Redmond city service building?

      When I see a post start with: ".. and everywhere I go I see NetWare and UNIX.. " I have to scratch my head and wonder where you're going!

      I don't want to seem like a troll, but wherever you're going is definitely NOT where i'd want to be or would want to work. If a place is so sophisticated that they are just getting around to replacing Netware, Windows Server really might be the right solution for your customer! :) No doubt that there is COBOL consultants following you in tow to these customers.

    30. Re:C# by Xest · · Score: 2

      Where on the server side have you looked? certainly for server side web application development C#/ASP.NET is gaining ground - you only have to look at job listings where there's rarely a Java job in sight, but hundreds of ASP.NET jobs. I think Java is still important, and still my preferred option on some projects, but it's definitely been losing ground quite rapidly on both server and client side for quite some time now.

      I agree people aren't hosting on Linux with mono though. It's all Windows/IIS.

      People just aren't recruiting Java devs anymore, but neither are they recruiting Objective-C devs either to be honest, which highlights why TIOBEs method is completely and utterly flawed and it's results meaningless. If you go pick a bunch of random places in the world and do job searches for developer you get results on the order of C#, PHP, Java/C++/Ruby/Objective-C in a ratio of something like 20:6:2 respectively nowadays, so unless this growth in Objective-C is being led by one or two single places in the world who are hiring hundreds of thousands of Objective-C devs to make the stats work then we can once again do our annual ignore of TIOBE.

      Really, if you want a rough idea of what the fastest growing languages are in your area then job sites are far and away the best option. Looking at multiple job sites in multiple places across the world gives you the best overview of global demand. TIOBE is completely meaningless for this because if for example we have two new languages, one of which has picked up 10,000 users in a day, and has really good docs so they're all sat using it locally quite happy, or they're discussing it on USENET or something like that, then another language comes along backed by a big firm, has no actual users but a massive PR drive giving it thousands of news stories across the globe, then of course, the latter will be deemed more popular, and seeing faster growth, even if no one's actually even using it at all. Obviously that's dumb, but this illustrates how TIOBE goes wrong - from languages that are common amongst teaching having more newbie questions, even if the language is only being used for assignments, to languages that are backed by regular PR, to languages that people say on forums because there's a proud history behind said language - "Oh yeah, I know C++" because they think it makes them look smart. A language with excellent docs, and even an IDE that offers intellisense is going to lead to far fewer questions than one that has no documentation and no IDE also. There's just so many things to go wrong in TIOBE's methodology that TIOBE basically tells us only one thing - how many times a language has been mentioned on the internet, which has absolutely no bearing to how much it is actually used in the real world.

    31. Re:C# by Xest · · Score: 1

      It's more certainly happening, but primarily from the web side of things. Java is still fairly secure on back end banking systems and the like (hence it has a good showing still in job searches in places like London where there is a massive banking sector), but C# is without question displacing it for things like internal bespoke web applications, and many corporate websites and intranets, as well as most client side work.

      If you work or live in a banking heavy area then you certainly wont see it, if you live anywhere else, or work in pretty much any other industry, you just can't miss it. Whilst Java and C# run pretty evenly in job searches in London for example, an identical search on Monster.com in cities like Leeds, Manchester, Birmingham, Sheffield, Edinburgh show .NET to be well ahead, with PHP arguably a close second. I had a search across a bunch of American cities and found a similar story.

      For what it's worth though, I haven't done this exercise in about 6 months, and Java has definitely picked up again by way of Java jobs compared to where it was then, and for about a year or two before, so whilst C# is definitely more popular in terms of recruitment still now, Java is definitely showing a resurgence right now relative to where it's been for the 18 to 24 months or so prior - it'll be interesting to see how it holds up, but watching the jobs market is a far more interesting and worthwhile indicator than TIOBE. It's also interesting that PHP has shown slow but steady growth in terms of jobs recruited for over the last few years too.

    32. Re:C# by julesh · · Score: 1

      Where on the server side have you looked? certainly for server side web application development C#/ASP.NET is gaining ground - you only have to look at job listings where there's rarely a Java job in sight, but hundreds of ASP.NET jobs. I think Java is still important, and still my preferred option on some projects, but it's definitely been losing ground quite rapidly on both server and client side for quite some time now.

      GP didn't say server side, he said enterprise side. Yes, there certainly are a lot of ASP.NET jobs being advertised, but my suspicion is most of these are jobs that a few years ago would have been PHP jobs, not Java ones. How many of those ASP.NET jobs are using heavyweight enterprisey stuff (message queue, service bus, WCF/SOA) versus simple database-backed web sites? Most of those big projects still seem to be in Java, at least to me.

    33. Re:C# by xtracto · · Score: 1

      If Microsoft would stop insisting on supporting only their platforms for .NET and the CLR, C# could quite easily catch up to if not stomp Java into the dirt.

      Indeed, nowadays C# is a better language than Java anyways. I worked in a startup about 10 years ago which used Microsoft technologies and thus we adpoted .NET (C# and VB.NET) when they were being introduced to the market. The version of C# I used was mainly Java, albeit a bit faster.

      Fastforward to today, I have made all my development in Java (mainly because I got into research and Java has a huge amount of free libraries). But lately I have been reading and thinkering with C# and was absolutely amazed. Stuff like LINQ, properties, lambda expressions embedded *within the language* by default make it an absolute joy to work in.

      --
      Ubuntu is an African word meaning 'I can't configure Debian'
    34. Re:C# by Kjella · · Score: 2

      That is definitely happening! Maybe not where you are, but I'm a consultant that gets to see a wide range of corporations, and everywhere I go I see NetWare and UNIX getting replaced with Windows.

      Something tells me that your information is quite a bit out of date, because NetWare started losing marketshare already in the 90s, the last NetWare release came in 2003 and the final service pack in 2008. Even the last stragglers I saw migrated to Outlook several years ago. Yes, along with that usually comes an Exchange server but it's hardly a big impact when companies decide what application servers they should run. At least not those where the servers are far more important than the desktops, like all the companies doing a online $anything or operating the back-end of a store chain or things like that. If all you're doing is providing your desktop users with a file server, an intranet and other auxiliary services while all the important stuff happens on the client and the applications require Windows, then yeah I'd probably go for an all-around Microsoft package.

      --
      Live today, because you never know what tomorrow brings
    35. Re:C# by art123 · · Score: 1

      I seriously doubt that JavaScript/HTML/CSS will ever be more popular then C#/XAML for native Windows 8 Metro apps.

      Look at Metro JavaScript code. Notice all the references to WinJS and ms- ?

      It is not like you can easily turn that Metro app into a cross platform web application. So why bother using a crappy language like JavaScript if you lose the greatest advantage which is cross platform?

      The only reason developers will choose this option is if JavaScript is the only language they know.

    36. Re:C# by art123 · · Score: 1

      Agreed. For me, XAML is a hugely more productive markup language than HTML/CSS.

    37. Re:C# by svick · · Score: 1

      C++/CLR is only a niche language though. Under most circumstances, you will be writing managed code in C# or unmanaged code in C++, not managed code in C++. C++/CLR is there for the rare cases when you need to bridge the gap between managed and unmanaged (and you can't or don't want to use P/Invoke from C#).

      And native C++ does have IntelliSense in VS 2010.

    38. Re:C# by gbjbaanb · · Score: 1

      doesn't really matter what you think. Microsoft has said that HTML5 is the way to go for new apps on Win8. XAML was brought onto C++ as a way of helping "legacy" app development, and that includes C# too now.

      C# is ok language, but it suffers from the old Visual Basic problems - like absolute references. You can't have a directory with your dlls in to reference, as these will all be relative to your project workspace - so everyone has to work on an identical directory tree or things will go wrong. Its great if you're working on a 'lets build an exe', but once you get into the realm of complex systems, it starts to get real messy. And then we get onto 'dependancy hell' which is worse than the 'dll hell' it was supposed to fix.

      I guess adding a 'reference path' to the build environment was too hard for them (but you can do it, it's just on a per-user, per-project basis)
      Microsoft's answer is to use a huge solution to build all components in an app. Seriously.

      We won't go into what happens if you want to include a shared file that's not inside your project's directory either.

      In short, I think C# is a bit like VB was, it feels like VB and they've kept too many of the "lets make it easy" options that actually make it bloody difficult once you start to do real work with it.

    39. Re:C# by LDAPMAN · · Score: 1

      The problem is your using the wrong search term. Few people are advertising for Objective-C developers but MANY are advertising for iOS and OS X developers. To say that a knowledgable iOS dev can't find a job in a nanosecond is to be in denial of reality.

    40. Re:C# by Anonymous Coward · · Score: 0

      If you think Java is being replaced by C# you must be talking about some other enterprise. I'm trying to think of an enterprise that uses only Windows . . ., most use Linux. The enterprise software sellers - Oracle, SAP, IBM, etc use Java. You should rethink your comment.

    41. Re:C# by phantomfive · · Score: 1

      Really though, if you're starting a new project on Windows, that will be Windows only, is there any motivation at all to use C++?

      --
      "First they came for the slanderers and i said nothing."
    42. Re:C# by art123 · · Score: 1

      You are wrong.

      Microsoft has given no indication that JavaScript/HTML is the preferred method for building Windows 8 Metro apps. Look at the MIX 2011 conference videos -- plenty of videos on C++, C#, and JavaScript. If anything, C++ is getting a stronger support than it has in the past few years.

      You apparently don't know the difference between a language, a build tool, and an IDE so I don't think you are qualified to judge the merits of C#.

    43. Re:C# by Xest · · Score: 1

      I'm not searching for any specific developers, I'm just searching for "developer" without any specification and seeing what comes up. iOS, Objective C, however you want to phrase it is relatively uncommon.

    44. Re:C# by Xest · · Score: 1

      What do you mean "enterprise side"? enterprise software is just business software, some might argue that it has certain traits, like the ability to scale, but this means enterprise software encompasses desktop apps, web apps, and so on. There's no such thing as "enterprise side" as some special type of software that's separate from web applications and so forth.

      "How many of those ASP.NET jobs are using heavyweight enterprisey stuff (message queue, service bus, WCF/SOA) versus simple database-backed web sites? Most of those big projects still seem to be in Java, at least to me."

      The answer would be most of them, SOA is massively common amongst the types of ASP.NET sites businesses are building. For what it's worth I've also got a good relationship with a number of recruitment agencies and have on a number of occasions asked them what the market is like for various languages, and all agree that .NET is far and away the largest growth language now, and that there's little money in recruiting Java devs. If you think ASP.NET is only being used for basic dynamic websites which is more often the role of PHP then you're greatly mistaken, and I don't really even see how .NET jobs could be replacing PHP jobs when there are more PHP jobs being advertised out there now than Java jobs even.

      So you may be right, but if you are I've no idea where all these companies using Java are finding their candidates as it's not through job sites, and it's not through recruitment agencies. I doubt very much there's something special about Java whereby Java devs always apply directly to companies, but .NET devs don't at all.

    45. Re:C# by Anonymous Coward · · Score: 0

      C#, is a great RAD environment for Windows. Just like the original VB.
      It was enough like C I was able to pick it up in a day to build a test app for our embedded system.

      Such RAD systems, however, often fail to adapt to tasks that haven't been perfectly scripted by the vendor, making them unsuitable for real programs.

      This is why as a language I prefer Objective-C - when the Evil Fruit Vendor fails you, you've still got the old, known, standard and trusted C. Something C# and Java(or C++ but it doesn't fit in a group of high level languages) can't provide.

      Nevermind the fact I don't actually use Objective-C as I couldn't care less about iShit and GNUstep just sucks.

    46. Re:C# by Anonymous Coward · · Score: 0

      He meant "statically" typed languages. It's error so common among those who don't live with type theory as a girlfriend I'm not sure if it's even an error anymore. But it saddens me nevertheless.

    47. Re:C# by Nethemas+the+Great · · Score: 1

      Apologies, you are quite correct. Typed "strongly" without thinking about it.

      --
      Two of my imaginary friends reproduced once ... with negative results.
    48. Re:C# by Nethemas+the+Great · · Score: 1

      Actually, you're quite mistaken. HTML5/JavaScript is simply the "lowest common denominator" and supported natively within the OS by way of the technology called WinRT. The technology is billed as a replacement for the Win32 API with the goal of making C++, managed (C#, etc.), and JavaScript all first-class citizens.

      A great deal of confusion was had thanks to that speaker at BUILD who either didn't have all the facts or more probably was told to keep a lid on the big picture with respect to Windows 8. Microsoft was never going to abandon the C++ or .NET crowd of whom consists of more or less nearly everyone developing for Windows today. Anyone that took half a second to think about how absurd it would be to tell a C++ or C# developer to use JavaScript would see that. The languages aren't even comparable in terms of expressive power, maintainability or scalability. HTML5/JavaScript are great for small widgets, and mini-apps but its like showing at the job site with a toolbox filled toys when it comes to developing anything of substance. I'd love to see the reaction of a WPF developer when you tell them that from now on they've got to use Scriptaculous.

      --
      Two of my imaginary friends reproduced once ... with negative results.
    49. Re:C# by gbjbaanb · · Score: 1

      I'm sure it'll be like the face of a Silverlight developer....

      I know the old stuff won't go away, but MS is pushing HTML5 hard. That does not mean your apps will be entirely written in javascript (but it's interesting to see who thinks that apps are monolithic all-in-one things). It'll be HTML5+js GUIs (very similar to WPF+C# GUIs, as WPF is just another xml-based markup language with a bit of code-behind the gadgets), with a 'proper' language making up services for it to call, probably exposed as web services, but hopefully something a bit leaner and better.

  3. Poor Scala by Anonymous Coward · · Score: 1

    Has fallen out of even the top 50. Good riddance.

    1. Re:Poor Scala by atrus · · Score: 1

      And what is wrong with Scala? Its miles better than Java. I also don't see Clojure or F# up there.

  4. Objective C by aahpandasrun · · Score: 5, Funny

    Objective C is only popular because iOS requires it. It's like reporting that orange jumpsuits are the hot fashion trend in prison.

    1. Re:Objective C by antitithenai · · Score: 4, Insightful

      Which doesn't change the fact at all, and only shows the importance of iOS.

    2. Re:Objective C by Anonymous Coward · · Score: 4, Insightful

      Actually, that would be the case if the news was "Objective-C is the most popular language for iOS development". If orange jumpsuits would be one of the most used form of clothing everywhere because they are used in prison, well, that would be newsworthy...

    3. Re:Objective C by SpinyNorman · · Score: 5, Insightful

      Of course it changes the facts - it's not Objective-C that's popular - it's the iPhone that's popular. If the language itself was popular then we'd see it being used where it was a choice, not a necessity.

    4. Re:Objective C by Anonymous Coward · · Score: 1, Interesting

      And on that note, it really shouldn't be called "Objective-C" but rather "Apple's bastardized take on Objective-C."

      Ever tried to port code written for Mac OS X to GNUstep? You'll rapidly discover that the Objective-C that GCC uses isn't the Objective-C that Apple pulled from their ass.

      Which stops being funny when you discover that Apple used GCC for their compiler (they've since replaced it with closed proprietary shit), and never bothered to contribute their version of Objective-C back.

    5. Re:Objective C by DanTheStone · · Score: 4, Insightful

      Different definition of popular. This is using it in the "most used" sense, not the "most liked" sense.

    6. Re:Objective C by Toe,+The · · Score: 2

      Sometimes a statistic is used to show trends in other areas.

      For example, yes, iOS is popular with users. However, the fact that the programming language used for it is growing indicates that it is popular with programmers. That's different, and at least a little bit notable. Not only for nerds thinking about what to program in, but also for industry watchers: developer support is very important to a platform.

    7. Re:Objective C by nobodyman · · Score: 4, Insightful

      Actually that's not even remotely true. You always had option of using C and C++ in addition to Objective C, and ever since apple removed the language restriction you can use whatever language you wish so long as it compiles to native code, resides in the app bundle, and doesn't use undocumented API calls. In fact many games are written in C# using monotouch.

      But even if your statement was correct, I'm not sure it's relevant. There are lots of environments that *require* Java development, so do we then apply some sort of negative weighting to it's rank on the TIOBE index? If it's popular it's popular.

    8. Re:Objective C by Anonymous Coward · · Score: 4, Insightful

      And on that note, it really shouldn't be called "Objective-C" but rather "Apple's bastardized take on Objective-C."

      Objective-C is what ever Apple says it is since they for all intents and purposes owns it. They are only only people that make an Objective C compiler so they get to define the language.

    9. Re:Objective C by Goaway · · Score: 4, Informative

      Even GNUstep considers Apple's implementation the official one, and they try to follow it as closely as they can.

      When you run into problems porting, it is because GNUstep is lagging behind.

    10. Re:Objective C by GuldKalle · · Score: 5, Funny

      Were you popular in school?

      --
      What?
    11. Re:Objective C by Anonymous Coward · · Score: 0

      Popularity is about how much people like something, not about how much people are forced to use something. Then again, the focus of the artile is about the most searched programming language on the internet last year, whatever the reason for that is, be it popularity, necesity or some other reason.

    12. Re:Objective C by ColdWetDog · · Score: 4, Funny

      Are you new here?

      --
      Faster! Faster! Faster would be better!
    13. Re:Objective C by antitithenai · · Score: 1

      Popular isn't necessarily how much people like something. For example not that many actually likes the "popular" girl or guy in school, there's just other contributing factors, like themselves getting something out of it. Just like with Objective-C and iOS.

    14. Re:Objective C by SpryGuy · · Score: 2

      In this case, I think it's solely driven by iDevices. If the iPhone and iPad were to suddenly tank in the market, I believe you'd see Objective-C usage tank right along with it. Objective-C isn't the reason they're popular. It's just the only choice developers have to code for a popular platform.

      Meanwhile, something like C# is actually pleasurable, and I think would see increasing usage even if WP7 tanks (heck, it's barely a blip in usage as it is right now). C# in some form or another is available on non-MS platforms too, and is used there. Obviously MS drives C# adoption with the popularity of their Windows platform, but I think there's a subtle difference in that C# is really nice... (you have MANY options when coding for Windows). Objective-C is just the only choice.

      --

      - Spryguy
      There are three kinds of people in this world: those that can count and those that can't
    15. Re:Objective C by SQLz · · Score: 3, Funny

      Is $99 some kind of large amount of money? What is that like a week of brown bagging your lunch?

    16. Re:Objective C by Anonymous Coward · · Score: 0

      Yes, let's not, and point out that clang is BSD licensed.

      Which means that Apple's version will never see the light of day. Don't forget that the Darwin kernel is open source, but the version Apple actually uses most certainly isn't and the majority of Mac OS X is proprietary shit.

      The exact same thing holds true for their "Objective-C" compiler. It may have had its roots in open source, but under Apple it most certainly is not now and never will be again.

      So I stand 100% by calling Apple's compiler proprietary shit.

    17. Re:Objective C by Anonymous Coward · · Score: 0

      you must've been, as popular people never learn to not use fallacies as they've always had the majority backing their play (argumentum ad populum).

    18. Re:Objective C by bonch · · Score: 0, Offtopic

      Who are you to claim that Objective-C is not popular? Have you surveyed every developer in the world to ask them about this? That's a pretty huge presumption on your part when you don't provide evidence either way.

    19. Re:Objective C by shutdown+-p+now · · Score: 3, Insightful

      And on that note, it really shouldn't be called "Objective-C" but rather "Apple's bastardized take on Objective-C."

      Obj-C is a proprietary language, in a sense that it is unilaterally defined by a single entity. Said entity in this case was Stepstone, then NeXT, and now Apple. There's no ANSI or ISO Obj-C, nor any other standard, outside of the language spec that Apple publishes. So it's kinda silly to blame them for not toeing the line. If anything, you should blame GNUstep for not keeping up.

    20. Re:Objective C by shutdown+-p+now · · Score: 1

      Actually that's not even remotely true. You always had option of using C and C++ in addition to Objective C

      You can use vanilla C or C++ for your own code, but all iOS APIs are Obj-C, so you necessarily need to know the language enough to at least work with those.

      But even if your statement was correct, I'm not sure it's relevant. There are lots of environments that *require* Java development, so do we then apply some sort of negative weighting to it's rank on the TIOBE index? If it's popular it's popular.

      I think GP's point was that it being popular doesn't mean that it's good.

      (which is, of course, also true of Java and many other languages in TCPI)

    21. Re:Objective C by anyGould · · Score: 1

      Thou shalt re-write the applications when iOS 5 is released (because we decided that access to Device Unique Identifier needs to go away)

      Considering that the Device Unique Identifier was becoming a popular vector for spyware, I'm perfectly happy that it's going away.

    22. Re:Objective C by Anonymous Coward · · Score: 0

      What a lot of shit you talk. Not only do Apple release source code for their compiler but they have a new one (which is again open source) in the form of Clang/LLVM to replace the ageing GCC. Also, since NeXT/Apple are the only real user of Obj-C surely they have the right to improve/change it as they see fit?

    23. Re:Objective C by Timbo · · Score: 1

      If you substitute 'uses' for 'requires', the GP is quite correct. It's not like there has been a mass adoption of the language because of the merits of the language itself.

    24. Re:Objective C by Sunshinerat · · Score: 1

      Yes, as a punch bag.

      --
      Load New Commander (Y/N)?
    25. Re:Objective C by Anonymous Coward · · Score: 0

      What does the license even matter? You claimed that Apple violated the GPL with with GCC in any case (without proof, I note.)

      The real problem is that the Objective-C implementation in GCC was sorta-kinda related to the spec and allowed all sorts of things it shouldn't have, on top of being slow and not nearly as amenable to tooling as Clang-LLVM. Apple said "enough is enough" and put together a project that looks to the future, not the past.

    26. Re:Objective C by Anonymous Coward · · Score: 4, Informative

      Yes, let's not, and point out that clang is BSD licensed.

      http://llvm.org/svn/llvm-project/cfe/trunk/LICENSE.TXT

      The exact same thing holds true for their "Objective-C" compiler. It may have had its roots in open source, but under Apple it most certainly is not now and never will be again.

      If clang started as open source that apple made proprietor, then why is the very first commit from Apple? http://lists.cs.uiuc.edu/pipermail/cfe-commits/2007-July/000000.html
      And why is the newest feature to come to Objective C being actively worked on Top of Tree by an apple employe. http://lists.cs.uiuc.edu/pipermail/cfe-commits/Week-of-Mon-20120109/051009.html

      So I stand 100% by calling Apple's compiler proprietary shit.

      Nope you stand 100% full of shit.

    27. Re:Objective C by Tablizer · · Score: 1

      Objective C is only popular because iOS requires it. It's like reporting that orange jumpsuits are the hot fashion trend in prison.

      Explains C#.

    28. Re:Objective C by 0100010001010011 · · Score: 3, Informative

      Which means that Apple's version will never see the light of day.

      Um. You mean the version that I downloaded with XCode?

    29. Re:Objective C by LWATCDR · · Score: 4, Informative

      Actually IOS does allow you to develop in C++ if you want.
      http://gamedev.stackexchange.com/questions/11079/objective-c-or-c-for-ios-games
      and here
      http://iphonedevelopertips.com/cpp/c-on-iphone-part-1.html
      for examples.
      To be honest I have worked in C++ and Objective-C and I like Objective-C better. When I work on Windows or Linux I use C++ because that is the better supported language on those platforms. On IOS I use Objective C.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    30. Re:Objective C by LWATCDR · · Score: 1

      Maybe you should learn teh differences between facts and opinion.
      If Windows tanked it would take C# with it. Yes I know about Mono but it is just a blip.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    31. Re:Objective C by VGPowerlord · · Score: 2

      Actually, that would be the case if the news was "Objective-C is the most popular language for iOS development". If orange jumpsuits would be one of the most used form of clothing everywhere because they are used in prison, well, that would be newsworthy...

      A more apt analogy would be that orange jumpsuits are the clothing item with the biggest increase in sales (to the government obviously) in America because we're sending more people to prison.

      --
      GLaDOS for President 2016! "Well here we are again. It's always such a pleasure." -- GLaDOS, 2011
    32. Re:Objective C by Anonymous Coward · · Score: 0

      I'd add that this becomes particularly relevant if you consider the restrictions Apple places on what developers can use and what they can't.

      Maybe that's what you meant, but it's important to keep in mind that if you want to develop for Apple, they won't let you use whatever language you choose, even if it were technically possible. The orange jumpsuit in prison analogy is pretty apt in this regard.

    33. Re:Objective C by SpinyNorman · · Score: 1

      I'm not so sure...

      All I can see on the TIOBE site is:

      The TIOBE Programming Community index is an indicator of the popularity of programming languages.

      followed by:

      The index can be used to check whether your programming skills are still up to date or to make a strategic decision about what programming language should be adopted when starting to build a new software system

      It seems that the "popularity" they are trying to measure is one that infers some merit (i.e. popular by considered choice) to the more popular languages, otherwise using this measure to choose a language for a new project doesn't make much sense. Similarly a language isn't going to be widely useful as a career skill if it's only being used on a niche platform, so it would seem that they are expecting their popularity to be measuring breadth of use (presumably due to merit), not depth of use on a single platform (which speaks for itself).

    34. Re:Objective C by VGPowerlord · · Score: 5, Insightful

      And on that note, it really shouldn't be called "Objective-C" but rather "Apple's bastardized take on Objective-C."

      Obj-C is a proprietary language, in a sense that it is unilaterally defined by a single entity. Said entity in this case was Stepstone, then NeXT, and now Apple. There's no ANSI or ISO Obj-C, nor any other standard, outside of the language spec that Apple publishes. So it's kinda silly to blame them for not toeing the line. If anything, you should blame GNUstep for not keeping up.

      Incidentally, this also applies to just about every language on the list other than C.

      Just to name a few: Java (Oracle), C# (Microsoft), JavaScript (Mozilla nee Netscape), PHP (The PHP Group), Ruby (Yukihiro Matsumoto), Python (Guido van Rossum)...

      --
      GLaDOS for President 2016! "Well here we are again. It's always such a pleasure." -- GLaDOS, 2011
    35. Re:Objective C by Anonymous Coward · · Score: 0

      I was Mac developer before the switch to OSX. I took the Java route over Objective-C and a few years back started learning Objective-C because I wanted to learn iOS. At first it was painful, but within weeks I was pretty productive and now working on an app that would expose part of our Java app to be accessible as an iPhone app. I am actually starting to like Objective-C quite a bit. Once you get over the odd syntax, the framework is very powerful.

    36. Re:Objective C by kvvbassboy · · Score: 1

      I think his point is that the popularity of Objective-C relies heavily on the success of iOS platform. What would really make a language popular, if people "forked" it from its initially intended usage, and ported it to other platforms or application domains. Objective C is too single-dimensional to make everyone consider learning/using it, unlike some other languages.

    37. Re:Objective C by gtbritishskull · · Score: 1

      On what platforms do people code in Objective C besides an ipod/pad/mac/ect?

    38. Re:Objective C by JoeMerchant · · Score: 1

      Different definition of popular. This is using it in the "most used" sense, not the "most liked" sense.

      I'd say "most used" not "most useful," which sounds good but is a little off-target on the meaning. For a meaning targeted pair, I'd go with "most used" not "most efficient," or even better "most used" not "most universally applicable."

      Liked is a subjective opinion, Objective-C and C# are objectively less portable than C++.

    39. Re:Objective C by JonySuede · · Score: 1

      C# is Java done right without the legacy crap, it is a nice language to develop in but it's Windows-centricity is a big turn off...

      --
      Jehovah be praised, Oracle was not selected
    40. Re:Objective C by shutdown+-p+now · · Score: 1

      JavaScript on that list should arguably be EcmaScript, and that one is taken care of by ECMA these days.

      C# is neither here nor there - it has an ISO standard, but in practice it's still designed by MS, and the spec is updated to match the most recent VC# release with a few minor exceptions, and even then not quite regularly (last I heard they are still working on an updated ECMA spec for C# 4, which would then take more time to get ISO stamp of approval). So it's proprietary in practice, but you still can take the spec and compare it vs what the compiler actually does (and there are some things that VC# does wrong, like being able to cast int[] to uint[] when the spec says you should get InvalidCastException).

    41. Re:Objective C by nobodyman · · Score: 1

      Well hell, so long as we're substituting words, I choose to replace the word "correct" with "high" in your previous statement ;-)

    42. Re:Objective C by Anonymous Coward · · Score: 0

      At least you learned a trade.

    43. Re:Objective C by sourcerror · · Score: 4, Funny

      Then your were popular in the "most used" sense.

    44. Re:Objective C by Xtravar · · Score: 3, Interesting

      I have seriously considered using Objective-C for non-iProjects, because it is so pleasant to use. I used to be a huge C# fan, using it in Linux and Windows for everything. I can guarantee that non-Apple APIs and tools will arise because of its usage.

      --
      Buckle your ROFL belt, we're in for some LOLs.
    45. Re:Objective C by Timbo · · Score: 1

      I'm curious how you explain the meteoric rise of Objective-C then, if it's not down to the proliferation of iOS?

    46. Re:Objective C by Anonymous Coward · · Score: 0

      It's like reporting that orange jumpsuits are the hot fashion trend in prison

      It's more like reporting that orange dye is selling well. Whatever the reasons, it's happening and relevant to the dyers.

      20 years ago you couldn't find many Objective C programmers, and they were all nerds and probably wanted lots of money. Now they're everywhere and will work for $50 a month.

    47. Re:Objective C by SpryGuy · · Score: 1

      You and I are on different ends then... I honestly can't stand Objective-C. I can't even really tell you why. It just grates everytime I see it.

      --

      - Spryguy
      There are three kinds of people in this world: those that can count and those that can't
    48. Re:Objective C by BasilBrush · · Score: 1

      iPhone and iPad and MacBooks.

      iPhone on it's own is less popular than Android phones. But iOS has more developers than Android.

    49. Re:Objective C by BasilBrush · · Score: 2

      Which is fine as a hypothetical. But in practice developers who use Objective-C do tend to like it. It's the Android shills who don't know it that whine about it.

    50. Re:Objective C by Grishnakh · · Score: 1

      It's like reporting that orange jumpsuits are the hot fashion trend in prison.

      Depends on the prison. Here in Maricopa County, Arizona, pink underwear is all the rage!

      However, "humans rights" groups have been complaining about it bitterly, as apparently it's far worse to require inmates to wear pink undies and other garments than to waterboard them.

    51. Re:Objective C by Grishnakh · · Score: 1

      C# might be "available" on non-MS platforms, but while Erlang, Scheme, and Ada are also available on various platforms, their usage is pretty much insignificant, just like C# on non-MS platforms. Mono is out there, but it's always a few steps behind, and it's very unpopular in FOSS circles because of the association with MS.

    52. Re:Objective C by beelsebob · · Score: 1, Troll

      Which stops being funny when you discover that Apple used GCC for their compiler (they've since replaced it with closed proprietary shit), and never bothered to contribute their version of Objective-C back.

      Uhh actually, they did – the gcc dev team decided they didn't want the patches. Because of that, combined with gcc's license, it's slowness, it's mass of spaghetti code and various other reasons, apple dumped gcc. They then went out and wrote clang, and then open sourced in under a more permissive license than gcc is licensed. Oh, along with their entire Objective-C runtime implementation. The only reason you struggled with GNUstep is because you tried to use a crappy compiler who's dev team actively fought against being made better by apple. Use clang and libobjc2 and you're golden.

    53. Re:Objective C by scialex · · Score: 2

      It is when you realize that for every other platform with even a microscopic amount of market-share the price is $0. ;)

    54. Re:Objective C by beelsebob · · Score: 4, Informative

      Which means that Apple's version will never see the light of day.

      clang.llvm.org

      Clang was an internal apple project, open sourced by them here's the email in which Chris Lattener (an apple employee) open sourced the code that he had written on apple's time. The code has continued to be released by apple under the BSD license.

      For reference, here's Apple's Objective-C runtime too.

    55. Re:Objective C by Anonymous Coward · · Score: 1

      Did you get source code with that? Stop being intentionally dense.

      Apple's Objective-C both isn't real Objective-C by any useful meaning of the word, and isn't open by any meaningful use of the word.

    56. Re:Objective C by wzzzzrd · · Score: 1

      as source?

      --
      On second thought, let's not go to Camelot. It is a silly place.
    57. Re:Objective C by pwinkeler · · Score: 1

      Hmm - Except that the developers, unlike the prisoners, chose to develop for iOS. If Objective-C was so inferior to Java and the various Android releases that force you to use it, this thriving ecosystem would not exist.

      --
      PaulW, IT Consultant
    58. Re:Objective C by Nethemas+the+Great · · Score: 1

      C#'s largest hindrance on non-MS platforms isn't the language per-se but the lack of the .NET library in any meaningful implementation. If .NET 4 complete with a full implementation of WPF and WCF were implemented for LINUX/Android it'd dethrone Java and stomp it into the dirt in a heart beat. Unfortunately Microsoft is too stuck on the idea that their platform is the only platform that should exist and greatly to their detriment especially when it comes to the mobile segment.

      --
      Two of my imaginary friends reproduced once ... with negative results.
    59. Re:Objective C by theshowmecanuck · · Score: 1

      The definition of 'popular' in the dictionary doesn't mention anything about 'most used'. It is pretty much all about 'most liked'. And if you noticed right from the start, the TIOBE site and I Programmer don't use the word 'popular' in context with 'the index'. They use the term 'market share'. So even though it would be redundant (since it is mentioned in the first paragraph on the TIOBE index page) maybe this branch of the thread should have started:

      'Objective C only has an increasing market share because iOS requires it. It's like reporting...'

      Then the child posts are moot. Unless you want to be redundant and say that Objective-C isn't necessarily popular, it is only increasing in market share because iOS based devices are popular. If you want to find out what's popular you have to survey the developers and ask them why they are using a language, not just what language they are using. There are lot of times something or someone that is popular isn't used because it isn't suitable for the job. And that is probably why the term 'market share' is used in TFA's, and not 'popularity'.

      --
      -- I ignore anonymous replies to my comments and postings.
    60. Re:Objective C by Anonymous Coward · · Score: 0

      if you're brown bagging a 4 course steak dinner, then yeah. Personally for me, 99 bucks is about a month worth of groceries, mr. money bags.

    61. Re:Objective C by Thing+1 · · Score: 1

      Well, for one, they won't generally want to steal the garments. But I think the real underlying reason? The guard put in charge of the laundry facilities had earlier failed home ec.

      --
      I feel fantastic, and I'm still alive.
    62. Re:Objective C by BasilBrush · · Score: 1, Flamebait

      ...Meanwhile, something like C# is actually pleasurable

      The implication being that Objective-C isn't. Which is nothing more than your personal, and possibly ill-informed, preference.

      As to portability C# is about the same as Objective-C. Both primarily for a single platform, but available on other platforms too, although few use it on those other platforms.

    63. Re:Objective C by BasilBrush · · Score: 1

      GNU supports Objective-C, so what platforms DOESN'T it run on?

      Objective C is too single-dimensional to make everyone consider learning/using it, unlike some other languages.

      In what sense are you using the term "single-dimensional" there?

    64. Re:Objective C by BasilBrush · · Score: 1

      Its almost like that. The fashion for wearing jeans with the waistband hanging below the ass started with convicts in US prison, and became common with youths on the streets all over the world.

    65. Re:Objective C by Anonymous Coward · · Score: 0

      Yes as source... (look at clang, lldb, etc.) and this stuff also exists at llvm.org.

      http://opensource.apple.com/release/developer-tools-42/

      Apple does sometimes keep aspects in house until they are ready to release a product dependent on some new capability they developed. Once released however their work is integrated upstream in timely fashion. Most of the time llvm, clang, and lldb work takes place out in public under the LLVM site.

    66. Re:Objective C by BasilBrush · · Score: 1

      Which stops being funny when you discover that Apple used GCC for their compiler (they've since replaced it with closed proprietary shit), and never bothered to contribute their version of Objective-C back.

      Which of course isn't true. The full source of GCC, including Obj-C, as used by Apple, and the full source of LLVM (the replacement), along with all the other open source stuff Apple do is here:
      http://opensource.apple.com/source/gcc_42/gcc_42-5531/

      You think LLVM is proprietary and shit? You haven't the first clue about what you're talking about. It's open source, and it smokes GCC.

      (This is why my filter is usually turned up above the AC level.)

    67. Re:Objective C by Anonymous Coward · · Score: 0

      Comparing the price of food with the current foreign exchange rates, it appears that $99 is enough for take-out each day for five weeks and two days. That's a huge amount of money.

    68. Re:Objective C by BasilBrush · · Score: 1

      And on that note, it really shouldn't be called "Objective-C" but rather "Apple's bastardized take on Objective-C."

      The standard is set by Apple, much in the same way the c# standard is set by Microsoft. The difference is that the Obj-C compiler than Apple uses is open source. The MS c# one isn't.

    69. Re:Objective C by BasilBrush · · Score: 1

      You can use vanilla C or C++ for your own code, but all iOS APIs are Obj-C

      No they're not. Lots of iOS APIs are C.

      For sure you do need some Obj-C boilerplate in an app. But that's not the same thing as the entire API being Obj-C.

    70. Re:Objective C by TheCouchPotatoFamine · · Score: 2

      i have no problem with messages - but every time I see objective-c, i do think to myself, "gee most of the power of python (dynamic runtimes rules the UI!), with all the syntax of C:" - and i kinda wish it was the other way around.

      fwiw.

      --
      CS majors know the time/space tradeoff, but they never get taught the 3rd, crucial, tradeoff of the set: comprehension!
    71. Re:Objective C by BasilBrush · · Score: 1

      Obj-C is C++ done right.

    72. Re:Objective C by shutdown+-p+now · · Score: 1

      How much is "some"? My understanding is that, unless you are writing a fullscreen OpenGL app, all UI APIs are Obj-C only.

    73. Re:Objective C by MightyMartian · · Score: 1

      The thriving ecosystem exists because of iDevices. If Apple had decided to use Fortran-88, then Objective C would remain some minor language, and everyone would be going on about how Fortran-88 is better than C++, Java or C#.

      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
    74. Re:Objective C by Anonymous Coward · · Score: 0

      Did you get source code with that?

      Here is the exact source from Xcode.
      http://www.opensource.apple.com/source/clang/clang-211.10.1/

      Here is the exact source from main clang development.
      http://llvm.org/svn/llvm-project/cfe/trunk/

      Here is what happens when you type clang -v
      Apple clang version 3.0 (tags/Apple/clang-211.12) (based on LLVM 3.0svn)
      Target: x86_64-apple-darwin11.2.0
      Thread model: posix

      Here is apple adding Automatic Reference Counting (ARC) to Objective C
      http://lists.cs.uiuc.edu/pipermail/cfe-dev/2011-June/015588.html
      Here is apple showing the specification document for runtime support so other people can have it too.
      http://lists.cs.uiuc.edu/pipermail/cfe-commits/Week-of-Mon-20110613/042840.html
      Here is GNU Step maintainer adding Support for ARC
      http://lists.cs.uiuc.edu/pipermail/cfe-commits/Week-of-Mon-20110627/043360.html

      Apple's Objective-C both isn't real Objective-C by any useful meaning of the word

      Yes it is because Apple defines what the word Objective-C and by extension Objective-C++ mean. If you want to add to Objective C they take patches.

      and isn't open by any meaningful use of the word.

      Definition of Open
      svn co http://llvm.org/svn/llvm-project/llvm/trunk llvm
      cd llvm/tools
      svn co http://llvm.org/svn/llvm-project/cfe/trunk clang
      cd ../..
      mkdir build
      cd build ../llvm/configure
      make

    75. Re:Objective C by fyngyrz · · Score: 5, Interesting

      I'm in the midst of a pretty large image processing project for OS X, and the UI "wrapper", which is minimal, is in ObjC, but everything else is in C, implemented as a library. So we barely code in ObjC at all.

      Seems to me that terms like "must" are being thrown around here without any real knowledge of the options available.

      --
      I've fallen off your lawn, and I can't get up.
    76. Re:Objective C by Anonymous Coward · · Score: 0

      But... but... but... spyware is a kind of malware, and everyone knows iOS can't possibly have malware!

      ALL GLORY TO THE HYPNOSTEVE

    77. Re:Objective C by Xtravar · · Score: 1

      C# is very appealing at first because of its syntactic sugar. Obj-C is appealing because of the way it works underneath. Don't be a shallow programmer - save your aesthetic judgements for cars and women.

      --
      Buckle your ROFL belt, we're in for some LOLs.
    78. Re:Objective C by Anonymous Coward · · Score: 0

      Core Graphics is a C API.

    79. Re:Objective C by Xtravar · · Score: 1

      Not to mention, the self-documenting nature of Objective-C is fantastic. If you name your methods like Apple does, you'll never need to write comments. ;)

      --
      Buckle your ROFL belt, we're in for some LOLs.
    80. Re:Objective C by BasilBrush · · Score: 2

      Yes, UI is Cocoa (touch), and Cocoa is all Obj-C. As is Foundation.

      The other exceptions for non-Obj-C UIs besides OpenGL is Carbon, which is C.

      But outside of Cocoa and Foundation much most APIs are C. Core Foundation, Core Graphics, Core Animation, Core Audio. Grand Central Dispatch, all the Posix stuff, etc.

      Yes, in practice every app other than OpenGL apps will need the UI doing with Obj-C APIs. I was just picking up on incorrect statement "all iOS APIs are Obj-C" really.

    81. Re:Objective C by Anonymous Coward · · Score: 0

      Yes, let's not, and point out that clang is BSD licensed.

      You know, it's people like you and Richard Stallman that give GNU and the GPL a bad name.

    82. Re:Objective C by Anonymous Coward · · Score: 0

      Then you realize Xcode is free and Visual Studio is $500 and updated every 2 years or so. Suddenly $99 year isn't that much for an amazing development ide.

    83. Re:Objective C by LordLucless · · Score: 1

      If orange jumpsuits would be one of the most used form of clothing everywhere because they are used in prison, well, that would be newsworthy...

      If you're reporting on orange jumpsuits becoming the most popular form of clothing, and the reason is that 50% of the population is in prison, you're reporting on the wrong thing.

      --
      Just because you're paranoid doesn't mean there isn't an invisible demon about to eat your face
    84. Re:Objective C by Anonymous Coward · · Score: 0

      I'll tell you why I hate it... compile time errors should be caught at compile time. Any language that choose to let compile time errors through (because it might work at run time) is fundamentally broken and not suitable for non-toy projects.

    85. Re:Objective C by nobodyman · · Score: 1

      Oh to be sure Objective-C wouldn't be on the radar were it not for iOS. I'm sure that 95% of objective-c developers are working on iOS (the other 5% probably being MacOS). My only point is that there's a big difference between "uses" and "requires".

    86. Re:Objective C by smash · · Score: 1

      Well, obj-c will get you on iOS, Mac and unix.

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    87. Re:Objective C by smash · · Score: 1

      Its also available for Linux (GNUStep) and other unix...

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    88. Re:Objective C by smash · · Score: 1

      I think you are confusing CLANG with core foundation.

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    89. Re:Objective C by Anonymous Coward · · Score: 0

      Hrm. That's an interesting quandary. Since Objective-C is a true superset of C, you could theoretically claim all of your code is in Objective-C... despite most of it being plain C.

    90. Re:Objective C by fyngyrz · · Score: 1

      It's just compiled as c, though -- the library works perfectly under linux, for instance, and isn't developed under xcode or using the ObjC capabilities of gcc. So I think not. The only bridge here is that ObjC knows how to talk to a standard library.

      --
      I've fallen off your lawn, and I can't get up.
    91. Re:Objective C by fatphil · · Score: 1

      I don't know anything about Obj-C, but I do know that C++ is C++ done wrong. I just hope that the people who ruined C++ don't move into other languages and ruin them too. I'm particularly worried about Digital Mars D, which used to be a great language (it was also a C++ done right), but now A.A. has started contributing to it, it could just turn into another bombsite.

      --
      Also FatPhil on SoylentNews, id 863
    92. Re:Objective C by gbjbaanb · · Score: 1

      I think C# is appealing because of Intellisense. Most junior programmers can code by typing and accepting what the IDE thinks they should type next.

    93. Re:Objective C by nobodyman · · Score: 1

      Beyond that I think they also own it it the literal sense. Wikipedia says they purchased it from the original inventor...

    94. Re:Objective C by Anonymous Coward · · Score: 0

      The Apple compiler is LLVM. Any language can be used with it as long as an interface to LLVM is written. I read that RealBasic is writing just such an interface for it.

    95. Re:Objective C by foniksonik · · Score: 1

      $99 isn't the price to code, it's the price to get your code signed by Apple and gives you access to a huge market of buyers. You can and always have been able to code in Obj-C for free. XCode can still be downloaded standalone (if you want Apples compiler).

      --
      A fool throws a stone into a well and a thousand sages can not remove it.
    96. Re:Objective C by Anonymous Coward · · Score: 0

      I started off with my project almost entirely in Objective-C and have been noticing the benefits of using Obj-C for organizing much of the code, but moving much of the functionality into separate C functions. There's less overhead, all side effects are apparent in the function call (so long as you're not stupid), the unit test needs are more obvious, and if called inside of a Obj-C file C functions can deal with most Obj-C calls just fine (NSAssert is the main exception of the top of my head). Of the various OOL, Objective-C is one of the better ones and one of the perhaps surprising reasons is that it's very graceful in its interactions with C.

    97. Re:Objective C by jeremyp · · Score: 1

      That's funny, I've used Objective-C quite a lot and my perception is that compile time errors are caught at compile time. Not only that, the Clang static analyser will catch lots of run time errors at compile time too.

      --
      All I want is a secure system where it's easy to do anything I want. Is that too much to ask ~~ Randall Munroe
    98. Re:Objective C by BasilBrush · · Score: 1

      Named parameters is more Python than C. And when you look at Obj-C code the named parameters (along with the square brackets surrounding them) are the most apparent features.

    99. Re:Objective C by BasilBrush · · Score: 1

      If you like Objective-C why would you chose anything other than Apple's platforms to code for?

    100. Re:Objective C by Anonymous Coward · · Score: 0

      Actually. Yeah. It is. A week of food when you live paycheck to paycheck is pretty damn significant.

    101. Re:Objective C by BasilBrush · · Score: 1

      And on that note, it really shouldn't be called "Objective-C" but rather "Apple's bastardized take on Objective-C."

      Ever tried to port code written for Mac OS X to GNUstep? You'll rapidly discover that the Objective-C that GCC uses isn't the Objective-C that Apple pulled from their ass.

      That's kind of like blaming Microsoft because WINE only runs some WIndows apps.

    102. Re:Objective C by Anonymous Coward · · Score: 0

      The Apple compiler is LLVM. Any language can be used with it as long as an interface to LLVM is written.

      LLVM isn't a compiler, it's an intermediate representation and libraries for building compilers.

    103. Re:Objective C by Anonymous Coward · · Score: 0

      DavidSell, ByOhTek, antitithenai, Bonch, Dtech and others are psuedonyms/sockpuppets used by the Waggener Edstrom rapid response team employed by MS to astroturf discussions in favour of MS and to attack any point of view which isn't favourable to MS and supportive of their interests.

      http://waggeneredstrom.com/about/approach

      Mod accordingly

    104. Re:Objective C by wzzzzrd · · Score: 1

      Just so you know, it's source code, yes, but most of it does not even compile. I'm not explaining it, others have done that already. Just google Apple Open Source Analysis and the like. If your search query ends with "and the like. If your search query ends with", go shoot yourself in the foot.

      --
      On second thought, let's not go to Camelot. It is a silly place.
  5. Slashdot conversation hijacking by Anonymous Coward · · Score: 1, Insightful

    Have you ever noticed that people can sorta hijack Slashdot threads by simply posting a reply to the first post? This makes them the irrevocable second post in the thread.

    To show your appreciation of this "feature," please reply to this post with something completely different.

    1. Re:Slashdot conversation hijacking by CSMoran · · Score: 0

      To show your appreciation of this "feature," please reply to this post with something completely different.

      There. http://www.youtube.com/watch?v=PqosS6DBwhA

      --
      Every end has half a stick.
    2. Re:Slashdot conversation hijacking by Anonymous Coward · · Score: 0

      Yeah, its usually anti-ms trolls blabbering about Linux in every post that contains the word Windows or Microsoft. What is your point?

    3. Re:Slashdot conversation hijacking by badkarmadayaccount · · Score: 1

      I hate ritzy places. I recently came to this conclusion. The setting is nice, but the people are intolerable. I lost vision and movement 2 a.m. in a rock bar, leaning on the column I was lucky to get to, sitting on the floor, trying to recuperate (the weed was stronger than I though), and within the minute security came to direct me to the exit, I barely knew where I was, for a few seconds. No "are you okay?", no "need an ambulance?" (I didn't, but that is beside the point.), just "get out, and don't come back". Am I the only one who thinks this is wrong?

      --
      I know tobacco is bad for you, so I smoke weed with crack.
  6. BBBBBBOOOOGGGGGUUUUUSSSSSS +1, Credible by Anonymous Coward · · Score: 0

    Two words: Big Brother (tm)

  7. Moderators? by betterunixthanunix · · Score: 1, Offtopic

    Why was this modded funny? This is the truth -- obj-C is popular because of iOS, not because it is some kind of programming language panacea.

    --
    Palm trees and 8
    1. Re:Moderators? by Anonymous Coward · · Score: 2, Insightful

      It's funny because the analogy is funny. Was it really that hard to figure that out?

    2. Re:Moderators? by Anonymous Coward · · Score: 0

      It's like reporting that orange jumpsuits are the hot fashion trend in prison.

      Probably because of this part.

    3. Re:Moderators? by Anonymous Coward · · Score: 1

      I wrote years of C, C++ and C# before learning Obj-c and now I'm starting projects in Obj-c (not related to iOS) simply because I like it more than the others. Nothing of importance (pet projects), but years ago I would have used Python or Ruby for those. It feels somehow more fun to program in (yeah, crazy talk).

    4. Re:Moderators? by iluvcapra · · Score: 2

      No language is popular because of the features. Languages are attributes of platforms, people write for platforms. Even platforms that support multiple languages, like iOS and the WinRT, have a "favorite" language where the documentation is most focused, and people will write for whichever language is the most documented.

      --
      Don't blame me, I voted for Baltar.
    5. Re:Moderators? by Anonymous Coward · · Score: 0

      I think you're definitely in the minority there. I've used all those languages too, and I've actually avoided coding for iOS/OSX simply because I can't stand Objective-C.

    6. Re:Moderators? by Anonymous Coward · · Score: 0

      I can't even get that far along - I started reading the Apple documentation on Objective-C, and they have trouble putting together more than three words without trying to SELL the language to me.

      If it's so great, why does it need a marketing team?

      Couldn't they just document it, and let it's own points sell itself?

      Come to think of it, most OOP documentation is like that - the hard sell. Usually not as bad as the Objective-C documentation, but pretty bad.

    7. Re:Moderators? by Nethemas+the+Great · · Score: 1

      True. Which is why Java is at the top instead of say C#. Java is WORA. C# is write-once run Microsoft. It does however say something about Objective-C though since iOS and Linux have similar support and very few want to touch it on Linux.

      --
      Two of my imaginary friends reproduced once ... with negative results.
    8. Re:Moderators? by BasilBrush · · Score: 1

      If you like programming in Objective-C, then you're going to tend to pick an Apple platform to program on and for, rather than Linux.

    9. Re:Moderators? by Nethemas+the+Great · · Score: 1

      That's sounds plausible but you need to consider that Linux is first and foremost a server platform and iOS/Apple is not.

      --
      Two of my imaginary friends reproduced once ... with negative results.
  8. Incorrect by Anonymous Coward · · Score: 0

    Any language that was created in 2011 experienced more growth.
    An infinite percentage of growth to be exact

  9. "Objective-C will be the next big language." by Sebastopol · · Score: 4, Funny

    My IT friend in 1993.

    Time to find him on facebook.

    --
    https://www.accountkiller.com/removal-requested
    1. Re:"Objective-C will be the next big language." by jockm · · Score: 4, Insightful

      My boss and I believed that in '87, it is (IMHO) far better than C++, and at the time it had a great chance. Obj-C was a great language for the time, probably the most advanced practical OO language of the time. Sadly it never got any traction until NeXT.

      Sadder still is the fact that it didn't keep up with the time. It is still state of the art for the late 80s/early 90s; but languages moved on and improved. If they eliminated the need for separate header files (including getting rid of the declaration/implementation divide), added keywords to get rid of the need for the CPP, added autoboxing, and improved runtime errors; it would be a world class language (again).

      As an aside Cocoa is a wonderful and powerful class library, with one major flaw: needlesslyLongAndOverSpecific method names. Where Smalltalk was content with anArray getAt: someIndex NeXT decided to drive in the fact that you were getting an object: [anArray objectAtIndex: someIndex], despite the fact that a NSArray can only old objects. That is a mild example, but the power in the library is amazing.

      Sadly the stewards of Obj-C still seem to think the language is fine as it is, which is a shame. The lamdbas are nice though...

      --

      What do you know I wrote a novel
    2. Re:"Objective-C will be the next big language." by jon3k · · Score: 1

      Well it certainly wasn't the next big one. PHP wasn't introduced until 1995.

    3. Re:"Objective-C will be the next big language." by smash · · Score: 1

      The method names are self documenting. Xcode has tab completion. Get over it. :)

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    4. Re:"Objective-C will be the next big language." by jockm · · Score: 1

      LongAndComplexCamelCasedNamesImpeedUnderstanding

      --

      What do you know I wrote a novel
    5. Re:"Objective-C will be the next big language." by Sebastopol · · Score: 1

      You can totally do Lambdas with Boost. /s :-)

      --
      https://www.accountkiller.com/removal-requested
  10. From 0 to 1 user equals infinite growth. by Anonymous Coward · · Score: 2, Funny

    Fastest growing language is the one you invent yourself.

  11. The top 20 by danbob999 · · Score: 5, Informative

    Java
                    C
                    C#
                    C++
                    Objective-C
                    PHP
                    (Visual)
                    Python
                    Perl
                    JavaScript
                    Delphi/Object
                    Ruby
                    Lisp
                    Pascal
                    Transact-SQL
                    PL/SQL
                    Ada
                    Logo
                    R
                    Lua

    1. Re:The top 20 by Hatta · · Score: 5, Interesting

      Cheers for R! I didn't expect to see a statistical programming environment on this list, but I'm not surprised either. R is getting really big in bioinformatics, which is a burgeoning field right now. I used R myself more often in 2011 than in any previous year, and I'm sure I'll use it more this year. If you use Excel, especially if you use macros or VBscript, you should give R a look. Steeper learning curve, but far more powerful and rewarding.

      --
      Give me Classic Slashdot or give me death!
    2. Re:The top 20 by Trogre · · Score: 1

      Dammit where's bash in that list?

      (grumpy sysadmin here)

      --
      "Nine times out of ten, starting a fire is not the best way to solve the problem." - my wife
    3. Re:The top 20 by Anonymous Coward · · Score: 0

      Blame the Pirate Party for that.

    4. Re:The top 20 by Em+Adespoton · · Score: 1

      I see you prefer Python :D

    5. Re:The top 20 by Anonymous Coward · · Score: 0

      RTFA. It's ~45-50

    6. Re:The top 20 by Anonymous Coward · · Score: 0

      Logo... Because grade schools really are that slow when it comes to changing their curriculum.

      (Likely teaching 5th graders via old photocopies of a 30 year old book that explains how to make the turtle draw a star.)

  12. Notes on the trends. by Animats · · Score: 4, Interesting

    Interesting. Objective-C up (presumably because of iPhone usage), C# passes C++, and Python in a screaming dive.

    The languages that are on the way down suffer from mismanagement. The C++ committee went off into template la-la land years ago, focusing on features used by few and used well by fewer. Python had a "Perl 6" experience - von Rossum pushed the language to Python 3, which is only marginally better, no faster, and incompatible. That seems to have hurt the language's market share.

    The languages on the way up are rather similar. They're strongly and explicitly typed, compilable, memory-safe (mostly), and have garbage collection. That describes Java, C#, and Objective-C, and even Delphi. The only exception on the way up is Javascript, which has progressed from being an awful language to a pervasive although mediocre one. Javascript does have the advantage of fast implementations, unlike Perl and Python.

    These stats, of course, are based on what people are blithering about on blogs, not what's implemented in them.

    1. Re:Notes on the trends. by shutdown+-p+now · · Score: 2

      I mostly agree, but... Delphi has garbage collection? since when?

    2. Re:Notes on the trends. by jd · · Score: 3, Interesting

      C didn't gain any ranks but it did gain in the ratings, so two exceptions. If I'm reading the long-term trends correctly, the more potent languages suffered some at the hands of Visual Basic but as VB has died they have recovered. C++ is doing very badly on the long-term trends - that's not merely a product of templates, it would seem to me that it indicates something more serious. Python's usage in the longer-term trends seems to have stabilized, along with a couple of other languages, with most having falling usage. To me, that suggests more hybridization at least in the fields (mostly teaching) that this survey covers - people aren't using one-size-fits-all languages as much, opting for limited use of languages in specialized areas.

      --
      It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
    3. Re:Notes on the trends. by Anonymous Coward · · Score: 0

      Since forever....

    4. Re:Notes on the trends. by KDR_11k · · Score: 1

      C had an increase in market share as well even though that didn't improve its rank.

      --
      Justice is the sheep getting arrested while an impartial judge declares the vote void.
    5. Re:Notes on the trends. by shutdown+-p+now · · Score: 2

      Last time I looked at it - which was, admittedly, Delphi 7, sometime around 2004 - you had to explicitly call Destroy on objects to release memory. You also got refcounting if you derived from TInterfacedObject, but only for interface-typed references. And you had refcounting with COW for strings.

      That's nowhere even close to a GC.

    6. Re:Notes on the trends. by 19thNervousBreakdown · · Score: 1

      I have a very hard time classifying Objective-C as strongly-typed--no matter how much everyone says it is, it programs like any other weakly-typed language due in large part to the fact that all of its built-in collections are collections of ids, and a large portion (the majority? seems that way when I'm working with it, don't know actual #s) of the framework functions operate only on id. And its primary deployment (iOS) isn't garbage-collected.

      --
      <xml><I><am><so><damn>Web 2.0</damn></so></am></I></xml>
    7. Re:Notes on the trends. by Anonymous Coward · · Score: 1

      Python had a "Perl 6" experience - von Rossum pushed the language to Python 3, which is only marginally better, no faster, and incompatible.

      I don't agree with you. The Python community is, overall, content with Python 3. Takeup of Python 3 has been a bit slow, but I don't think you can really call it a disaster on the level of Perl 6.

      You may think it is only marginally better, but I see Python 3 as a polished jewel. The weird historical artifacts (such as having both "range" and "xrange") have been smoothed away. One of the most attractive things about Python is its clean simplicity, and Python 3 is a worthwhile improvement. I think Python 3 is the best language for teaching introductory programming classes.

    8. Re:Notes on the trends. by hal2814 · · Score: 1

      I'd argue that the Smalltalkish message-passing and shallow inheritance in the API make Objective-C feel more weakly-typed than it's non-templated collection classes, but I completely get what you're saying. As far as iOS garbage collection, Automatic Reference Counting (ARC) was deployed with the iOS 5 SDK (which can compile at least as low as iOS 4.2 with few restrictions) so for any new development, Objective-C very much has garbage collection as an option.

    9. Re:Notes on the trends. by 19thNervousBreakdown · · Score: 1

      Yeah, I agree that there's other things that contribute more to the "feel" than the collection classes, but this is Slashdot and the collection classes not supporting strong typing is a much harder thing to argue against than API feel.

      On that subject, ARC is definitely not garbage collection. As almost an opposite cousin to the technically-strongly-typed-but-feels-weakly-typed type system, ARC feels like garbage collection but is technically not. See: http://stackoverflow.com/questions/6385212/how-does-the-new-automatic-reference-counting-mechanism-work

      There are claims that each of these gives you the best of both worlds, but maybe that comes with experience, because as someone still picking up the language I've found that you generally get the worst of both worlds with both of them, as you have to learn the pitfalls of both sides, but don't get to take (much) advantage of the benefits of either. All in all, coming from C++ and C#, I am not a huge fan of Obj-C so far.

      --
      <xml><I><am><so><damn>Web 2.0</damn></so></am></I></xml>
    10. Re:Notes on the trends. by epine · · Score: 3, Insightful

      C++ is doing very badly on the long-term trends - that's not merely a product of templates, it would seem to me that it indicates something more serious.

      How the heck did you factor templates out of the equation? I am not a member of the Order of the Crystal Ball. Please enlighten me. For the last seven years, C++ has frequently crisscrossed 10% (of what, one wonders) most recently about six months ago if I skimmed the chart correctly. It's a small uptick shy of steady state.

      I don't think C++ really should have become as popular as it once was. I'm sure it was supplanted in many cases for languages better suited to task, with automatic instead of standard transmissions, as the automatic transmissions improved over time. C++ is best used where the constraints on the acceptable solution are more severe than constraints of available talent. Scaling out Google or Facebook are good examples. Even there, C++ is best applied selectively. Or if you already have the skills, there are a lot of computations where C++ is easy enough to code and nearly impossible to beat.

      I would say that the education cost of C++ mastery is just too much for most coders. Few people working on the hardest problems give much thought to education cost, however, if the lever rocks your world. I've never seen templates as being conceptually difficult. The problem has always been the diagnostics. It would have been nice to have something like concepts, or perhaps the vastly improved Clang diagnostics will mitigate matters enough.

      I'm mostly using R these days and calling out to C++ where I get the most bang for my buck.

    11. Re:Notes on the trends. by Anonymous Coward · · Score: 0

      ARC is not garbage collection by the normal definition. There is no runtime component doing the clean up. The compiler inserts retain and release messages at the appropriate points in the code based on convention and static analysis.

      One of the big implications is that cycles are not handled automatically as they would be in a (well-implemented) GC.

      It's actually pretty neat.

    12. Re:Notes on the trends. by dzfoo · · Score: 1

      Only if you use TObject and it's descendants. If you go for TInterfacedObject you not only get automatic reference counting and memory management, you also get interfaces and a crude form of introspection.

            dZ.

      --
      Carol vs. Ghost
      ...Can you save Christmas?
    13. Re:Notes on the trends. by shutdown+-p+now · · Score: 1

      To the best of my knowledge, all that TInterfacedObject gives you with respect to memory management is a standard implementation of AddRef/Release that will call Destroy once the refcount hits zero. The problem is that Delphi still won't treat references to TInterfacedObject, or any derived class type, as anything special - in particular, it won't call AddRef/Release on them automatically. It will only do that on references of interface types. So if you want automatic refcounting, you pretty much have to only ever pass around interface references, and write an interface for every class you define.

    14. Re:Notes on the trends. by BasilBrush · · Score: 1

      I know what you mean about collections being ids and that making it seem a bit weakly typed. But I don't know many other places in the API that use ids. It seems to me to be about halfway between a real strongly typed language such as Java and a weakly typed language such as Python.

      iOS doesn't support GC, but GCs been deprecated in favour of ARC anyway. And that IS supported on iOS 4.0 onwards.

    15. Re:Notes on the trends. by jd · · Score: 3, Informative

      If you ignore the peaks and troughs, looking only at the general trend, it has been on a fairly steady decline since 2002 according to that graph. (I'm completely ignoring the specific values, for a graph like this you always want to plot a smooth curve that reflects the general pattern and not the individual data points.)

      Because the graph is based on what is taught, you're looking at a latency of 1-2 years - maybe more - to factor in the delay between the changes in demand and changes in the classroom. That would imply that the demand itself changed around 2000 at the latest. The steady decline also means that the 2003 and 2008 revisions to the standard have not significantly altered the trend - up or down - and that the problems originate with the C++ 1998 standard (the last one before the known start of the decline).

      My guess is that between 1998 and 2000, there would have been a rise in usage of C++ (standards make programming much easier), that it crested around that time and that the decline (which I'm estimating to have started midway between the first and second formal language specifications) came from better specialist tools. I honestly couldn't tell you when CORBA started dying as a standard, but it seems to me that it was around the same timeframe and for much the same reason as I'm giving for C++ (RPC is perfectly good for remote functions, sockets are perfectly good for streaming data, etc - you just don't need a top-heavy solution that can do anything adequately but nothing brilliantly).

      Likewise, I think that's part of why scripting languages are starting to suffer. A lot of them are becoming extremely top-heavy and whilst that might make programmers happy in the short-term (they don't have to mix languages right there and then), it makes programmers unhappy in the long-term (they do have to mix languages anyway, it's just more complicated to do so and they feel like they were promised they didn't have to).

      If I extrapolate from this, I'm going to say XML (which now requires a monstrous number of libraries to process in various ways) is going to fall out of favour. Architecture-neutral data storage can be done using NetCDF, a key/value database like QDBM is quicker to read/write than an XML database, precisely because XML is often processed as ASCII text it is not very good at handling UTF32 safely, and unordered data is a bugger to read. Specialist tools already exist to do all of the things XML is used for, so I would expect XML to lose ground to those tools once it passes the critical threshold of complexity. It does not appear to have hit that threshold yet, but it will if it continues to gain complexity with no obvious corresponding gain in usefulness. (XML is very useful for some tasks but it doesn't become more useful for those tasks because of XML-RPC or other rarely-used extensions.)

      Ada was once extremely popular, far more so than now, but lost a lot of ground because it also became extremely complex. There have been times when Ada has been the laughing-stock of programming because nobody could build a compiler capable of handling it. It was only partially implemented, which caused severe problems for portability but also for provability. (Ada was the flagship language of Formal Methods for a long time, but incomplete and overweight ships sink. It damaged the entire Formal Methods methodology to such an extent that it may never recover.)

      This pattern also explains the love-hate relationship with X11 and with other designs that got.... a little too flamboyant. My old Software Engineering instructor used to represent this with a picture of a tyre swing with three ropes holding the tyre up. Each rope functions perfectly as designed, but the result is unusable.

      --
      It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
    16. Re:Notes on the trends. by fyngyrz · · Score: 1

      ...and I don't agree with you. There is nothing about Python 3 that is worth the incompatibility. We're at 2 here and we're staying there. And we write one heck of a lot of Python.

      --
      I've fallen off your lawn, and I can't get up.
    17. Re:Notes on the trends. by hal2814 · · Score: 1

      I know it's a whole different ballgame than the tracing algorithms Java and C# use, but way way way back when I was in college we learned that reference counting is a form of garbage collection. Maybe I'm wrong. Personally, I like Objective-C better than C++ (never really warmed to that language) but I do prefer C# to both, especially now that it supports some more functional concepts like lambda expressions.

    18. Re:Notes on the trends. by Anonymous Coward · · Score: 0

      Objective C has Lambda expressions and clangs version of C and C++.

    19. Re:Notes on the trends. by julesh · · Score: 1

      The primary benefit of Python 3 is that as a cleaner language it's easier to learn. If you're already a regular Python 2 user, you are not in the group of people who will benefit from the changes. I'm an irregular Python user, and Python 3 looks a *lot* more attractive to me.

    20. Re:Notes on the trends. by Kjella · · Score: 1

      precisely because XML is often processed as ASCII text it is not very good at handling UTF32 safely

      Any software that does that will choke on anything not in ASCII, it won't even get æøå right like even Slashdot manages to do. Almost everything that wants to be used outside the US uses UTF8 encoding these days, and it'll expand to UTF16/24/32 as needed. The reason why most everything will choke on UTF32 is that almost no system is ready to handle four byte characters. With UTF16 allowing dual-width characters (2x16 bits) and every currently used language fitting in the basic plane of UTF16 with plenty to spare for all historic languages we're likely to find and then some it's unlikely we'll ever need UTF32. Maybe if we start running to aliens and they give us all their languages as well, but not otherwise.

      --
      Live today, because you never know what tomorrow brings
  13. Logo by LateArthurDent · · Score: 4, Interesting

    I've seen logo used a lot in multi-agent systems research. It just lends itself well to that, with every turtle being an agent.

    1. Re:Logo by Anonymous Coward · · Score: 0

      I haven't seen logo mentioned anywhere since I came second place in a national logo programming competition for kids in primary school. That was 24 years ago. They gave me a Cross pen. I was always jealous of the guy who came 1st, they gave him some cheap ass calculator.

    2. Re:Logo by Timmmm · · Score: 1

      I think it would take me less time to implement a turtle-like environment in Matlab or C++ than it would to relearn Logo. And then I wouldn't have to use Logo.

      I'm not saying Logo isn't cool; it just isn't cool for anything other than learning very basic programming by drawing pretty pictures. And I have no idea how you would use it in multi-agent systems research. Can you even have more than one turtle? How on earth do you do matrix multiplication in Logo?

    3. Re:Logo by Anonymous Coward · · Score: 0
    4. Re:Logo by Rubinstien · · Score: 1

      If you are really interested in understanding how LOGO might apply to subjects outside of teaching turtles to draw pictures, find or borrow a copy of Seymour Papert's Mindstorms Children, Computers, and Powerful Ideas [ ISBN: 0-465-04629-0 ]. The book is a quick read, and covers the work that went into developing the language at MIT as part of an experiment in finding better ways to teach children, starting in the late 1960's through the early 1980's when the book was written. The first several chapters do contain lots of images of turtle drawings, or more accurately, Turtle Geometry, but starting about midway through the book, Papert introduces the concept of MicroWorlds, specialized environments for modelling and experimenting with other formal systems. In the Geometry MicroWorld, the turtle is an analogue to a "point", for the most part -- in other 2D drawing languages there is generally the concept of a "current point" with some associated state. In other MicroWorlds, the turtle becomes an analogue for other abstract concepts -- in the Newtonian Physics MicroWorld, for example, the turtle might represent a particle. In addition to position in space it has other associated state such as current velocity and heading. The turtle concept is extended to allow kids to experiment with different aspects of formal systems. More elaborate concepts are added over time, new turtle types are derived (velocity turtle, acceleration turtle, etc.,), and richer state is provided, along with allowing the turtle objects to interact with each other and other objects in these environments.

      I guess a way of summarizing it is to say that LOGO is/was about building environments that encapsulate the rules of a formal system, and allowing individuals to interact with the objects in those environments to modify their state according to the rules -- and observe the results. The intended goal was to allow children to have environments in which they can discover the rules for themselves, and develop an intuitive understanding of the system and how to go about solving problems according to the rules they have discovered. This was applied in experiments covering mathematics, physics, and even poetry. Papert was not proposing LOGO as the tool to be used for these purposes, however -- he considered it too primitive, limited by the capabilities and availability of computers in the 1970s. What he was proposing was that the concept of modelling specialized environments with computers had merit by making abstract concepts into something that learners could "play" with, but predicted that such a revolution would not come until the machines were cheap and ubiquitous. I know that most of my daughter's AP Physics lessons last year had associated Java applets available to demonstrate concepts -- but most of it was utter, buggy crap. There were several times where I had to tell her what the applet *should* have done, if it had worked -- but even when things did work none of it really let her "play" with concepts very much. I had to keep working with her throughout the year to help her develop better and more intuitive understanding of concepts. Papert's revolution hasn't arrived yet.

    5. Re:Logo by Sigg3.net · · Score: 1

      Like a kid friendly Matrix at the beach?

  14. Interesting. by jd · · Score: 2

    Anyone here want to comment on Lua? It's now provided with LaTeX to help provide a bit more oomph, but I'm torn between learning it and seeing what other scripting languages are added in.

    Objective C and C# are not terribly surprising but given that there are plenty of C-based languages that never even made the top 20, I find it curious as to which C-based languages are thriving and which are not. If it were on the merits of the language alone, then you'd expect usage to reflect specific features, and I was assured repeatedly in the discussion on Java that languages were not (as I'd claimed) popular due to promotion. Surely not all those people could be wrong, could they?

    Logo's popularity is puzzling as this is far too recent a survey to reflect the UK's demand to switch from learning about office supplies in IT to learning about writing software and starting off on 2D graphics applications. However, precisely because of that switch, I'd expect Logo's popularity to rise at least a little bit more. It is, after all, a language designed to start people off on writing 2D graphics applications.

    Pascal, Delphi and Ada get mentions, but Modula-2 and Modula-3 do not. Nor does Eiffel. Not a terrible shock, but again it does say a lot about perceptions in regards to usage. I'm no fan of Modula-2 or Modula-3, but there are bound to be cases where they're more appropriate choices but the others are used instead.

    --
    It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
    1. Re:Interesting. by Darinbob · · Score: 1, Interesting

      Lua is probably the smallest and easiest language to integrate into a system and is extremely powerful for its size. While you can write full blown applications only in Lua it's real purpose is to be a subordinate add on to another program or system. A lot of people point to games when Lua is mentioned but there's nothing inherent about games in it. So you'll see this a lot more in embedded systems coming up I think. For example, unlike say Ruby or Python it doesn't come with a lot in the library but you can build your own customized to your own needs. No object oriented system but again you can create your own (from small efficient things to overblown monstrosities that make me think someone was missing the point). It's a relatively mature language as well.

    2. Re:Interesting. by aralin · · Score: 1

      Lua has been used in multiplayer online games as the choice language for writting addons and extensions for quite some time now.

      --
      If programs would be read like poetry, most programmers would be Vogons.
    3. Re:Interesting. by sourcerror · · Score: 1

      Lua is preferred in games to other scripting languages, because it's extremely fast. (2-3 times faster than CPython). What I didn't like about is the idioms surrounding the metatable (used to hack on OOP elements, and other language extending magic). It looks more complicated than it should.

    4. Re:Interesting. by Em+Adespoton · · Score: 1

      I do notice that Forth is missing from that list as well... but I'm not surprised. Most people don't want to deal with hardware these days.

    5. Re:Interesting. by jd · · Score: 1

      What shocked me was an interview I was on some years back for the position as a BIOS programmer. I was told "programmers don't do BIOSes", flat-out by the interviewer. Sorry, they don't grow on binary trees. I was also told "programmers don't do assembly or Forth", leaving me to wonder what else the interviewer was wanting to hire the tooth fairy for.

      The very notion of a programmer not wanting to program is beyond my comprehension. A problem is a problem, a solution is a solution, specs are specs and code is code. Why should someone really, truly, passionately care that byte X is in a register rather than in a heap? Does it make that much of a difference? Is a queue or a ring buffer any less of a queue or a ring buffer because you're directly sending words to a port rather than a virtual object? The PCI Express bus uses 4K packets that are addressed to specific devices, so what if that's an on-the-wire protocol? It's not like there's a Spanish OSI Inquisition. Or, at least, not one that's expected.

      --
      It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
    6. Re:Interesting. by brendank310 · · Score: 3, Interesting

      As mentioned by someone above, Logo is being used in a lot of agent-based modeling research. One in particular came up time and time again in a seminar class I took on complex systems was NetLogo. Some poor economics PhD was working on modeling the relationship between groundwater depletion and policy approaches to curbing its overuse, and his simulations were taking weeks with something like 100 nodes. Too bad it isn't open source, might be fun to try to parallelize simulation runs.

    7. Re:Interesting. by djrobxx · · Score: 1

      Lua is also used in the MiCasaVerde Vera home automation system. It's lightweight enough to run in router firmware, but powerful enough to allow users to script advanced home control logic, or even develop "drivers" for alarm panels or other serial devices it doesn't support out of the box.

    8. Re:Interesting. by Xest · · Score: 1

      "I find it curious as to which C-based languages are thriving and which are not. If it were on the merits of the language alone, then you'd expect usage to reflect specific features, and I was assured repeatedly in the discussion on Java that languages were not (as I'd claimed) popular due to promotion."

      It's all down to whether the language has been granted a purpose.

      C# rises because Microsoft has made it the defacto option for developing for their platform.

      Java rose, because it was chosen by universities as the defacto teaching language

      Objective C rose because of the increased popularity of iOS.

      So it's really simple, a language succedes when it's been given a popular cause to. You could make the most beautiful C-like language in the world, but if it's not picked up for any wild scale reason (i.e. made a learning language across nearly all unis, or attached to a popular product) then it wont go anywhere.

      But keep in mind the TIOBE index just measures discussion of languages, not actual real world usage - there's a fair argument that Java's position is boosted more than C#'s for example because if Java is used as a training language it will produce disporportionately more questions than a language that is not - new developers are going to ask more questions than professional developers.

      Similarly buzz around iProducts is extremely high, they're talked about massively disproportionately to their actual marketshare, and if the language they use, Objective C gets more mentions as a result, it'll boost it's ranking.

      So Logo's popularity could again be more about students asking questions related to it rather than anyone actually using it for any projects.

      Of course, you can argue that this type of learning is usage, and it is to some extent, but it seems a weak definition to me - if a C++ coder sits for 3 days solid writing C++ code at work without needing to consult the internet for help by posting a question, then after 3 days finally has to ask one question, does that really mean C++ is being used less than the kid using Logo at school who asks 5 different questions in 2 hours whilst he's doing his homework?

      These are the problems with TIOBEs methodology, and a better measure of popularity is to take a global sample of job listings in various cities across the world to see what companies are actually recruiting for - that gives us a more realistic idea of what's really, actually being used IMO.

    9. Re:Interesting. by gbjbaanb · · Score: 1

      These are the problems with TIOBEs methodology, and a better measure of popularity is to take a global sample of job listings in various cities across the world to see what companies are actually recruiting for - that gives us a more realistic idea of what's really, actually being used IMO.

      I can't say globally, but the UK has the IT Jobs Watch which is based on job adverts. FYI, top skill is for "developer", 2nd for "finance", 3rd for "SQL".

      You can filter by programming languages.

      It also shows average salaries, which I think is far more important than popularity. C# for example is around £40k, Java at £47k. For a contractor, C++ may have fallen in popularity but pays £100 a day more than C# contractors.

      For languages, the biggest jumpers are Scala (on £55k) and Ruby (on £47.5k).

    10. Re:Interesting. by Xest · · Score: 1

      "It also shows average salaries, which I think is far more important than popularity."

      By what metric? Average wages are governed like most other things, by supply and demand, if the wage is higher it means there's a shortage, and there's a good chance that there's a shortage because it's not a thriving market.

      You only have to look at the millenium bug for evidence of this - COBOL programmers were getting paid an absolute fortune but it was short lived- the salaries were paid to get essential fixes in but ultimately no new projects would then be started in COBOL because staffing them was too expensive, and similarly as many systems as possible were moved off of COBOL because again, hiring staff to maintain them was too expensive.

      The fundamental problem is that if say, Scala is commanding a high salary, it may be a good short term investment - go for it, rake in the £55k, but then what happens when your Scala project is finally made obsolete due to said cost and you have to start looking for a new job, or simply because you want to move up the career ladder? or even what if your employer has to make redundancies? There'll be no new Scala jobs, and the .NET shops wont touch you because you haven't been using it.

      There's also the point that the Scala market is so utterly tiny, and the Ruby market relatively so too, that although they may command higher average wages, because the community is so small by virtue of the very way averages works there'll still be more high paid C# jobs than scala jobs anyway, e.g. if there's 100 scala jobs and they pay in the range of say £55k, then there may be 10,000 C# jobs, of which most pay may be only £25k, but still 500 of which (i.e. more than scala) are paying as much as say £80k. This does mean there may also be more competition for the C# jobs too of course, but in my experience that's not the case - there's so many C# jobs out there companies just can't fill them, when I last looked I could basically name my wage (and I did, and got it without even any hesitation as my employer had been looking for 9 months already, and kicked myself aftewards for not asking for even more!!).

      There are other factors of course, looking at Scala job availability they appear, in the UK, to be almost in their entirety, situated in London's financial sector, which has disadvatanges in itself, the £55k Scala dev in London is going to feel a lot more poor than the £40k C# dev in say Leeds, because of the massively higher cost of living in London.

      I'm not saying there aren't circumstances where being a Scala dev or whatever isn't nice, if you've always lived in London and are happy there then sure it's a pretty decent option, but for many it's a non-starter, you'll often be lucky to even find a Scala job outside of London. It's a similar story now even for Java, it's so much easier to pick up a C# or PHP job, and I've certainly seen no better financial prospects in going for Java roles instead here in the North of England.

      I suspect any personal choice on technology has to come down to personal circumstances, and when you've got some years experience under your belt going for more obscure languages is much easier, but for graduates fresh out of university, living and working outside of London for example who would be glad of any kind of employment right now, C# is definitely a guaranteed answer to that, and they'll find themselves on much more than the national average wage from the outset even which is more than many of our current 2 million unemployed could even wish for!

    11. Re:Interesting. by Osgeld · · Score: 1

      care to site more than the WOW GUI ?

    12. Re:Interesting. by Osgeld · · Score: 1

      lua is sudocode that works

      it can be very flexable and useful, it can also be a complicated pain in the ass that makes you reinvent the wheel just to get simple shit done

      my thought is ... if you can structure a complete program in your mind from start to finish lua is fine, if you have to think about it go elseware cause your probally going to end up writing a bunch of C shit anyway just to get lua to do what you want it to, and at that point ...

    13. Re:Interesting. by gbjbaanb · · Score: 1

      some of that's true, but the metric I choose to be important is the one that pays me more :)

      If someone wants a career helping others, and has the talent to be a doctor, they become a doctor, they do not choose to be charity workers or minimum-wage carers after all.

      As for salaries, I did a search for 'manager' in the local area recently, (looking for a IT mgr job I'd seen). A 'manager' job selling fish and chip supplies earns more than most programmers. I was a little surprised, as it didn't seem to require much effort or skill at all.

      As for averages, you have to look at everyone, not just yourself to decide things for the graduates. As for changing jobs, you simply 'lie' - "I am a great .net dev, but I've been using scala for my last rle so I may be a bit rusty" is all it takes, but you must be able to back it up somewhat and to be fair anyone who's taken the trouble to get into Scala will pick up C# in a few moments.
      I don't know what the job market will look like in a few years, but I think C# will fade (as you say, people can't hire them, so they will look elsewhere for the candidates) and HTML will rise. I can't really say any more than that though, unless more Linuxy-style languages appear.

    14. Re:Interesting. by Xest · · Score: 1

      Yes, but the point is in this case, that on average you wont be paid more following this route because the jobs just aren't there for most people, and in the long run it may be a career dead end, which will whipe out any benefits of short term pay gain, that's the fundamental problem with going for an obscure, or dying language. The point is that whilst you may be one of the lucky ones who manages to outdo the averages, and actually thrive off the benefits of a higher paying, more obscure option, that for everyone that does that, there must be someone that fails, hence the average case. It's quite a gamble for your career.

      "As for averages, you have to look at everyone, not just yourself to decide things for the graduates."

      That was exactly my point - on average .NET is a far superior option for grads, because it's the development skillset that is most employable right now. For the odd unique case, i.e. those who have somewhere they can stay for free in London, then it may well be that that's not the case, but .NET is going to be far and away the best option for candidates.

      "As for changing jobs, you simply 'lie'"

      But when you're pretty high up in your game, rusty isn't good enough - the argument works fine if you're going for junior or low-mid range jobs, but if you're at the mid, to upper range level of skill "I'm a bit rusty" just doesn't cut it, because you'll be up against candidates who aren't. So sure you may still find work as a .NET job but it'll be at the lower end of the scale - £25k or so, and you'll have to spend a couple of years there to get the experience companies are looking for, by that point taking in that low wage will have undone the benefits of a short stint at a higher wage relative to just going for something more employable from the outset.

      "I don't know what the job market will look like in a few years, but I think C# will fade (as you say, people can't hire them, so they will look elsewhere for the candidates) and HTML will rise."

      But what will replace it? The C# market is churning out devs as fast as any other option, so sure you can move from C# to a different language, but that language will suffer recruitment problems to an even greater degree so you don't solve anything by moving away. I think growth for .NET will slow, largely because of the shift to mobile and because it'll take MS some time, if at all to move more strongly into mobile, but I think it'll be the best bet for quite some time to come.

      It's always worth keeping an eye on the horizon, to try and spot the next big thing, but I don't think we're there yet, .NET doesn't even seem to have reached it's peak yet due to the very fact growth still actually seems to be accelerating right now, only when it's stopped accelerating and starts to become flat will it be at it's peak.

      You're right that HTML/Javascript skills are becoming much more important, but they're still not seen as high paying jobs, and if I'm honest even at my current employer we treat it as such, HTML/Javascript is, in all but the most complex cases, something that can be delegated to fairly fresh graduates pretty safely. Amongst our more senior devs, HTML is something they know inside out, it's not a specific sought for skill in itself at that level - it's something you're expected to know as standard, with your main languages (i.e. Java etc.) on top. The Javascript side will probably become more important and more skilled with canvas of course, as this is where you start to require some ability in mathematics to do some really fancy stuff, but I still think it'll remain a lower paying skill.

  15. Does it matter how it's popular? by nobodyman · · Score: 1

    I'm not sure I understand how it matters why it's popular. The index isn't a listing of strictly general purpose programming language.

  16. At least Scala is dead by SQLz · · Score: 1

    Fallen out of the top 50 into obscurity where it belongs.

    1. Re:At least Scala is dead by nicholas22 · · Score: 1

      I'm very surprised... But it's just Tiobe, which uses a brute-force "page-count" approach. Scala is becoming more and more relevant. Lots of projects in major banks are being done in Scala, some would say "eating" Java's lunch. But in my opinion, these two language can co-exist very harmoniously...

  17. Yiobe's bogus metrics by edxwelch · · Score: 5, Informative

    Tiobe generates the rating by the search results of google/bing, etc. So basically, it's just measuring how many web pages mention a particular language. It does *not* measure the actual usage of the language in applications.

    1. Re:Yiobe's bogus metrics by Anonymous Coward · · Score: 0

      I can't think of a much better way of measuring usage of programming languages can you?

    2. Re:Yiobe's bogus metrics by nicholas22 · · Score: 1

      From my experience (Lead dev, London, Finance, JVM) I'm hearing of more and more projects being done in Scala and Java than any of these other languages...

    3. Re:Yiobe's bogus metrics by Em+Adespoton · · Score: 1

      Not offhand (other than by polls and surveys)... but it seems to me that the languages requiring the most documentation and support libraries would be the ones that would rise to the top via that method. Thus, more open languages, languages used more for internet-related functions, and languages that involve heavy compartmentalization would show up, while things like shell scripting and ASM, no matter how prevalent, would be unlikely to show up.

      The fact that the Vaults of Parnassus no longer exists, but you can get the same stuff via non-web locations probably contributes to Python's fall.

    4. Re:Yiobe's bogus metrics by BasilBrush · · Score: 1

      It doesn't claim to measure actual usage. Indeed they explicitly point out that's not what they are measuring. So your expectation is bogus, not the metric. The metric is exactly what they say it is.

    5. Re:Yiobe's bogus metrics by edxwelch · · Score: 1

      No, actually it does. This is the statement from their web site:
      "This award is given to the programming language that gained most market share in 2011"

  18. It's the conjuncture by TarMil · · Score: 1

    With all these countries losing their subjective AAAs, it's quite logical that the objective C gains interest.

  19. The TIOBE index is nothing but a giant troll. by Anonymous Coward · · Score: 0

    In many cases they can't even remotely accurately detect what language they are looking at described in a web page.

  20. The reason for its popularity... by Timbo · · Score: 4, Informative

    ...is obviously because of iOS. More specifically it's because when Steve Jobs rejoined Apple in 1996 he brought with his a lot of NeXTStep tech, including Obj-C. That's why many of the system types have the 'NS' prefix. History lesson aside, it's rather a shame as it's (in my opinion) a rather poor and outdated language. If I'm ever asked by people who aren't familiar with it what it's like I say that it's the anti-sibling to C++. By this I mean that it has the same parentage as C++, but where C++ went down one path, Obj-C took the other. The fact that most well regarded modern languages have more in common with C++ than Obj-C should indicate that they made mistakes in its design. Obj-C's biggest failing is its tendency to fail at runtime rather than during compilation. This is mostly down to its weak type system.

    Don't get me wrong, I think C++ is getting pretty creaky too. I'm quite fond of D; in a fantasy world, some big commercial player will start using it and make it popular.

    1. Re:The reason for its popularity... by Anonymous Coward · · Score: 0

      History lesson aside, it's rather a shame as it's (in my opinion) a rather poor and outdated language. If I'm ever asked by people who aren't familiar with it what it's like I say that it's the anti-sibling to C++.

      You sometimes hear this said about Obj-C and it is somewhat true. It's syntax is a little outdated in comparison to some of the more modern languages but other things like the dynamic typing being a big issue are long since history; Objective-C compilers will now give you a lot more compile time information and make these kind of runtime errors largely a thing of the past. Obj-C is far from perfect but it's a much nicer language than the bloated hell that is C++.

    2. Re:The reason for its popularity... by iluvcapra · · Score: 1

      Obj-C's biggest failing is its tendency to fail at runtime rather than during compilation.

      Are you sure this isn't just a matter of taste? It gives it scripting-language agility and introspection with compiled language speeds, and still most of the type checking features are available when you want them, it just doesn't compel them.

      The people who hate really Objective-C the most seem to be the people who are paid to write IEnumeratesEveryOddThursday interfaces and AbstractClassFactoryIntegerSerializationDataFactory classes for a living. Also, people who expect garbage collection on every platform, they aren't crazy about it either :)

      --
      Don't blame me, I voted for Baltar.
    3. Re:The reason for its popularity... by Timbo · · Score: 3, Insightful

      You sometimes hear this said about Obj-C and it is somewhat true. It's syntax is a little outdated in comparison to some of the more modern languages but other things like the dynamic typing being a big issue are long since history; Objective-C compilers will now give you a lot more compile time information and make these kind of runtime errors largely a thing of the past. Obj-C is far from perfect but it's a much nicer language than the bloated hell that is C++.

      Compilers can only compensate for the language's failures, not fix them. Having said that, the 'Analyze' option in Xcode 4 is pretty good.

      Language bloat isn't a problem in itself. You are free not to use the features you consider bloat, at no cost. Where it does become a problem is when new language features are shoe-horned with every effort not to break compatibility. The result is obscure new syntax and existing features that should have gone the way of the Dodo. This is where C++11 is, if you ask me.

    4. Re:The reason for its popularity... by Timbo · · Score: 1

      Are you sure this isn't just a matter of taste?

      To some extent I guess; it depends how confident you are in your code. At the extreme end of functional programming you can prove that a certain program is correct before you even run it. This is very hard to do with a dynamic language.

      It gives it scripting-language agility and introspection with compiled language speeds, and still most of the type checking features are available when you want them, it just doesn't compel them.

      C# has reflection whilst being strongly-typed. The two things aren't mutally exclusive.

    5. Re:The reason for its popularity... by 19thNervousBreakdown · · Score: 1

      things like the dynamic typing being a big issue are long since history; Objective-C compilers will now give you a lot more compile time information and make these kind of runtime errors largely a thing of the past.

      Ahahahahaha... that's rich. I mean, sure, it's true (as long as you don't try working with a collection, or any of the multitudes of #DEFINEs that the static analysis can't handle, or any of the API functions that only work on id even though they expect a particular type, or override any of the built-in functions that return id even when there's no need to do so), it's just funny.

      As for it being nicer than C++, well, that's entirely ... Subjective.

      --
      <xml><I><am><so><damn>Web 2.0</damn></so></am></I></xml>
    6. Re:The reason for its popularity... by dzfoo · · Score: 2

      I think the point was that Objective-C is compiled to native machine code and it has instrospection along with dynamic typing. C# may have those capabilities but at the cost of running in a VM.

            dZ.

      --
      Carol vs. Ghost
      ...Can you save Christmas?
    7. Re:The reason for its popularity... by BasilBrush · · Score: 1

      In case you haven't noticed, buggy C programs will fail at runtime just as much as buggy Obj-C programs. You treat a pointer to foo as if it's a pointer to unrelated class bar, it'll fail more often at runtime in C++ than in Obj-C.

      What I think you meant is that the C++ compiler will catch more programmer errors at compile time than Obj-C the compiler will. But with the standard Obj-C compiler front end being LLVM now, the reverse is true. LLVM Obj-C compiler will catch far more programmer errors than the standard GCC C++ compiler.

      On top of this, Obj-C allows techniques such as introspection that are just not available on C++.

    8. Re:The reason for its popularity... by Timbo · · Score: 1

      You treat a pointer to foo as if it's a pointer to unrelated class bar, it'll fail more often at runtime in C++ than in Obj-C.

      Of course strongly typed languages can fail at runtime; I'm not suggesting they don't. What I am saying is that having a strong type system makes you more likely to catch the failures at compile time. The hypothetical you've just stated would require an explicit reinterpret_cast to get a foo pointer to point to a bar i.e. you're asking the compiler not to point out your mistake.

      What I think you meant is that the C++ compiler will catch more programmer errors at compile time than Obj-C the compiler will. But with the standard Obj-C compiler front end being LLVM now, the reverse is true. LLVM Obj-C compiler will catch far more programmer errors than the standard GCC C++ compiler.

      I said it elsewhere, but the compiler can only compensate for the failures of the language -- it can't fix them. When the language allows you to fail exotically at runtime in ways that are statically unpredictable, the compiler is irrelevant. Almost all languages except for the strictest functional ones have these failure modes, but weakly typed languages have them more. Out of interest how would you rank LLVM Obj-C against LLVM C++?

      On top of this, Obj-C allows techniques such as introspection that are just not available on C++.

      That's not entirely true. Qt (the widget library) is an example of a C++ based code base that does introspection. To be honest though in my career I can only think of a handful of times where introspection has been useful and in most of those cases there were better solutions to the problem that didn't need it.

      I'm kind of coming out of this sounding like a C++ apologist; I'm really not. Objective-C is not the answer though. It smells of the 80s.

    9. Re:The reason for its popularity... by BasilBrush · · Score: 1

      What I am saying is that having a strong type system makes you more likely to catch the failures at compile time. The hypothetical you've just stated would require an explicit reinterpret_cast to get a foo pointer to point to a bar i.e. you're asking the compiler not to point out your mistake.

      Not necessarily. id is what makes Obj-C somewhat weakly typed. But C++ has void* which has less type information than id does.

      Out of interest how would you rank LLVM Obj-C against LLVM C++?

      I couldn't say. I used to do C++ with GCC, then Obj-C with GCC, now Obj-C with LLVM. I think most people are still using GC for C++.

      I'm kind of coming out of this sounding like a C++ apologist; I'm really not. Objective-C is not the answer though. It smells of the 80s.

      For sure, they both smell of the 80s. Obj-C is far from perfect. But it's much nicer than C++.

    10. Re:The reason for its popularity... by Anonymous Coward · · Score: 0

      Of course strongly typed languages can fail at runtime; I'm not suggesting they don't. What I am saying is that having a strong type system makes you more likely to catch the failures at compile time.

      So what you're saying is, "Compilers can only compensate for the language's failures."

    11. Re:The reason for its popularity... by Timbo · · Score: 1

      Not necessarily. id is what makes Obj-C somewhat weakly typed. But C++ has void* which has less type information than id does.

      Yes, you can choose to use void pointers and subvert the type system if you so wish. That's a pretty dumb choice though and you deserve everything you get if your programs end up error prone. Obj-C's id type is an integral and unavoidable part of the language. Comparing the two things is a bit silly I think.

      For sure, they both smell of the 80s. Obj-C is far from perfect. But it's much nicer than C++.

      I think we'll have to agree to disagree. Both languages need to die off, but potential successors should resemble C++ far more than Obj-C.

    12. Re:The reason for its popularity... by BasilBrush · · Score: 1

      Yes, you can choose to use void pointers and subvert the type system if you so wish. That's a pretty dumb choice though and you deserve everything you get if your programs end up error prone. Obj-C's id type is an integral and unavoidable part of the language. Comparing the two things is a bit silly I think.

      Both id and void* are part of the language. Both are avoidable. But of course we end up using them if the library uses them.

      With Obj-C you end up using id when you use Apple's Foundation library collection classes.

      With C++ you are using them with printf. The first parameter is a char*, and then you implicitly have an unlimited number of void* parameters. And if you get the type wrong, they'll only fail at run time.

      I suppose there's a difference there in that C++ have templates, and that helps avoid void*. But then we're getting into features that one languages has that the other doesn't. Obj-C for example has categories, which allow you to extend the functionality of a library class - even if you don't have the source for it. C++ can't do that. It can only subclass. Which doesn't help if someone else's code is creating the class in the first place.

    13. Re:The reason for its popularity... by lars_stefan_axelsson · · Score: 1

      Language bloat isn't a problem in itself. You are free not to use the features you consider bloat, at no cost.

      Spoken like someone that has never needed to maintain other people's code. You might not write code using these features, but if they're there, you must be able to read and understand them because someone else will use them.

      And team/employer coding standards won't work, because they a) have to be followed to the letter, and b) other teams/employers don't use the same standards.

      We learnt this already with PL/1 (granted they made the mother of all such mistakes). It's a mistake that we shouldn't have to make over and over again. Language bloat is a problem because people (i.e. programmers) aren't suited to using overly large and complex languages.

      --
      Stefan Axelsson
    14. Re:The reason for its popularity... by Timbo · · Score: 1

      Both id and void* are part of the language. Both are avoidable. But of course we end up using them if the library uses them.

      With Obj-C you end up using id when you use Apple's Foundation library collection classes.

      OK, technically the standard library is not Obj-C, but you'll have a pretty hard time not using it for most purposes.

      With C++ you are using them with printf. The first parameter is a char*, and then you implicitly have an unlimited number of void* parameters. And if you get the type wrong, they'll only fail at run time.

      Technically printf is a variadic function, not one which takes a void pointer. The functions dealing with direct memory access (memset/cpy etc.) use void pointers obviously, but I can't think of any others off the top of my head. Using void pointers is a choice. Random aside: you can write a completely statically type safe printf using variadic templates.

      Obj-C for example has categories, which allow you to extend the functionality of a library class - even if you don't have the source for it. C++ can't do that. It can only subclass. Which doesn't help if someone else's code is creating the class in the first place.

      C# and Java can do this. Not really sure what you're getting at to be honest...

    15. Re:The reason for its popularity... by Timbo · · Score: 1

      Spoken like someone that has never needed to maintain other people's code.

      This is actually ~80% of my job, for what it's worth.

      You might not write code using these features, but if they're there, you must be able to read and understand them because someone else will use them.

      But I do agree. My point was more than a language shouldn't be discounted because it's perceived to have "too many" features.

    16. Re:The reason for its popularity... by BasilBrush · · Score: 1

      Technically printf is a variadic function, not one which takes a void pointer.

      Different issues. The variable number of parameters can also cause run time errors. But those variable number of parameters are all void*, as I said implicitly.

      Using void pointers is a choice.

      As is using ids.

      C# and Java can do this. Not really sure what you're getting at to be honest...

      It's not complicated. You pointed out a particular thing that you think C++ does better. I pointed out it's not different in that respect and picked out another topic in which Obj-C is better. You can't compare A and B if you only ever look at ways that A is better than B. You can also have to consider ways that B is better than A.

    17. Re:The reason for its popularity... by Timbo · · Score: 1

      Using void pointers is a choice.

      As is using ids.

      If you're prepared to not use the standard library; and that is impractical.

      Anyway... Nazis etc.

    18. Re:The reason for its popularity... by lars_stefan_axelsson · · Score: 1

      My point was more than a language shouldn't be discounted because it's perceived to have "too many" features.

      That I agree with. I'm not a minimalist. As long as we're in agreement that even the features you don't use do have a cost. Even to you.

      --
      Stefan Axelsson
  21. Explaining LOGO is easy by anyGould · · Score: 4, Interesting

    You need to show a bunch of six-year-olds how to program in an hour? Here's LOGO. Here's your turtle. Type FWD 20, watch it move forward. Five minutes later, the kids know all the basic commands. Put a maze in front of them, let them figure it out. Congrats - they're programming with a computer.

    LOGO was my first programming language, back on an Apple II with a big honkin 5 1/4" floppy disk drive. It was the eye-opening "OMG these things do more than Oregon Trail?!?!?" moment.

    1. Re:Explaining LOGO is easy by Anonymous Coward · · Score: 0

      Logo has its roots in Lisp. There's a lot more to it than just REPEAT 5 [ FD 100 RT 144 ] which is the extent to which they usually taught it in elementary schools.

    2. Re:Explaining LOGO is easy by Rubinstien · · Score: 1

      Simple enough even for some four-year-olds. My daughter (now 16) wrote her first program in MicroWorlds LOGO at age 4. It drew a cat. I had her act out what she wanted the turtle to do, using only the things she already knew how to tell the turtle to do. She worked from there.

    3. Re:Explaining LOGO is easy by bob0the0mighty · · Score: 1

      It's also a LISP and was a teaching language at Berkeley. I don't know if it's still used there but the books are online at http://www.cs.berkeley.edu/~bh/v1-toc2.html

  22. Fastest growing... by Anonymous Coward · · Score: 0

    I hate the "fastest growing" statistic...If you only have 2 users and manage to get 2 more you've OMG DOUBLED your users!

  23. Chinese by Tablizer · · Score: 1

    nuf sed

  24. Perl by tirnacopu · · Score: 2

    Love to see it soldiering on. No advertising, no vendor lock-in, no World Wide Whatever Conventions, and yet there's no-one moving it off the top 10. Congratulations, to all the devs and monks.

  25. incorrect characterization of Objective-C by khipu · · Score: 1

    They're strongly and explicitly typed, compilable, memory-safe (mostly), and have garbage collection.

    Objective-C is none of those things: it is dynamically typed, has gaping type holes both in its C and in its OOP interfaces, it isn't "memory safe" (since it has pointers), and it has "automatic reference counting", which isn't the same as garbage collection.

    1. Re:incorrect characterization of Objective-C by dzfoo · · Score: 1

      It is, nonetheless, compilable.

      --
      Carol vs. Ghost
      ...Can you save Christmas?
    2. Re:incorrect characterization of Objective-C by Anonymous Coward · · Score: 0

      Even shell scripts are "compilable", so that's not a meaningful criterion.

  26. Encouraging. by blind+biker · · Score: 3, Interesting

    While I have not been doing any serious coding since quite a while, it's encouraging to see that the four programming language I learned many years ago, are still in this top 20 list, and have not changed position since last year: Java, C, Pascal and.. BASIC :)

    Wait, I forgot one: where's FORTRAN!?

    --
    "The agriculture ministry is not in charge of Gundam" - Japanese ministry official.
    1. Re:Encouraging. by Megane · · Score: 1

      Right there next to COBOL?

      --
      #naabhaprzrag, #sverubfr-000, #agi-fcbafberq, negvpyr[pynff*=' negvpyr-ary-'] { qvfcynl: abar !vzcbegnag; }
  27. How's that any different from C, C++, Cobol, Java? by jmcbain · · Score: 1

    Why does it matter why a programming language is popular?

    Suppose increasingly popular embedded systems require C programming; does that make C growth any less valid?

    Suppose increasingly popular financial systems require Cobol; does that make Cobol growth any less valid?

    Suppose increasingly popular Web browser apps require JavaScript; does that make JavaScript growth any less valid?

  28. It's not about programming language by GauteL · · Score: 3, Insightful

    Your job security and desirability as a programmer is more about domain knowledge than anything else. C++ and engineering knowledge will still carry you much much further than C# and fuck all.

    Seriously, if you know C++ and you're thinking it might be outdated, by all means start looking at more modern languages, but the one thing that will ensure your success is to know more about the field you're working in.

  29. what about.. ? by Anonymous Coward · · Score: 0

    I wonder where CAML figures in this list!?

    1. Re:what about.. ? by dotbot · · Score: 1

      I assumed Ocaml to be 44 ML. Standard ML is listed below at 47, so ML must mean Ocaml.

    2. Re:what about.. ? by dotbot · · Score: 1

      As it's case sensitive, perhaps I should have said "OCaml".

  30. Logo's popularity is easy to explain by Anonymous Coward · · Score: 0

    TIOBE is an astonishingly dumb keyword scraper, and I suspect 99% of the uses of the word "Logo" are probably things like "Logo design" and "Corporate logo".

  31. Don't misinterpret the chart by Anonymous Coward · · Score: 0

    When they say that PHP, Python, etc, all are falling that may not be true. Since this shows percentages . . . Objective C and C# are growing, it doesn't mean that the other languages are actuall declinine in use, but their percent of the 100% Tiobe shows has to drop. They could actually be steady or growing in raw numbers even thought Tiobe shows a drop.

  32. Objective C often means 80% C/C++ by LordZardoz · · Score: 1

    Most game development studios that are supporting iOS tend to use the minimal amount of Objective C required to access the underlying system libraries and features. The rest of the code is either C / C++. This is not only true within my workplace, but it seems to hold true for new hires relating their experience with the Objective C language.

    For programmers used to reading C++ code and languages derived primarily from C, the Objective C syntax is an eyesore that makes figuring out the code at a glance much more difficult. While the language has some very compelling features, the atypical syntax makes using those features more of a chore.

    END COMMUNICATION

  33. Most used. by Doctor+O · · Score: 4, Funny

    Then your were popular in the "most used" sense.

    I feel there's a "your mom" joke hidden somewhere.

    --
    Who is General Failure and why is he reading my hard disk?
    1. Re:Most used. by Anonymous Coward · · Score: 0

      his mom was indeed the most well liked cum dumpster in school, but the most used was his dad's ass

    2. Re:Most used. by Anonymous Coward · · Score: 0

      Your mom felt it too.

    3. Re:Most used. by Anonymous Coward · · Score: 0

      Then your were popular in the "most used" sense.

      I feel there's a "your mom" joke hidden somewhere.

      There's no "your mom" joke hidden here... although last night, I was partly hidden... in your mom.

  34. Java is also "walled garden" ask Oracle by walterbyrd · · Score: 3, Funny

    Oracle will tell you the language is free, then sue you when you use it. Just ask Google.

    1. Re:Java is also "walled garden" ask Oracle by Anonymous Coward · · Score: 0

      Moot point.

      I come from the "old school," where Java, Python, CSS, Ajax, Ruby, and WordPress themes aren't really languages.

  35. PHP by Anonymous Coward · · Score: 0

    PHP has stopped growing so much because it's reached a level where it can't grow exponentially anymore. It's used everywhere. Imagine how many more things that use php it would take for it to be 'the fastest growing' again.

  36. Ya people really underesitmate C/C++ by Sycraft-fu · · Score: 5, Insightful

    As a simple example pretty much every videogame is written in it (C++ usually). On Windows it is almost always Visual C++, in particular because for the 360 that is what you have to use. The PS3 doesn't use VC++, of course, but it does use a C language for processor programming and nVidia's CG for programming the GPU (if you need more fine control than OpenGL ES offers). Go look at any posting for a programmer for a game company, see what language they are asking for.

    Now obvious to anyone who's looked around that games are HUGE. Lots and lots of development going towards videogames. It's a large and profitable market.

    In terms of pure C, that still reigns supreme in the embedded world and man is there a lot of that going on. we have tons of embedded devices, in things you'd never even think of.

    The problem is as you note these guys use the "What are people chattering about," method, as do many people on Slashdot. They think because there's a lot of buzz about something that means it is in heavy use. Not really. There's no buzz about C++ because it is well established, but that doesn't mean it isn't getting used. It means the people using it don't feel the need to go on about it.

    1. Re:Ya people really underesitmate C/C++ by fyngyrz · · Score: 3, Informative

      There's no buzz about C++ because it is well established, but that doesn't mean it isn't getting used. It means the people using it don't feel the need to go on about it.

      ...and that goes double for C -- can't think of the last time I had a C question I couldn't answer without even cracking a reference or prodding Google. I spend my time being productive with it, not talking about it, except I do tend to say something when the wags around here declare it's dead, etc., lol

      --
      I've fallen off your lawn, and I can't get up.
  37. old and unused by Anonymous Coward · · Score: 0

    Surely Modula-2/3 are not used anymore. I used to be a big modulan, but now-a-days I gladly prefer perl and Ruby. Others would prefer Java or python.

    Similarily with Eiffel, except that it was even less popular. This summer I tossed out all my books by Bertrand Meyer.

  38. Learning a second language by tomhath · · Score: 1

    For the past decade the majority of programmers came out of college knowing how to wire together modules in Java, and that's about all they know. What we're seeing now is a huge shift to languages used on mobile devices. Native apps on Android aside, what TIOBE saw this year is an entire generation of programmers trying to learn a second programming language.

    1. Re:Learning a second language by plopez · · Score: 1

      That's sad. I went through a class my sophmore year where they introduced us to three languages, including LISP. It was a weed class but very good for showing you TMTOWTDI.

      --
      putting the 'B' in LGBTQ+
  39. Python, and staying with same by fyngyrz · · Score: 1

    Python had a "Perl 6" experience - von Rossum pushed the language to Python 3, which is only marginally better, no faster, and incompatible. That seems to have hurt the language's market share.

    Knowing full well that the plural of anecdote is not data...

    I write a lot of Python, it's my preferred scripting language. We use 2.x, looked at 3 when it came out, determined it was thoroughly incompatible and that translation and testing of our existing codebase wasn't practical, and proceeded to ignore it completely, no harm done. Now, one relevant point is that we don't generally use a lot of externally written python -- frameworks, etc -- so we don't have to worry about who is migrating, or not, etc.

    What keeps me with Python (aside from familiarity) is the broad functionality available within the basic language distribution itself; the elegance of the language; an appreciation for the indent mechanism (I know others hate it, my point is I like it) and a certain perceived readability that may be the result of a personal quirk more than anything else.

    Also... the more I learn about the functionality that is part of the base 2.x distribution, the more comfy I get with the whole thing.

    The seemingly random mix of I and we in the above is the result of there being a programming team, but I get to make the key decisions. :)

    --
    I've fallen off your lawn, and I can't get up.
  40. R is not a programming language by plopez · · Score: 2

    R is a, very large, library of Mathematical and Statistical libraries usually written in Fortran glued together by a scripting language. Maybe the popularity of R means that Fortran is becoming more popular, via the "back door".

    BTW, check out Fortran '08. OO, fast, native parallel capability[*], supports 30 year old legacy code, and easy to learn. I've been hobbying with it. As the saying goes "It ain't your grandpappy's Fortran".

    [*] Which is mind bending enough I haven't tried it, yet.....

    --
    putting the 'B' in LGBTQ+
    1. Re:R is not a programming language by Anonymous Coward · · Score: 0

      > becoming more popular, via the "back door".

      ...like Joran Van der Sloot, soon.

  41. Issue with this metric too though by SuperKendall · · Score: 4, Insightful

    StackOverflow is a great general purpose site, but was started by two guys VERY heavy into Microsoft and .Net technologies. As such, the C# guys jumped on it en masse, and so they are significantly over-represented here - there were already a lot of sites discussing Java and it takes time to migrate people over.

    Objective-C users really had no other great public forums so StackOverflow quickly became a major hub for Objective-C information.

    --
    "There is more worth loving than we have strength to love." - Brian Jay Stanley
    1. Re:Issue with this metric too though by maple_shaft · · Score: 3, Insightful

      Objective-C users really had no other great public forums so StackOverflow quickly became a major hub for Objective-C information.

      And therein lies one of the main problems, StackOverflow is a Q&A site, not a programming forum. This doesn't help prevent the under educated masses from flooding the site with their *"PLZ TEH CODEZ!"* cancer and letting once active contributing users like me eventually begin to give up.

      I know that this isn't exclusive to Objective-C developers at all, and I don't begrudge them for not having even the most rudimentary of programming skills, I begrudge them because they don't know how to ask a damn question. If I got a dollar for every time some idiot asked what was wrong without posting their code, what they have tried, and what versions of X they are using then I could retire to the Caribbean.

      Like any other bubble right now, iPhone apps will plummet in value and the disgusting amount of money invested in making apps that nobody wants based on horrible ideas will dry up, leaving a large swath of unemployable idiots paying the price. Of course those of us who what the hell we are doing will be fine. It happened after the .com crash, it will again soon with mobile apps.

    2. Re:Issue with this metric too though by BasilBrush · · Score: 0

      Like any other bubble right now, iPhone apps will plummet in value and the disgusting amount of money invested in making apps that nobody wants based on horrible ideas will dry up, leaving a large swath of unemployable idiots paying the price. Of course those of us who what the hell we are doing will be fine. It happened after the .com crash, it will again soon with mobile apps.

      "apps that nobody wants"? That's a strange use of the word "nobody" given that there have been 20 billion downloads from the Apple App Store.

      That's Billion. 20,000,000,000. Count 'em.

      I wish I had a dollar for every prediction that Apple product X is a fad. Even if I had to pay back 10 dollars for every such prediction that was right, I'd still have made a fortune.

      But wait... you're not just predicting the downfall of iPhone apps but all mobile apps. As if somehow, all of a sudden, people will decide that they don't need computing, information or entertainment whilst on the move.

      Let me guess... you're a web developer with sour grapes because your field isn't the big new thing any more.

    3. Re:Issue with this metric too though by Smallpond · · Score: 1

      If I got a dollar for every time some idiot asked what was wrong without posting their code, what they have tried, and what versions of X they are using then I could retire to the Caribbean.

      I am trying to recognize faces in images using jquery but it doesn't work. I need this by tomorrow, please tell me what is wrong.

  42. Include the context folks by recharged95 · · Score: 1

    It would be interesting if they listed in a column the last update for the specific language. Cause development cycles do exist.

    According to wikipedia....

    Java (2011, version 7)
    C (1999, C99)
    C# (2010, .Net4)
    C++ (2007, really 2005, version TR1)
    Obj-C (2007, Xcode)
    PHP (2004, PHP5)

    Really in the end, C is an exception since most OSes and their hardware drivers are written in C. Once you get an OS and device drivers written in a higher level language like C# or Java, you will see C drop off a cliff.

    1. Re:Include the context folks by lophophore · · Score: 1

      You may never see a device driver coded in C# or Java. Not for a physical machine, at least. They run too far from the metal.

      Most **modern** OSes are written in C, though even unix was originally written in assembler. And pretty much every OS has a bootloader, and a fair bit of the library written in assembler. None of this is going to Java or C# (gachhk!). Too inefficient. Too proprietary. Nobody's going there.

      The comments on this thread are unbelievable to me. CS grads that are only fluent in one programming language! Would you like fries with that? Shit.

      By the way, the latest C language standard is C11. As in 2011. Same with C++. 2011.

      --
      there are 3 kinds of people:
      * those who can count
      * those who can't
    2. Re:Include the context folks by atrus · · Score: 1

      I wouldn't call that last update list up to date :) C++ is at C++11 (2011) Objective-C arguably is at a new version due to weak references and ARC (which are a feature of the compiler) (2011). PHP has had updates (for better or for worse)

  43. Logo by Progman3K · · Score: 3, Interesting

    People forget that Logo is not only about the turtle-animation and drawing.

    It is parent to Lisp and has list-processing primitives that make it quite good at processing streams of information.

    Its actually a lot like Java; procedures can dynamically generate procedures as they run.

    Its syntax is so simple, a child can learn it but you can easily program recursive algorithms with it.

    I say all this from experience. My very first programming job, I was an apprentice at a place that did the books and business-accounting of about 30 client companies, all in Logo.

    This Logo was running on a micro and we had 8 terminals hooked up to it. This logo had NO turtle, it was text-only. (M.I.T. Experimental Logo #53 or something like that)

    --
    I don't know the meaning of the word 'don't' - J
  44. Flexibility by SuperKendall · · Score: 1

    Any language that choose to let compile time errors through (because it might work at run time) is fundamentally broken and not suitable for non-toy projects.

    Any language insufficiently flexible to allow this is fundamentally broken and not suitable for large scale projects.

    Seriously though, just because that can happen doesn't mean it becomes a problem. There are very few problems that arise in practice from this flexibility. And the improved static analyzers catch a LOT of potential issues along those lines.

    --
    "There is more worth loving than we have strength to love." - Brian Jay Stanley
  45. "free" by SuperKendall · · Score: 1

    It is when you realize that for every other platform with even a microscopic amount of market-share the price is $0. ;)

    I will keep my "expensive" $99/year development platform over the "free" platform that requires I buy $1k worth of devices every six months for proper testing.

    --
    "There is more worth loving than we have strength to love." - Brian Jay Stanley
  46. Kept up and now surpassed by SuperKendall · · Score: 1

    If they eliminated the need for separate header files (including getting rid of the declaration/implementation divide), added keywords to get rid of the need for the CPP, added autoboxing, and improved runtime errors; it would be a world class language (again).

    I'm not saying those would not be nice but they are not not really an issue.

    While they were not doing those they were working on things like ARC, blocks and Grand Central Dispatch as well as many other areas of the core frameworks (which are to modern languages every bit as important as the core language itself). I know which I would rather have! The only thing I would actually say I still miss and desire to some degree is some kind of namespaces.

    As an aside Cocoa is a wonderful and powerful class library, with one major flaw: needlesslyLongAndOverSpecific method names.

    After working on Obj-C full time for many years now you can pull my veryLongButActuallyDescriptiveMethodNames from my cold, dead fingers. I prefer code that says what it does vs. comments that LIE. Always.

    The lamdbas are nice though...

    Between that and ARC I am not minding the continued need for header files one bit...

    The thing is you are looking at it wrong. It's not that other languages really surpassed Objective-C, its just that it took a very different path. It's like a Steampunk language, full of advances that simply made lots of different choices than the mainstream languages but still ended up with advanced technology that is hard to appreciate until you really get into it.

    Sure the core language may have spent a while seemingly not changing before iOS but all that while Apple was growing a VERY excellent set of frameworks and development tools to complement the language.

    --
    "There is more worth loving than we have strength to love." - Brian Jay Stanley
    1. Re:Kept up and now surpassed by jockm · · Score: 1

      Clearly you are happy with Obj-C as is. I don't think you can make that comment about engineers in general. The need to update declarations, for me at least, means I tend to write longer methods that are harder to read because it is tedious to define another method at the right visibility, and XCode's refactors rarely work (or when they do, they don't do the correct thing) for me. I find myself less likely to subclass or do other good practices. And reading the code of other Obj-C programmers I see the same problems with them.

      I worked in Obj-C in the late 80s and early 90s, and came back to it periodically since OSX came about. What I see is a lot of people writing code as they did in the 80s and 90s, ignoring the best practices we learned in the intervening decades. The apps may be good, but the code is nowhere near as good as it should be.

      XCode — compared to IntelliJ, Netbeans, Eclipse, or VisualStudio — is merely OK as an IDE. InterfaceBuilder being the only shining star.

      I am sorry it is a myth to assume that brevity is the enemy of clarity, or that verbosity is its friend. Exactly how is getAt: less clear than objextAtIndex:. To be absurd I could point out that that method name makes many assumptions about how the object should be retrieved, what kind of collection it is, etc that could also be spelled out. But no one assumes they should be, so why is the "object" part of that name needed.

      Names should be clear and as long as they need to be, needless specificity is not an aid to understanding.

      But most importantly, there is nothing in your arguments to say why Obj-C should not be better, why we need header files, why the language should have remained so static for so long. The fact that one can get by doesn't mean that we shouldn't all advocate for better tools. There are languages I like far far better but Obj-C but I don't pretend they are somehow perfect or without need for improvement. Craftsmen should always be striving to do better and make better things

      --

      What do you know I wrote a novel
    2. Re:Kept up and now surpassed by SuperKendall · · Score: 1

      Clearly you are happy with Obj-C as is.

      I'm not going to quote your whole post, because this fundamental assumption is not right.

      I am not happy with any language (and I have worked with production applications in several) as is.

      I am merely saying that of all the things Apple could have worked on (and let's face it, for a long time they have been the only ones seriously pushing ObjC forward) the things they did actually work on are more important than the changes you listed.

      I even said in my original post I would like the changes you mentioned. But again, I feel Apple has done a reasonable job in picking which things to work on to keep the language modern and current, and that it is as important with modern languages to recognize work done in system libraries and support as it is core language features.

      Lastly, to me objectAtIndex: vs. getAt: is a non-starter as an issue - thanks to code completion both take the same number of keystrokes to write, and to me do not really affect my reading of code. And of course if you felt such a thing were vital - Categories!

      One thing you mentioned I absolutely agree with though, the refactoring tools are very weak. Before any of the things you listed are worked on I would like to see refactoring greatly improved, which Apple is in a good position to do now with LLVM as a base to make choices on... I am really surprised a third party has not filled that gap with as many iOS developers as we have now.

      --
      "There is more worth loving than we have strength to love." - Brian Jay Stanley
  47. Cruise ship aground - nude girls swimming ashore by flyingfsck · · Score: 0, Troll

    A cruise ship ran aground off Italy: http://www.bbc.co.uk/news/world-europe-16558910 OK, I had to add something to the subject to spice it up, else no-one will click it.

    --
    Excuse me, but please get off my Pennisetum Clandestinum, eh!
  48. Only one? by Anonymous Coward · · Score: 0

    Considering what you can do in c it is not strongly typed either as you can just tell the compiler to cast the type to something completely unrelated and it will do so happily.

    However all these languages support compile time variable types which helps to reduce the number of runtime errors. Of course you are free to exclusively use id for Objective-C, void* for c or Object for C# and java just don't complain about type errors in the production system.

  49. Java #1 by Anonymous Coward · · Score: 0

    $99 isn't all. You also have to buy a mac. The 30% fief at the App store hurts too. iOS == GITMO as far as I'm concerned. I have no desire to go there.

  50. Hurray for domain knowledge by guided_by_coffee · · Score: 0

    Your job security and desirability as a programmer is more about domain knowledge than anything else. C++ and engineering knowledge will still carry you much much further than C# and fuck all.

    Very well said, couldn't agree more.

  51. Indeed by krischik · · Score: 1

    Incidentally, this also applies to just about every language on the list other than C.

    C++ and Ada have ISO standards as well. That makes 3 out of 20 (Pascals ISO standard expired) so I guess you are right.

  52. between 20 to 30 by krischik · · Score: 1

    To lazy to look up the exact place but last I saw Fortran it was between 20 and 30.

  53. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  54. ColdFusion by aclarke · · Score: 1

    Just to show my own little pet peeve with TIOBE, it does a terrible job of handling ColdFusion. It looks for "CFML", which basically nobody uses when describing the language. Stackoverflow.com doesn't even have a CFML tag. However, if you add up the ColdFusion-related tags, you get:

    Unanswered: 417 / 3,712 = 11.23%

    TIOBE puts Lisp as #13, but "CFML" as somewhere between 51 and 100. If you go strictly by Stackoverflow.com questions (which I don't recommend either), ColdFusion is more than twice as popular as Lisp.