Meteor showers are a spectacle to see. Streak of lights illuminating the night sky. A very enthusiastic celestial event for everyone to enjoy, from a distance that is. If magically you were to fly into the path of the shooting star, getting closer and closer; well you could get burned. Similarly, when initally hearing about the Meteor Framework I was essentially admiring it from afar, being impressed about its features. And then the Meteor started getting closer, or rather I decided to take flight into its path.
I got burned … out. There is definitely a learning curve when initally starting meteor, and boy that steep learning curve was real. It wasn’t gonna be easy. I honestly hated it. But then, what is easy about learning something new anyway? When first learning Meteor, we were given simple assignments to do. Screencasts and tutorials of how to do things were also given as supplemental information. All the information however just didn’t seem stick with me. I always found myself not being able to understand why certain steps were done to do a certain task. Adding to that, I’d often get lost while doing the assignments since there were so many files having the same filenames. Sometimes I’d accidentally edit the wrong file, causing a huge mess in the application, and adding more stress to solving unending errors that I’d have to debug through. The end product was cool though; a fully functional application that was created in real-time.
About two weeks into Meteor, and many assignments later, I finally have a grasp of what is going on. Then the pros of the software finally come back to mind. Development in real-time, smart packages, and tons of integration, support, and features right out of the box. You realize just the amount of work that Meteor does for you. I’m not completely sure of how to implement everything right on the spot, but I’m becoming comfortable using the framework. Although I’m positive my knowledge of Meteor will increase with more experience and time working in the framework.