safe name to descrbe a fundamentally new idea. Ember.js it was! ! Initially, Ember was a view library, just like Angular.js or React.js is today. It's easy to forget, but we didn't even have a router!
for a slice of the jQuery Refugee pie, we built a community of people who believed they were building "ambitious web applications". ! As application developers ourselves, we refused to settle for the status quo that said that tiny, simplistic abstractions were the epitome of good design. We put out the call: let's build ambitious web applications together.
me that while the idea was good, the developer ergonomics were terrible. * It would have been easy to let the inertia of Router v1 brush off his critique.
even thought to attempt before, because the degree of difficulty was so high my brain just closed the door on the option. http://frontside.io/blog/2014/02/24/ember-and-the-future-of-the-web.html I consider myself successful when I am building a thriving, growing community of people building amazing things that they couldn't have dreamed of building before.
your idea; to give people something to join. "Ambitious Web Apps" and not being embarassed of "Framework" made it clear what people were joining and who should stay away.
people will be ready with rotten tomatoes every time we pitch the idea of shared community solutions at the app level of abstraction. We knew what we were signing up for
keep you sane during these periods or you will burn out and give up. It's amazing how many new ideas flame out within 6 months. If it's worth doing, it's worth signing up to do for a while.
mean the rest of the world doesn't have a point * We got increasingly micro-library'y over time * We learned the importance of a super-easy starting experience from Angular, but never sacrificed one core principle: the getting started experience has to be a subset of the real-world experience, not a totally different one. * We spent a lot of time seriously considering React's approach, to see what parts of it people perceive as "simple", even though React's solution is a small subset of the "ambitious web app" scope Ember has. It's super-easy to ignore these kinds of things. * TL;DR We spend a lot of time looking at what everyone else is doing and saying, and even if we don't agree with the message, we look for things that work well or appeal to people.
say "ship and iterate", but then forget to iterate once "workarounds" are well understood by the community. ! (I consider proliferated workarounds to be a bug)
thinking hard and periods of implementation and "contact with reality". ! It's easy to get over-focused on "Big Ideas" or "Just Ship It", so you have to push yourself to ship regularly as well as really think through what is happening.
I try to surround myself with people who share my big-picture goal but are willing to challenge everything all the time. * We seriously considered using React under the hood in Ember * We rewrote Router v1 from scratch * We ask ourselves constantly why people are confused or challenged, and don't accept excuses * Finding a collaborator and taking regular walks is an excellent way to avoid getting stuck in the intertia of decisions already taken.
you don't have to be all things to all people. If somebody doesn't like what we have to offer, that's totally fine. You get far more mileage out of being true to your principles and giving people a refined, focused solution to a problem everyone understands than prioritizing growth above all else. * Example: Ember has always been "embeddable", but we focus on people who want to build applications instead of watering down our message and documentation with a million ways to do anything.
door to people peeking in around the edges, so some amount of adaptation is a good idea, but only in service of getting them to the same place. Embedding is a great transitional solution, but only for people who are ultimately interested in building an app.
door to people peeking in around the edges, so some amount of adaptation is a good idea, but only in service of getting them to the same place. Embedding is a great transitional solution, but only for people who are ultimately interested in building an app.
even thought to attempt before, because the degree of difficulty was so high my brain just closed the door on the option. http://frontside.io/blog/2014/02/24/ember-and-the-future-of-the-web.html We're Building Amazing Things: Personally, I am interested in working on tools and technologies that help people build things they couldn't imagine building before. Not everyone is interested in pushing the boundaries, but there are enough people like that to keep people like me busy.
yourself to abandon your principles in search of some temporary gain. Instead, strap yourself in and commit to push the envelope and never stop trying, no matter what anyone says. Don't Settle.