Stars Fell On Alabama, or My Shift to MeteorJS

1 min read

It's been quiet around these parts lately; I apologize. I've been shifting away from Ember and Angular for a while now and I don't regret it one bit. Why? Well let me tell you about the most fun I've had learning and developing recently.

Angular is great for front-end developers like myself, but I didn't appreciate the sudden move to a complete different syntax that is confusing (yet more intuitive). Ember seemed very nice in theory, but no matter what I tried I could not wrap my head around all of it.

A Short History Lesson On Me

Back in 2013, I was starting a new job and looking for a good solution for the newly formed team. Meteor flew past me in a whirlwind of new technologies so I researched a bit into it, but ultimately moved on to something that was more familiar to another co-worker. We settled on Grails/Groovy to build enterprise level healthcare applications, but I did not forget about Meteor. Fast forward to February 2015 and I rediscovered Meteor via the Discover Meteor book (see what I did there?). After just a few days with Meteor, I was hooked.

Not a framework, but instead a full solution

Meteor is a full-stack JavaScript solution, not a framework. Utilizing new technologies and allowing developers to program a full application in mere months using only JavaScript was perfect. I love how quickly and easy it is to build with MeteorJS, and full reactivity is just plain awesome.

So what's next? I've decided to start writing solely about Meteor. Why do I feel people might actually read my words? Because I'm beginning down a road that many other developers are traveling also. I will hit all the small potholes and big roundabouts in the process and write about it. So expect to see short posts, long posts, links, videos, and anything else I find interesting about this new world.

Also I changed the blog name, not that anyone really cares.

Let's do this!