This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # aleph (11)
- # arachne (7)
- # aws (1)
- # bangalore-clj (4)
- # beginners (24)
- # boot (128)
- # bristol-clojurians (23)
- # cider (1)
- # cljs-dev (43)
- # cljsrn (6)
- # clojure (178)
- # clojure-austin (3)
- # clojure-chicago (1)
- # clojure-dusseldorf (14)
- # clojure-finland (15)
- # clojure-france (6)
- # clojure-italy (18)
- # clojure-portugal (2)
- # clojure-russia (67)
- # clojure-spec (148)
- # clojure-uk (55)
- # clojurescript (199)
- # core-async (4)
- # cursive (18)
- # datascript (5)
- # datomic (120)
- # devcards (3)
- # dirac (53)
- # emacs (11)
- # events (3)
- # gsoc (7)
- # jobs (1)
- # lein-figwheel (25)
- # leiningen (5)
- # lumo (12)
- # off-topic (29)
- # om (174)
- # om-next (2)
- # onyx (7)
- # perun (10)
- # protorepl (6)
- # re-frame (12)
- # remote-jobs (1)
- # ring (19)
- # ring-swagger (25)
- # rum (6)
- # spacemacs (13)
- # sql (3)
- # untangled (88)
- # yada (7)
@richiardiandrea : I feel guilty about the fact I'm not even paying you for support contract. // Github needs to implement this feature.
I would actually be okay if, every time my boot project pulls a dependency, it pays the dev team behind the dependency $1.00 in dogecoin or something.
or maybe not every pull (since it's automatic), but something like "boot -pay-all-the-devs-because-my-code-just-did-something-awesome-and-I'm-in-a-really-good-mood"
A boot task that pays you some small amount every time it pulls a new dep is cool
the tech is theoretically all there; we just need every dependency to attach a bitcoin address to it
FYI I'm running all the latest versions, but I'm on Linux, and while Dirac indicates it connected successfully, the developer console is blank.
Here are two related errors adjacent in the logs:
Some more log digging inside Chromium reveal the following messages:
at Object.Protocol.InspectorBackendExtensionMode.loadFromExtensionIfNeeded (inspector.js:4597)
this won’t work, you have to stick with the bleeding edge: https://github.com/binaryage/dirac/blob/master/docs/faq.md#why-should-i-use-recent-chrome-canary-with-dirac-devtools
my travis builds run on ubuntu and test against:
Google Chrome: 58.0.3007.0 (Developer Build) (64-bit)
Ah, OK, that's nice to know. There is a dev package in Arch too. I better test it with that, then.
also dirac releases contain direct links to precompiled likely-compatible linux versions, see Rolling DevTools sections: https://github.com/binaryage/dirac/releases
Oh, thanks, that's nice too. It's kind of interesting (and a bit crazy) to keep up with the changes. For you it must be even more annoying to have these APIs constantly changing, no?
well, the devtools activity has beeb quite busy and there are no signs of a slowdown, but I hope protocol changes will be less frequent because now they commit to support node.js as well, which forces them to maintain more stable api between the frontend (UI) and backend (debugger)  https://github.com/binaryage/dirac/commits/devtools
Interesting. Out of curiosity, what's your view on weasel + piggieback? Is it a good foundation? Are they evolving too?
for me piggieback is so “clever” to the level it is incomprehensible for me, nREPL also adds a lot of complexity, but it is flexible
I did a brain dump here: https://github.com/binaryage/dirac/blob/master/docs/about-repls.md#piggieback--weasel
all these tools and libraries have place and were super-important in the early days at least
You're the man. Fantastic document. @cemerick used to write some early foundational clojurescript, he's a great guy but not always easy to follow, I remember struggling with piggieback.
Sometimes I wonder if at some stage someone will decide to rewrite those foundations because that person thinks he can improve on it. If it makes sense, if it's worth it, maybe someone will do that.
I think there is inherent complexity in the task of building a full-featured ClojureScript REPL. A rewrite could make individual parts more understandable from REPL developer’s point of view, but not much better from end-user’s point of view. So it not worth it IMO.
I get that. It makes sense, and probably it's the reason nobody made the foolish attempt. Self-hosted Clojurescript is full of promises in terms of simpler tooling, but that's theory at this point I guess.
in general I think good amount of tooling should be part of core development so that it is built on solid foundations and provides best user/developer-experience possible, but I think we don’t have man power for that right now, a single person (dnolen) cannot possibly handle everything, so he lets community to figure out more high-level tooling, like figwheel
Still trying to figure out why I see "Please install Dirac Runtime into your app and enable the :repl feature" despite running the (cljs-devtools) and (dirac) tasks in my boot pipleline.