Good morning.
Morning
I just got a very quick and dirty server side pre-rendering working with nodejs, reagent, re-frame doing ajax calls. \o/
yeah :simple_smile:
The bad news is that it requires a fork of re-frame. Hopefully my simple change will be merged into it later on.
I just wrote (console.log “foo”) in a javascript file. I’m finally thinking in Clojure.
haha
congratulations I guess :simple_smile:
morning
I have given up on yada for the moment.... 😞
using compojure again...
and struggling a bit with a POST command....
@pupeno: my younger brother is just starting to get into programming, he’s learning Javascript and often sends me snippets like “(some-function ‘hello’)” and asks me why it doesn’t work, i think he’s destined to be a LISPer
@afhammad: hahah. I’m doing an experiment with one of my parters, getting her started with Clojure before trying other languages. We’ll see how that goes.
@pupeno: yeh i wonder what the transition from a lisp to a non lisp language is like
@pupeno: interesting experiment... I remember reading somewhere that some people find lisp easier to start with....
I wish I started with a Lisp, but on the other hand, I’m glad I started with C.
So far, I don’t know how she’s doing because I don’t have enough experience teaching. She’s struggling with some things but that might be the normal learning process. Some of those are inherent to functional programming, but that doesn’t mean she wouldn’t struggle with the other oo-inherent things.
Argh… I also need to fork node-xmlhttprequest 😞
And I just finished my pre-rendering library. It works, but it requires forks of node-xmlhttprequest and re-frame (small changes). I’m off for a bit and when I’m back I’ll start documenting it. Hopefully it’ll be out today.
Cool stuff :simple_smile:
@pupeno: you are everywhere. I just searched for a cursive cheatsheet and got this: http://www.cheatography.com/pupeno/cheat-sheets/cursive-on-mac-os-x/
:simple_smile:
@thomas: what stopped you with yada ?
@mccraigmccraig too many new steep learning curves at the same time. Still think yada would be better for my use case. But not 100% certain it has all the functionality I need in it.
There is a comment in one of the tests that maps in atoms aren't supported yet.
@thomas i can understand the learning curve thing, given what you tried
what functionality do you need in yada ?
And I think that would be very beneficial for my use case
pretty sure atom resources are supported - https://github.com/juxt/yada/blob/master/src/yada/resources/atom_resource.clj
I have been asked to build a simple rest phonebook service.
https://github.com/juxt/yada/blob/master/test/yada/atom_resource_test.clj
;; TODO: Restore this test once atoms can wrap maps (and other collections)
is the one I spotted.
ah, gotcha, atoms work, maybe not maps in atoms
but you wouldn't really be wanting to use those would you ? you would want some persistence
and I think for a simple DB I would need a those...
for this particular example a in memory DB would be good enough.
well, you don't need to use atoms/maps at all - the AtomResource thing is just a ready-to-roll resource implementation
it's straightforward to create your own resources from functions
I have to take another look at it...
e.g. here's a login-resource : https://www.refheap.com/bbf94136e5222185236e83ef1
at the moment my compojure solution is looking pretty good. but not as "complete" as a yada solution woul.
probably a lot more synchronous too :simple_smile: ... i went with yada because i can make everything async
compojure is a lot more mature though, so it will definitely be an easier ride
yes... but I guess you could replace jetty/ring with http-kit.
and it is something i was familiar with as well. makes a big difference to get going.
but I just decided I needed to rewrite bits of it... want to use UUIDs for identifying my resources.
but that is something for tomorrow... need some sleep now.
ha, i'm deep in the guts of my cassandra client. no sleep for a while yet
ok good luck. and do get some sleep.
ttfn