Do never ever use Google trends to compare programming languages. The names of programming languages have different meanings in different contexts.
Java is the COBOL of my generation and Go is its successor
31–40 of 96 posts
Re: Java is the COBOL of my generation and Go is its successor
#32"My prediction is much stronger than saying Go will be as popular as Ruby, Python, or Node."
Was anybody else thrown off by this? I thought it was weird to throw Node in there considering Go, Ruby, and Python are languages.
Re: Java is the COBOL of my generation and Go is its successor
#33Sigh. We're still banging rocks together and amazed when occasionally there is a spark? Look, Ruby and Python -- their implementations just plain suck. There, I said it. MRI and CPython are just a pile of crap. We've known since 1991-ish (see Self) how to make performant runtimes for dynamic languages and 23 years later Ruby and Python still have crappy slow interpreters with no useful concurrency support. Note that…
Exactly how I feel. I don't even want to bother with languages that don't have algebraic data types and exhaustive pattern matching.
Re: Java is the COBOL of my generation and Go is its successor
#34"My prediction is much stronger than saying Go will be as popular as Ruby, Python, or Node." Was anybody else thrown off by this? I thought it was weird to throw Node in there considering Go, Ruby, and Python are languages.
Most people say Node as to not confuse client-side JavaScript. e.g: Saying Go will be as popular as JavaScript would be unreasonable, saying Go will be as popular as JavaScript on the server is reasonable.
Re: Java is the COBOL of my generation and Go is its successor
#35Sigh. We're still banging rocks together and amazed when occasionally there is a spark? Look, Ruby and Python -- their implementations just plain suck. There, I said it. MRI and CPython are just a pile of crap. We've known since 1991-ish (see Self) how to make performant runtimes for dynamic languages and 23 years later Ruby and Python still have crappy slow interpreters with no useful concurrency support. Note that…
I think you're missing the point of the basic type system: simplicity. It's a bigger win than you think when it comes to attracting new developers and making code easier to read. Sure, there are languages that let you write more succinct code and support all sorts of crazy typing, but one of the things good code requires is readability. Your code my be terse and elegant, but if other people can't understand it, it wo…
Either the language is complex or the application code is. Which one would you prefer to keep simple?
Re: Java is the COBOL of my generation and Go is its successor
#36Sigh. We're still banging rocks together and amazed when occasionally there is a spark? Look, Ruby and Python -- their implementations just plain suck. There, I said it. MRI and CPython are just a pile of crap. We've known since 1991-ish (see Self) how to make performant runtimes for dynamic languages and 23 years later Ruby and Python still have crappy slow interpreters with no useful concurrency support. Note that…
What language created in the last 5 years has a feature that wasn't originally discovered in the 80s or earlier? It's all too easy to bash new languages for not having some hot new, never before seen feature, meanwhile there are almost no examples of new languages doing earth shattering things.
I think what we're currently seeing with Go, Rust, Elixir and others is taking the features that are perceived as good as trying to combine them in different ways.
Re: Java is the COBOL of my generation and Go is its successor
#37Troll much?
Re: Java is the COBOL of my generation and Go is its successor
#38"My prediction is much stronger than saying Go will be as popular as Ruby, Python, or Node." Was anybody else thrown off by this? I thought it was weird to throw Node in there considering Go, Ruby, and Python are languages.
I think it fits in this context.
JavaScript alone has no standard library or execution environment. Unlike the other languages listed there.
Re: Java is the COBOL of my generation and Go is its successor
#39Sigh. We're still banging rocks together and amazed when occasionally there is a spark? Look, Ruby and Python -- their implementations just plain suck. There, I said it. MRI and CPython are just a pile of crap. We've known since 1991-ish (see Self) how to make performant runtimes for dynamic languages and 23 years later Ruby and Python still have crappy slow interpreters with no useful concurrency support. Note that…
[deleted]
Re: Java is the COBOL of my generation and Go is its successor
#40Earlier quoted context omitted.
Totally agree that the JVM is super powerful. I think it's Java's greatest strength. However, I don't see any current JVM language as a potential replacement. Scala is too complex. Clojure, while wonderful, is Lisp and no one has been able to make that popular for 5 decades (not even pg).
What about Groovy?
[deleted]