Go: C does not have garbage collection.
What languages fix
11–20 of 91 posts
Re: What languages fix
#12Haskell: Programmers aren't disciplined enough to to isolate side effects by themselves.
Re: What languages fix
#13This list hints at something interesting:
The intent behind the creation of a programming language does not always match up with the result, or the culture around it.
For example, you might say;
Lua: SOL (our data language) doesn't have enough programming constructs.
which is historically accurate, but in a modern context you might also say:
Lua: Game engines and other apps need a really easy to integrate, reusable embeddable scripting language library.
which is a vastly different problem that lua didn't necessarily set out to solve.
Re: What languages fix
#14Would be helpful to see this list be updated with a few others. A couple of that come to mind: SQL: Tuple relational calculus is too low level? Julia: Hadoop is a kludge for data science? Clojure: We need Lisp for the JVM? Dart: JavaScript is a kludge? Go: C/C++ are kludges for systems programming?
Can you explain what is the relation between Julia and Hadoop?
Re: What languages fix
#15Haskell: other languages make making mistakes too easy.
This article came up about a year ago[1], so I'm just reusing my comment :P. Now I'd also add:
Go: C is the prefect language, except it's too low-level.
Ermine[2]: Scala is not functional (enough).
Re: What languages fix
#16I would dispute the description of Python, at least as an 'origin story'. The actual impetus was 'ABC doesn't have libraries or exceptions': http://docs.python.org/2/faq/general#why-was-python-created-...
If we're going for why Python appealed to its early adopters as opposed to the actual motivations for creating it in the first place, something more like 'other languages are all hard to read' would be fair. You could even reintroduce the Perl rivalry in the form 'Perl is too hard to read', if you insist. But it really wasn't Perl's kludgeyness per-se.
Re: What languages fix
#17Would be helpful to see this list be updated with a few others. A couple of that come to mind: SQL: Tuple relational calculus is too low level? Julia: Hadoop is a kludge for data science? Clojure: We need Lisp for the JVM? Dart: JavaScript is a kludge? Go: C/C++ are kludges for systems programming?
Go: C is too low-level, C++ is too complicated, and neither is adequate for concurrency. (That's an attempt at summarizing Rob Pike and fitting it into Graham's framework, not necessarily what I believe, although I believe something close).
A sane module system was a big part of it, according to the SPLASH talk.
Re: What languages fix
#18pg: php?
Re: What languages fix
#19Rust: Other languages have boundary issues -- action-at-a-distance is evil.
Re: What languages fix
#20APL: Errors increase in proportion to the amount of code typed; therefore, decrease amount of code typed while keeping expressiveness and power unchanged.
Alternatively:
APL: Programming should be more like math.