http://gist.io/5378663 if you like your eyes or you're on a mobile device.
... or you don't want to read the enlightening reply from an Ember core member :P
Anonymous Open Letter to the Ember.js Core Team
31–40 of 44 posts
Re: Anonymous Open Letter to the Ember.js Core Team
#32http://gist.io/5378663 if you like your eyes or you're on a mobile device.
... or you don't want to read the enlightening reply from an Ember core member :P
Re: Anonymous Open Letter to the Ember.js Core Team
#33PG: is it possible to configure HN to show the domain as gist.github.com instead of just github.com?
Yes, browsers have this feature where you can hover a link and it reveals the href.
It's easy to use snark to dismiss someone's problem.
Why show the domain at all if you can hover over the links? For a minimalistic interface like HN you'd think there would be a reason for it. And if people are identifying content based on that URL, it's probably best to make it descriptive when subdomains have very different content.
Plus, many touchscreen devices don't have an easy way to see where a link is pointing to, even on devices with 'hover' functionality.
Re: Anonymous Open Letter to the Ember.js Core Team
#34Not to sidetrack the conversation, but why is Backbone "a joke"? It seems a bit different in approach from Ember, but I've used it for a pretty big application and it worked great.
Re: Anonymous Open Letter to the Ember.js Core Team
#35It's scary, but even if you release something as open source, for free and free for people to modify as they please, you're still in a weird relationship with the people that use your software. You haven't exactly promised to do anything for them, and the code as-is is in itself a great gift... but on the other hand, there's an implicit acknowledgement that "yes, you can build on this". (Both the open letter and the…
Maybe the open source community needs a sort of standard way of declaring/disclaiming how production-ready a project is, and how much effort we intend to put into supporting it.
Re: Anonymous Open Letter to the Ember.js Core Team
#36To the ember.js team: don't worry, people like this are poison to open source. They demand so much, have such high expectations, and are not willing to contribute anything. They do not realize people have real lives outside of open source, and sometimes they need a break.
This is making a lot of assumptions about the author of the gist, whom we know absolutely nothing about.
They might actually be one of the contributors.
Re: Anonymous Open Letter to the Ember.js Core Team
#37Not to sidetrack the conversation, but why is Backbone "a joke"? It seems a bit different in approach from Ember, but I've used it for a pretty big application and it worked great.
IMHO Backbone is in a weird spot between plain old jQuery apps with no structure, and frameworks like Ember/Cappuccino/Angular/Knockoutthat have "bindings" constructs that can drastically reduce glue code.
Re: Anonymous Open Letter to the Ember.js Core Team
#38To the ember.js team: don't worry, people like this are poison to open source. They demand so much, have such high expectations, and are not willing to contribute anything. They do not realize people have real lives outside of open source, and sometimes they need a break.
On the contrary, he's unhappy that contributions (PRs) are ignored.
Pull requests can take more time to process than feature requests, because 1) The code is usually inconsistent with the rest of the project, 2) there are often merge conflicts that the submitter has to resolve 3) people rarely write tests or documentation about the feature.
Re: Anonymous Open Letter to the Ember.js Core Team
#39It's scary, but even if you release something as open source, for free and free for people to modify as they please, you're still in a weird relationship with the people that use your software. You haven't exactly promised to do anything for them, and the code as-is is in itself a great gift... but on the other hand, there's an implicit acknowledgement that "yes, you can build on this". (Both the open letter and the…
Maybe the open source community needs a sort of standard way of declaring/disclaiming how production-ready a project is, and how much effort we intend to put into supporting it.
People should assume that if there is no affirmative declaration of "This is production ready" then the code is not production ready.
If there is no affirmative declaration of "I will be actively supporting this beyond my own personal needs" then assume that the code will not be supported beyond the personal needs of the project owner.
Or people can just ask, instead complaining (however well-intended) that their assumptions have turned out false.
This is like people who build a business on some aspect of Twitter or Facebook then complain that Twitter or Facebook is shutting them out. If you are using someone else's code or API make sure you get some positive, unambiguous statement from the owner about what to expect.
Things can still go south, but then you at least have a legitimate gripe.
Re: Anonymous Open Letter to the Ember.js Core Team
#40It's scary, but even if you release something as open source, for free and free for people to modify as they please, you're still in a weird relationship with the people that use your software. You haven't exactly promised to do anything for them, and the code as-is is in itself a great gift... but on the other hand, there's an implicit acknowledgement that "yes, you can build on this". (Both the open letter and the…
Maybe the open source community needs a sort of standard way of declaring/disclaiming how production-ready a project is, and how much effort we intend to put into supporting it.
In the gist, even though the Ember Data README states that it's not production ready, the author complains that it 'should be' or something. We have that standard, it's called '1.0'.