News for hackers. Stuff that matters.

A comment on Lisping at JPL (2002). Parent comment

Re:Lisping at JPL (2002) by bgorman on Saturday January 18, 2020 @05:26PM (#22087760)
Why not Clojurescript? It has access to the whole JS ecosystem.
[ Parent | on HN ]
Re:Lisping at JPL (2002) by abraxas on Saturday January 18, 2020 @11:28PM (#22089474)
It feels like the Clojure community is kind of withering. Or maybe it's just perpetually stuck in the Lisp niche.
[ Parent | on HN ]
Re:Lisping at JPL (2002) by fulafel on Sunday January 19, 2020 @04:34AM (#22090409)
Interesting observation... not sure I get that from the Clojure community or from looking around.

Last year Clojure made it to #1 (2019), improving from #3 (2018) in the SO salary cahrts.

(https://insights.stackoverflow.com/survey/2019#top-paying-te... vs https://insights.stackoverflow.com/survey/2018#top-paying-te...)

[ Parent | on HN ]
Re:Lisping at JPL (2002) by scythe on Saturday January 18, 2020 @07:38PM (#22088524)
I've been teaching myself Clojurescript for the past three months, and while this might, in theory, be a good idea someday, the state of the Clojurescript tooling and learning materials I've used means that it is certainly not a good idea today.
[ Parent | on HN ]
Re:Lisping at JPL (2002) by Scarbutt on Saturday January 18, 2020 @05:36PM (#22087833)
Too much friction and incidental complexity for a kid, they will have to be familiar with JS anyway.
[ Parent | on HN ]
Re:Lisping at JPL (2002) by Oreb on Saturday January 18, 2020 @05:50PM (#22087941)
Why? Even as a professional developer, it’s extremely unusual that my cljs work requires any JS familiarity. I don’t see why a complete beginner would even need to know that JS exists.
[ Parent | on HN ]