We Are Pioneers: the Journey to Ember.js
hawkins.io
We Are Pioneers: the Journey to Ember.js
1–10 of 23 posts
Re: We Are Pioneers: the Journey to Ember.js
#2 > I've seen [the problems that occur when you're working
> with an immature ecosystem] before. I started with Rails
> in 2006. It was difficult in the earlier years. It has
> only really matured in the past 3 years. I think Rails
> 3.1 really embodies everything you need to make a
> certain class of web applications. Ember and its
> ecosystem are so far off.
Rails Releases Ember.js
--------------------- --------------------------
3.1.0 August 31, 2011 Now + 6.5 Years (End 2020)
3.0.0 August 29, 2010 Now + 5.5 Years (End 2019)
2.0.0 December 6, 2007 Now + 2 Years (Mid 2015)
1.0.0 December 13, 2005 Now (Mid 2013)
Re: We Are Pioneers: the Journey to Ember.js
#3I'm sorry but this is one of the most ridiculously vacuous, self-aggrandising pieces of nonsense I have ever seen submitted to HN. Even more so when it's just another framework, and not really even a particularly popular or revolutionary one. Pushing boundaries like travelling across the sea to an almost entirely unknown continent with little to no chance of return regardless of what you find there? Please. I think we need to stand back and take a deep breath.
Re: We Are Pioneers: the Journey to Ember.js
#4I'm sorry but this is one of the most ridiculously vacuous, self-aggrandising pieces of nonsense I have ever seen submitted to HN. Even more so when it's just another framework, and not really even a particularly popular or revolutionary one. Pushing boundaries like travelling across the sea to an almost entirely unknown continent with little to no chance of return regardless of what you find there? Please. I think w…
If I didn't know better, I'd accuse you of secretly being the OP and writing this comment that just begs jaded HN users to click through.
Re: We Are Pioneers: the Journey to Ember.js
#5I'm sorry but this is one of the most ridiculously vacuous, self-aggrandising pieces of nonsense I have ever seen submitted to HN. Even more so when it's just another framework, and not really even a particularly popular or revolutionary one. Pushing boundaries like travelling across the sea to an almost entirely unknown continent with little to no chance of return regardless of what you find there? Please. I think w…
Agreed. I was laughing out loud at some of the analogies, but the author does make some good points -- it's really early in the client side framework evolution.
Re: We Are Pioneers: the Journey to Ember.js
#6I'm sorry but this is one of the most ridiculously vacuous, self-aggrandising pieces of nonsense I have ever seen submitted to HN. Even more so when it's just another framework, and not really even a particularly popular or revolutionary one. Pushing boundaries like travelling across the sea to an almost entirely unknown continent with little to no chance of return regardless of what you find there? Please. I think w…
I was afraid it would come off like this. I picked the analogy and went with it.
Re: We Are Pioneers: the Journey to Ember.js
#7I'm sorry but this is one of the most ridiculously vacuous, self-aggrandising pieces of nonsense I have ever seen submitted to HN. Even more so when it's just another framework, and not really even a particularly popular or revolutionary one. Pushing boundaries like travelling across the sea to an almost entirely unknown continent with little to no chance of return regardless of what you find there? Please. I think w…
If I didn't know better, I'd accuse you of secretly being the OP and writing this comment that just begs jaded HN users to click through.
Nah I'm the author :)
Re: We Are Pioneers: the Journey to Ember.js
#8I'm sorry but this is one of the most ridiculously vacuous, self-aggrandising pieces of nonsense I have ever seen submitted to HN. Even more so when it's just another framework, and not really even a particularly popular or revolutionary one. Pushing boundaries like travelling across the sea to an almost entirely unknown continent with little to no chance of return regardless of what you find there? Please. I think w…
I was afraid it would come off like this. I picked the analogy and went with it.
Don't worry about it. The commenter here is wrong in assuming that using history to understand our own narrative implies something about the scale or scope of the original, or our own.
Events need not be the same for us to try to use them to understand and vocalize our experiences.
Great writeup! Some days I feel similarly about Ember.
Re: We Are Pioneers: the Journey to Ember.js
#9Earlier quoted context omitted.
I was afraid it would come off like this. I picked the analogy and went with it.
Don't worry about it. The commenter here is wrong in assuming that using history to understand our own narrative implies something about the scale or scope of the original, or our own. Events need not be the same for us to try to use them to understand and vocalize our experiences. Great writeup! Some days I feel similarly about Ember.
Thanks. I'm glad you enjoyed the post.
Re: We Are Pioneers: the Journey to Ember.js
#10I think it's important to rethink this progression a bit. In the early years of Rails, what else was around? What other Ruby-oriented frameworks did we find that did what Rails did? How many people were developing web-based MVC apps on a day-to-day basis in comparison to how many are developing them now? GitHub wasn't even around until three years after Rails v1 - seems like maybe GitHub on its own will have untold effects on speeding up development time on a project like Ember.
Let's consider also the simple fact that ALL client-side MVC frameworks are JavaScript (unless they are precompiler-based, which none of the big ones really are, currently). The fact that all of them are based on the same language, the massive cracks in server-side systems that are further exacerbated by language idiosyncrasies are reduced significantly.