Why I Switched from Python to Clojure (2016)

Re:Why I Switched from Python to Clojure (2016) by fiddlerwoaroof on Sunday March 24, 2019 @07:24PM (#19479341)

I had lots of pain dealing with CLJS but, since switching to http://shadow-cljs.org as my compiler, I've generally found that things "just work": instead of complicated messing with externs, you just npm install the package and then add `["vega" :as vega]` to your namespace's list of requires.

As far as the stack traces go, I have a hard time understanding why tooling like Cider's stacktrace filtering isn't wider spread: in Cider, when a stack trace pops up, it's one or two clicks to hide most of the things I don't care about and, yet, that information is still available for people working on the compiler or with Java interop.

[ Parent | on HN ]

Re:Why I Switched from Python to Clojure (2016) by thom on Sunday March 24, 2019 @08:45PM (#19479587)

Thanks for this, shadow-cljs looks very promising.

In terms of stack traces, it's not just the location in your code that you care about, it's the nature of the error. In lieu of spec being ubiquitous or anybody really checking their arguments ever, you're still left looking at 20 lines of stack beyond your own code to realise you've passed the incorrect type or structure somewhere. And even with spec you need additional libraries to actually yield human error messages in a lot of cases.

[ Parent | on HN ]