Get the basics of LISP and read the core paper on the language regarding it. www-formal.stanford.edu/jmc/recursive.pdf Especially pages 19/20. Those two pages describe the entire language in and of itself (Apply/Eval). The power of lisp comes that it can be described by itself rather shortly - code is data and data is code, and that can have some cool results.
Practically, some LISP dialects like Clojure are cool, I wouldn’t waste too much time in it unless you’ve got a special interest. I’d say the core strength of LISP is meta exploratory programming and quick compiler implementations (with use of LLVM if that fancies you). But yeah, if you don’t need a rapid compiler, don’t get intense into it.
On the other hand, if you wanna know pure functional programming, learn Haskell well - it’ll make you a better programmer. I agree with That dynamic languages can be fucking shit as good practice is 10x more important and spaghetti code can easily happen and knowing what things should be can become difficult.
Andrew Walker
you're just one of those kids who write 2-hour task in shitty outdated dialect in a span of year, and then shitpost about it on Jow Forums for the rest of their life. there's a good reason no one uses dyntyped languages unironically(except brainlets like you obviously. could we blame you for getting trolled into it? you're incapable of knowing any better)
I was having sooooo many fucking problems setting up the environment for building it. Is everything for F# installed through Nuget? I least F# has to offer but getting it to work has been silly for me.
Caleb Long
>it won't take you much time unless you're a retard. Herein lies the problem
Should I attempt to learn Lisp, or should I just stay away from something so complicated should I do something stupid
>That dynamic languages can be fucking shit as good practice is 10x more important and spaghetti code can easily happen and knowing what things should be can become difficult. Saying Lisp is shit because it's dynamically typed is like saying C is shit because it's memory unsafe. Any modern CL implementation will bitch at you for doing weird things with types, it's not like webshit languages where anything goes.
Jordan Ross
>there's a good reason no one uses dyntyped languages unironically Most dynamic languages are shit, but this is still a colossally retarded statement. Writing fizz buzz in Rust doesn't make you productive either. If you're retarded, try Go instead.
Joshua Perry
i woudn't know, i dropped it after doing helloworld in vscode and just went back to rust, since f# won't be implementing hkt anyways.
I haven’t played with CL that much, so I wasn’t aware of its compiler yelling at you. In that case, it sounds much more reasonable. I suppose my fears of Python are rubbing out on other things.
But yeah, I’d say the main concern is the lack of good documentation, along with the lack of major use in industry (therefore it’s not forced to update). Good and bad I suppose, but isn’t good if you want to be a professional LISPer.
Julian Bell
It’s a shame. It’s more user friendly than Haskell and I could prototype stuff pretty fast. I’ve never used Rust, how would you compare it to other languages?
