3 ms·

Given how much COBOL is still in production, I suppose it depends entirely on your definition of "dominant" ?

• renox 6y ago
  Given that if you are starting a new project now, you'd almost never even consider using Cobol, that would be a very weird definition of 'dominant'..
  • bird_monster 6y ago
    To me, dominant is defined by lines of code currently in production. The difference between my example vs. what you defined, is that hype and/or popularity determine what people use for _new_ projects. But that doesn't really assess how dominant a language has been in the past (or even in production currently). Java is another dominant language that you might not use for a new project. Same with C.
    • tatersolid 6y ago
      > To me, dominant is defined by lines of code currently in production. That definition biases towards verbose languages with lots of headers and boilerplate code (e.g. C++, Java)
    • renox 6y ago
      > Java is another dominant language that you might not use for a new project. Same with C I would very much consider using Java for a new project, same with C(1) if the project is in "real time" (I think that C++ hides too much things under the rug which can create latency issue). 1: Zig isn't ready yet to be a replacement