This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # admin-announcements (2)
- # beginners (53)
- # boot (151)
- # cider (11)
- # cljs-dev (60)
- # cljsrn (36)
- # clojure (71)
- # clojure-austin (13)
- # clojure-berlin (2)
- # clojure-czech (11)
- # clojure-dev (35)
- # clojure-dusseldorf (2)
- # clojure-france (6)
- # clojure-japan (9)
- # clojure-russia (183)
- # clojure-uk (18)
- # clojurescript (155)
- # cursive (6)
- # datomic (25)
- # euroclojure (6)
- # funcool (6)
- # hoplon (229)
- # instaparse (10)
- # jobs (9)
- # leiningen (5)
- # off-topic (70)
- # om (29)
- # onyx (18)
- # planck (1)
- # proton (5)
- # re-frame (8)
- # reagent (32)
- # untangled (4)
@iamjarvo: That's be incredibly helpful. I'd love to see three major things resolved disregarding the open PRs/tickets: 1) Upgraded to 1.8, 2) Updated to the latest Github API specification, 3) API client has an issue that I can barely recall where some endpoints return things that aren't consistent with the rest of the API (like a map vs a vector) and breaks it dramatically.
Those are the top three issues. I haven't looked at the latest github API spec, but it could be time to rewrite the whole thing without a function for each API call.
Wrapping each method is insane. It'd be cooler if the API was consistent enough to develop a lightweight flexible doesn't-need-updated-for-every-API-method-that-gets-added way of doing things.
But take it or leave it, there's a lot of work to do on tentacles and that's why I haven't spent much time on individual prs and issues.
But hey, my calendar recently freed up quite a bit so while I'm working on Amazon Echo skills at this particular moment in time I plan to spend time with Clojure projects this week.
You're welcome to take this one, it's one of a million I need to go update/deprecate/fix
btw @raynes, I am using tentacles on a demo in a talk tomorrow morning and it was a beautiful thing to pick up and mess with for that purpose
Well that's convenient as all hell because I sure as heck hate this leiningen bat file and I sure don't have a mac anymore and I actually kinda like Windows 10 especially on a surface book.
I'm a Windows 10 insider so I'm getting preview builds. They're doing native Ubuntu/Bash integration.
VSCode is a solid competitor to Atom, Visual Studio doesn't suck half as bad as it used to.
Maybe not so much intellij since I won't be writing Scala again soon unless Andre the Giant shoves it down my throat.
I think that's the next project I take on - building a framework for server-based Alexa skills.
Lease useful feature ever but it isn't even just a joke feature, it's also a ping feature to see if there's an issue with communication with the skill vs the receiver for debugging purposes.
Because that intent never touches the receiver, if it runs and responds then the skill is working and listening.
But yeah basically my goal is to do this alexandra style simplistic framework for Clojure. I don't even think I'm gonna look at echo chamber, it's been so long since I wrote a Clojure thing from scratch I just gotta dig in there.
I have two skills I need to build that I'd like to build using Clojure: more fine grained control of Phillips Hue bulbs (the Echo's built in support is purely on-off-brightness with no color control) and a Chromecast skill for pause/play/skip[f|b]/volume.
Unfortunately I'm mostly abandoning yams. Turns out Yamaha receivers seem to just (I've tested with two) have this flaw where they, within an hour of being turned on, become inaccessible via the built in http server.