3 ms·
Is the clojure user experience still a JVM stack trace on anything going wrong? As a non-JVM developer that was extremely off-putting. I never quite bought int
by JonChesterfield 4y ago
Is the clojure user experience still a JVM stack trace on anything going wrong? As a non-JVM developer that was extremely off-putting.
I never quite bought into the atoms/transactions concurrency model, but probably wouldn't have looked so closely at hashed tries if they weren't clojure's choices and those have brought me a lot of joy.
- tnisonoff 4y agostack traces have been much better over the past few years
- beders 4y agoYou can alternatively look at Node stack traces, C# stack traces or Dart stack traces nowadays ;) But, agreed, it has gotten better.
- silcoon 4y agoI became a Clojure developer in the last year and a half without any prior experience with the JVM. The stack-trace problem is rarely an issue, with time I just got better to read the code, with Clojure as with any other language.
- KingMob 4y agoThe Clojure concurrency model was the then-fashionable STM, which has largely not panned out anywhere. Luckily, atoms (based on a simple CAS) meet 99.9% of use cases.
- slowmovintarget 4y agoClojure also adopted the Go concurrency model with core.async adding channels to the language.
- KingMob 4y agoVery true. I was just replying to OP's bit about atoms/transactions.