Fork me on GitHub
#off-topic
<
2016-04-11
>
borkdude08:04:44

good morning girls and guys

puhrez08:04:35

good morning dude

sveri08:04:41

Good morning simple_smile

raynes11:04:07

It's so wild we have a slack now. (repost where it shoulda been anyways)

borkdude11:04:06

welcome @raynes

raynes21:04:19

@iamjarvo: Howdy

iamjarvo22:04:51

Hey @raynes

raynes22:04:29

I saw your email good sir.

raynes22:04:13

@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.

raynes22:04:42

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.

raynes22:04:54

I was fairly dumb when I wrote it that way regardless.

raynes22:04:33

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.

raynes22:04:52

Or at least some sort of metaprogramming to generate those methods.

raynes22:04:21

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.

raynes22:04:54

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.

raynes22:04:38

You're welcome to take this one, it's one of a million I need to go update/deprecate/fix

alexmiller23:04:29

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

alexmiller23:04:15

virtual 🍺 to you

alexmiller23:04:22

or beverage of your choice

raynes23:04:28

Well awesome that it actually still works.

raynes23:04:37

I've been outta Clojuretown for a minute

alexmiller23:04:40

well the 3 things I'm doing with it work

alexmiller23:04:59

so I totally vouch for those 3 things

raynes23:04:27

So I heard you like boot

raynes23:04:22

(there's a new build tool in town)

raynes23:04:32

That always gets me excited.

raynes23:04:20

Wait | hold up. Damn. Boot has a .exe for Windows users

raynes23:04:58

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.

alexmiller23:04:14

didn't I hear windows is going to do bash now?

raynes23:04:47

I'm a Windows 10 insider so I'm getting preview builds. They're doing native Ubuntu/Bash integration.

raynes23:04:54

They're also doing legit OpenSSH.

raynes23:04:29

VSCode is a solid competitor to Atom, Visual Studio doesn't suck half as bad as it used to.

raynes23:04:36

Though I'm an Atom dude

raynes23:04:43

Atom/Intellij

raynes23:04:10

Maybe not so much intellij since I won't be writing Scala again soon unless Andre the Giant shoves it down my throat.

raynes23:04:35

That said, Cursive is probably a better environment for Clojure than Atom.

raynes23:04:42

So maybe still Intellijing.

raynes23:04:14

I've mostly been developing Amazon Echo stuff in Python and Node.

raynes23:04:30

(for side projects, which are now... all my projects for the time being)

raynes23:04:50

(I am currently between jobs hence trying to jump back into Clojureland)

raynes23:04:01

I'm codecationing.

alexmiller23:04:19

talk in this area

raynes23:04:05

Wish I could make it

raynes23:04:46

He's doing this library for their Lambda version of Alexa skills...

raynes23:04:03

I see echo-chamber is a halfway-there framework for building Alexa skills in Clojure

raynes23:04:27

I think that's the next project I take on - building a framework for server-based Alexa skills.

raynes23:04:42

I built one with a close friend, https://github.com/erik/alexandra in Python.

raynes23:04:58

I'd like to take our learnings there and build something Clojury that's this simple.

raynes23:04:24

https://github.com/Raynes/yams is an example of using the aforementioned framework.

raynes23:04:27

Echo, ask Kendrick (my name for the skill) "What's the yams?"

raynes23:04:58

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.

raynes23:04:18

Because that intent never touches the receiver, if it runs and responds then the skill is working and listening.

raynes23:04:28

Sorry, probably more info than you care about 😛

raynes23:04:12

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.

raynes23:04:46

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.

raynes23:04:28

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.

raynes23:04:16

I've gone as far as assigning a static IP so it's clearly a firmware issue given my internet investigation. I have it plugged into a tp-link wifi switch so I can tell the echo to power cycle it when a yams call isn't working lol.