4 ms·
I like Javascript. As a language. It's fun, enjoyable, and I'm productive in it. There I said it. I don't mind exploring interesting avenues like immutability,
by marcus_holmes 9y ago
I like Javascript. As a language. It's fun, enjoyable, and I'm productive in it. There I said it.
I don't mind exploring interesting avenues like immutability, jsx, typescript, declarative or functional styles. I like that JS has enough flexibility to make all of these possible.
I get the fatigue about the endless stream of new frameworks, libraries, approaches, and "new hotness". But I became much more relaxed about it all when I realised it's all completely optional. I can just stick with vanilla JS if I want to, and cherry-pick interesting things as they whizz by. It's the sushi train of programming environments :)
LISP in JS sounds great, I might give it a try. But this does raise a conundrum... if LISP is the ultimate programming language because you can write all the others in LISP, then the fact that this is a LISP written in JS makes it...what?
- keymone 9y agounfortunately this approach does not scale past single developer or multiple klocs of code unless you're really disciplined, but then wouldn't that cognitive effort be better spent elsewhere?
- marcus_holmes 9y agoI get the impression that the OP wasn't talking about a team environment either? I could be wrong...
- seangrogg 9y agoI've seen multiple klocks of code written in Java and C that are taking minutes to handle database operations, unable to process parallel network requests, and choking on errors. Watching new features get added is exciting in the same way it's ensorcelling to watch someone assemble a house of cards. I'd love a tool that enabled me to spend my cognitive currency how I want to, but so far all I've found are tools that have disguised their expenses in new and interesting ways, like tranches of a collateralized debt obligation.
- keymone 9y agoi don't think i disagree with you and (i think) neither does the author. argument (as i understand it) is that rather than piling on features that don't really fit and have complex interference you could use a better tool.
- tempodox 9y agoI think this is one of the most sensible questions to ask wrt. JS (except where you have no choice but to use it).
- ben-schaaf 9y agoLISP isn't the ultimate programming language because you can write all others in it. You can write any Turing-complete language in any other.
- marcus_holmes 9y agoTrue, you can write a language parser in any other language. That's not what I meant. I may have not been clear enough.
- tasuki 9y agoWhat did you mean?
- yomly 9y agoIf I had to guess: that macros in LISP are natural, owing to the fact that its syntax are all s-exps which make it parsing it easier than in other languages?
- marcus_holmes 9y agoI had to go down a small rabbit hole of my own ignorance here. My initial thought was that since JS is the target environment for a LISP compiler, it would necessarily have to be more flexible and "powerful" (whatever that means). With a bit more thought I realised that that's not the case. Thanks for the prompt to look into this more, and learn :)
- holydude 9y agoWhen you say you like JS as a language what do you mean ? ES5 or ES6 or ES7 or transpiling ?
- marcus_holmes 9y agoThey're the same language. It's incremental additions without breaking backward compatibility. This isn't Python we're talking about here ;)
- holydude 9y agoI know that they are the "same" language. But having to maintain transpiled ES5 legacy app kills the joy for me.
- darkkindness 9y agoYou are right, it is great that there are endless options and styles to choose. A good chunk of the work is already done for probably every project imaginable! It's nice, especially for personal projects. And for multiple developers, well, at that point it's just a nice exercise in working with others to decide which framework(s) to use :) Yes, in some environments you don't get to choose, but why blame the language for that?
- kronos29296 9y agoA Lisp is a good lightweight way of expressing things. You can write a Lisp with any language. The main plus of a Lisp is that you are not burdened by Syntax and boilerplate. You can use Metaprogramming in an unconstrained way. We have Lisps written in most popular languages. Python has Hy (newest Lisp on the block), Java has Clojure (currently the most popular one), Erlang has LFE (For BEAM just like Clojure is for JVM), Most scheme (kinda like lightweight lisp with a 100 variants) interpreters are in C. What does that make them? Nothing more than what they already are. What makes Lisp a Lisp is Functional Programming and Syntax where the program itself is treated as Data (Very good for easy macros that transform like a Transformer) and S-Expressions (Every thing is an S-Expression). Not because you can write all others in Lisp.