3 ms·
When I was younger, I imagined there would come along a true language that would solve my problems. It took me a long time (and a lot of banging my head into b
by shadowgovt 7y ago
When I was younger, I imagined there would come along a true language that would solve my problems.
It took me a long time (and a lot of banging my head into bad environments) to realize that language matters a lot less when the IDE is well-configured and fluent with what I want to do, the toolchain allows for experimentation without ruining the ability to do large, collaborative work, and both debugging and profiling are possible. And those are things you can't really add to a language environment when the language itself (spec and implementation) is constantly in flux.
Maybe a language will appear one day that renders all those tools obsolete, but we still evaluate and run code on real machines and it's still written by human beings so I sincerely doubt it.
- hderms 7y agoThis is why I personally prefer Scala to Haskell
- leshow 7y agoA language is a tool that was built to solve some kind of problem, but no language is built to be the best at all problems. There are pros and cons to using it depending on the task just like anything else. You have to consider what you want to do and pick and language that aligns with your goals.
- slifin 7y agoClojure is good for this because it's a parasitic language it sits on top of and interops with JavaScript, Java, .NET, Erlang and their ecosystems, npm, maven etc Learn the main language once and you get incredible reach, for every new runtime the core language is practically the same
- iLemming 7y ago> when the language itself (spec and implementation) is constantly in flux. Common Lisp and Clojure are legendary for their stability. So many times I have experienced it myself - I would pick up a 5-6 year old Clojure project, update a bunch of dependencies, and somehow most things work right off the bat. That trick never worked for me with pretty much any other language - C#, Java, Python, Ruby, Go, Lua, Javascript - you name it. Why is that? Probably because Lisp dialects essentially have no syntax. Code is data and data is code.
- deleted 7y ago[deleted]
- lispm 7y agoI thought Common Lisp is stable because the standard is unchanged since its publication in 1994. Lisp dialects have a lot of syntax. Every macro implements syntax.
- iLemming 7y agoMacros don't get written very often. Some Lispers (e.g.: Clojurists) advocate against solving problems with macros (if they can be solved with regular functions). However, at the end of the day, macro or a function - data remains data. In non-lispy languages syntax often complects meaning and order.
- lispm 7y ago> Macros don't get written very often. It's not how often you write macros. Just write ten macros -> ten syntax extensions. The Common Lisp implementation I use has around 700 predefined external macros. > against solving problems with macros (if they can be solved with regular functions). It's just that macros are for different things and for those are widely used in Lisp.