After 12 months using Meteor and reading tens of posts regarding the future of the platform, I’d like to share my opinion about the whole situation and how you can become a better programmer this year:
“Software development is technical activity conducted by human beings.” (Niklaus Wirth)
If you don’t like changes or don’t have power to make them daily, don’t feel comfortable refactoring your existing code and your mindset every single day, don’t have time or don’t want to study about new technologies and trends, I’m afraid to say but Meteor is not for you.
On the other hand, if you understand that changes are inevitable, you will see that using Meteor is an excellent choice and a great way to be a better professional. You will be constantly ripped out from your comfort zone but, in the end, you will see that you never learned so much in a such a short period of time.
It doesn’t matter if you want more “stable” solutions with less changes. Do you know why? Independent of your business, we are living in a society that consumes innovation, so want it or not, changes are unavoidable and the day of changes will always come.
To become a better programmer you must have a reason for it. My reason is Meteor.
Until you start making a big project with Blaze and have to invest money. As much as it is fun / interesting / out of the confort zone, in the end it is an investment, where people hope to get something in return. And thus, instability is my reason NOT to Meteor (until things settle).
if you are an old dev and get home after 5 probably it means your not good, as most older devs are working from home and/or are payed per hour.
Besides programming its like sex. When you are young you have a lot of sex, but you are clumsy, messy, and always in a hurry so quality is not that good. When your older, you don’t have sex often, but you have quality sex that compensates.
When you are an older dev, you write (a lot) less code, but it does the job as it should.
The current flux of innovation in JavaScript is also a big part of why I’m sticking to it, as I’m learning from it like nothing I’ve ever studied before
I know C# and Java. I agree they have, for example, async/await, modules etc.
I’m talking about JavaScript as a community, not as a language.
I’m talking about innovation, not “primitive” language features. Time-travelling debuggers, implicit vs explicit reactivity, functional vs imperative programming, transpilation with babel, connected client vs lamp stack, isomorphism… I could go on forever, and it’s smeared all over the entire community with ideas, implementation examples, proposed changes And it’s nothing short of awesome to see this kind of momentum and enthusiasm.
And it’s nothing short of awesome to see this kind of momentum and enthusiasm.
)
scaling was never a factor that drove me to Meteor anyway.