What’s happening? https://github.com/google/clojure-turtle

@athos: hmmm Interesting!

@athos: where(how) did you find this ??

@gjnoonan: Yeah! I totally don’t know what this is, but it looks interesting. @snufkon: I saw somebody tweeted about it.

I remember Logo on C=64, primary school

Nice project clojure-turtle

Wow, ‘turtle’ really means turtle graphics.

So, why is Google reinventing Logo?

re-inventing? it's a small program

I mean, reinventing in the sense of “reinventing the wheel” 😃

there are many things replicated across languages.

Love it. Logo was my first experience with a counter at school.

the readme file says "This is not an official Google product (experimental or otherwise), it is just code that happens to be owned by Google."

strange are the paths of code ownership

nikolap: maybe they wrote it on a laptop owned by Google! reminds of the last episode of Silicon Valley

pastafari: right! 😄 great episode.

Counterclockwise has great syntax-highlighted REPL / editor support if you are an Eclipse user.

what is the most efficient way of swinging between Clojure vector and Java array? into-array and vec?

@ul yep

I was wondering if anyone has written down advice on code organization of a typical clojure web application (compared to a standard Rails app with models, services, config, etc)

this seems an interesting video about it http://www.infoq.com/presentations/DDD-Clojure

best tip i got from that talk was the use of a ‘homeless’ namespace

(ns cognician.homeless …)

great for acknowledging that you need a good place to put this thing but you’re not sure where right now

he mentions 'domain' should be pure. In the context of a simple crud app, domain would be almost empty then I guess.

@borkdude: I don't think there is any standard (which isn't great imo). I can describe how Yeller's webapp is organized, but I ain't particularly happy with it 😕

@tcrayford: I'm always interested to hear it. Every app I've built is different and I'm always searching to improve the structure.

@borkdude: so roughly the whole thing is in src/yeller/web. Everything's flat inside there. There's one "main" namespace: yeller.web.routes (that contains all the compojure routes), and one supporting thing for that, yeller.web.middleware. Then each "part" of the domain has several namespaces: yeller.web.invite_handlers (for ring handlers), yeller.web.invite_views (for stuff that renders into html), yeller.web.invites (for any logic that isn't strictly to do with HTTP)

so yeller.web.invites has the domain logic if there is any?

yeah

alternatives I have considered: yeller.web.invites.views, yeller.web.views.invites didn't like any of them (or the alternative I picked)