Well, ‘tis official, I’ve given up on GeddyJS. My original foray started out very polite and good and productive. But in the end, I had to walk away to something that was more ‘node’. Here's how it went down, step by step.
tl;dr: Geddyjs is RoR without the large community. Expressjs is a set of simple tools to get stuff done. I am learning this the stupid way.
I do front end, I do OOP
Let me first say I‘m not really, really a server thinker. I don’t really care about a stack. I don‘t really care about routes. I don’t really care about database layers or adapters or, you know, whatever.
new keyword. I like to have one
class for one concern, and that‘s pretty much it. Compiler or build errors make me feel warm and fuzzy and runtime errors (any way you throw them) make me feel sickly and dizzy. But that relegates me to a weird Product development plane which doesn’t exist in my world. You do websites, you do front end in my world.
OHAI, Ruby on Rails
Without knowing a lick of Ruby, one day I decide it would be an awesome idea to teach myself Ruby on Rails. It was awesome. It was probably the most accessible introduction to writing a server I‘ve ever had. RoR is largely automatic, and as I understood the basics of MVC or Router View Controller, it made sense. But RoR or Ruby (I don’t know which) isn't really OOP. And RoR sites don't really compile, at least not how I'm used to with Java, C#, C++ and ahem ActionScript. So I kind of just fizzled on RoR and gave up.
Well, Excuse Me, Mr. Geddy
Geddy is RoR for js, let‘s not kid ourselves. It’s really new and baby-like and doesn‘t really have a big community. That means if I google a question, I typically spend too much time finding an answer, if I find one at all. That’s lazy. But it also doesn‘t support debugging (I’ve become fond of node-inspector) and it doesn't yet have a great API. I know a lot of hardcore bro devs love to say crap like “just look at the source” but srsly, tl;dr. Api docs are good for adoption and way faster than reading source. I could just break and peek into the objects available at runtime but, shrug, there's no debugging Geddy. So I just walked away.