clojure-dev 2017-06-25 | Slack Archive

matan18:06:37

Mmmm actually this makes me more pessimistic rather than optimistic. If a team spent more than a year on it, either they've focused on the wrong areas, or there's challenge areas which are inherent to this ambition, or rather the way clojure is written. I'll watch the video through.

jeff.terrell12:06:49

matan: I think part of the challenge of that approach is that they forked Clojure itself. I suspect some of those improvements might be difficult to get accepted upstream. I'm wondering if a Leiningen or boot plugin might be a better place to start from with more potential for gaining inertia.

matan21:06:25

@U056QFNM5 actually they also mentioned a leiningen plugin somewhere, but I think they didn't get very far, I might be wrong here of course.

matan21:06:54

I guess a lein plugin can catch any exceptions and be used for "after the fact exception embellishment and replacement strategy" ― as much as such a strategy can get very far ― as there are at least three areas of challenge in making exceptions a better source for developer productivity

jeff.terrell21:06:46

What are the three you're thinking of? Just curious.

matan19:06:18

I'm surprised at the techniques employed as part of that effort ― nothing very intelligent from formal language theory or program analysis was used.

2017-06-25

Channels