What type of shortcomings? Can you provide some examples?
(The question is coming from someone who wrote a Scheme interpreter in the past, but have been using Python for the last 8 years and haven't touched Lisp in long time).
They are not lisps :)
> What if you need performance
Choose a lisp that gives you performance. Clojure gets you about 80% on the way there, for the rest you can use Common Lisp if you really require performance. I've found that Clojure usually does the trick if you optimize it a bit.
> Or even a community at all
Clojure does have a community, not sure what you mean? There are forums, chats, Q&A sites, blogs, people on Twitter.
> libraries and support?
Plenty of battle-tested libraries with stable APIs, and loads of companies that offer Clojure support (not to mention the great public community that can also help with most if not all questions).
Have you actually used Clojure in any capacity? These points seems to be coming from someone who haven't actually tried to get involved.
As long as it's s-expressions and interactive development oriented, I'm probably fine with it.
But for the last 4-5 years, I have literally not found a single use case where I'm forced to use C++ or Rust since multiple other (lisp-like) languages has the same target market and the ergonomics are just so much better.
I use C++ to write realtime audio processing applications, especially DAW plug-ins. This is hardly C++'s primary market, but AFAIK there are no lisp-like langauges that can compete with C++ here. I'd be happy to learn something new if this isn't the case!
It would help if you outlined what's missing from for example Common Lisp in order for it to compete with C++, then maybe I'll be able to give more helpful suggestions that will help you.
This is why managed languages like Lisps are rarely (if ever) used for the DSP in audio applications. I am an audio programmer who loves all things lispy, so believe me, I wish this weren't the case.
Linux is written in C, and, perhaps someday, Rust.
Linus doesn't like C++ and has explicitly objected to, among other things, its enthusiasm for implicit allocation. Rust's implicit allocation all lives in libraries and so the Rust for Linux project ripped that out.
All of this without even getting into Rob Pike (the man largely responsible for its origin, if you're not familiar) saying explicitly it was for people who weren't capable of understanding a better language:
«The key point here is our programmers are Googlers, they’re not researchers. They’re typically, fairly young, fresh out of school, probably learned Java, maybe learned C or C++, probably learned Python. They’re not capable of understanding a brilliant language but we want to use them to build good software. So, the language that we give them has to be easy for them to understand and easy to adopt.»
Rob Pike, 2014.
Go is a fine language, but let's not pretend, here. Rob Pike certainly doesn't.
As a C# developer, I get to deal with a lot more:
- Bikeshedding over LINQ
- Going back and optimizing LINQ
- Helping Developers understand someone else's LINQ, Reflection/Attribute Abuse
- Helping developers understand new syntax in each version of the language.
A large part of Go's philosophy is to more or less take away all of those tools from the Developer and try to force a style of code that is somewhat monotonous, verbose (in a way very different from Java), yet 'readable' by a developer with minimal experience.
The same is more or less true of Go. Abstractions can be bad, but in the majority of cases it is the only tool we have against complexity, and a method with an annotation may be thousands time more readable/understandable than the reimplementation of a given identical functionality for the thousands time.
Go is inferior (to me) because it doesn't have s-expressions, and it doesn't offer interactive development (who in the world wants to re-compile/re-run a whole program/tests on each change?).
Once you've got the taste for interactive development it's really hard to go back to anything else. Ask any Smalltalk developer what they think of other languages.
So my move.
1. Common Lisp (well obviously) 2. Racket (gotta make some noise) 3. Haskell (controversial, I know) 4. Rust (trendy and deservedly) 5. APL (terseness) 6. Prolog (made me think differently) 7. Fortran (come a long way) 8. Forth (brevity) 9. Ada (correctness) 10. Lean (I really like Lean) . . C . . C++ . . Python . Perl . Shell . . ECMAscript
Is there anyone I haven't offended? Do let me know :)
"A Critical Analysis of String APIs: the Case of Pharo" https://hal.inria.fr/hal-01651250/document
----
For CRUD stuff, PHP & Notepad will probably be OK.
For other stuff, local type inference does make a difference.
So does the widespread availability of free-as-in-beer source code libraries.
For example, the reason I like lisps is because they usually offer interactive development, something most non-lisps don't offer. That makes any non-lisps inferior to me.
For the future, you could do with less snark. I never said what I think is objective, and I'm pretty sure most of us know that what languages you like is very much subjective. The sarcasm in your comment just make this thread less interesting, not more.
You didn’t write that though, so I get how some could misunderstand you here.
> Do people decide to go to work for a company based on the language they'll be working in?
So it's expected that the responses will be highly subjective, since the subject itself ("which language you prefer to work with?") is very subjective. Then people write about their experiences which is again, subjective.
Or, I misunderstood the entire point of this thread, and if so, I'm sorry.
Just like I'm sure many people would reject jobs that would force you to write assembly code now when we have higher abstraction languages, I reject jobs that are requiring me to work with inferior languages and ecosystems like Rust, Go or JavaScript. It's simply not worth the frustration anymore.
In the beginning of my career I didn't have the flexibility to choose what languages to work with though, but nowadays I am that lucky.