News for hackers. Stuff that matters.

A comment on The road to Ember 2.0 RFC. Parent comment

Re:The road to Ember 2.0 RFC by inglor on Monday November 03, 2014 @12:35PM (#8552126)
The RFC process sounds very nice but be careful. PHP has been doing it for a while now and while it's working out nicely for them in some regards - pretty much every php person I talked to involved with it hates 'internals' with a passion.
[ Parent | on HN ]
Re:The road to Ember 2.0 RFC by tomdale on Monday November 03, 2014 @12:41PM (#8552155)
We do development of new features behind feature flags, and have automated tools to help enable, disable and strip them. We're planning on moving to a model where we do an approximately annual "garbage collection" pass on the framework (corresponding with a major version bump) and simply nuke all of the code that has been deprecated since the last major version release.
[ Parent | on HN ]
Re:The road to Ember 2.0 RFC by oblio on Monday November 03, 2014 @12:43PM (#8552172)
Maybe a process similar to Django's would be helpful? https://docs.djangoproject.com/en/dev/internals/release-proc...
[ Parent | on HN ]
Re:The road to Ember 2.0 RFC by steveklabnik on Monday November 03, 2014 @12:57PM (#8552265)
Fun fact: Python's PEP process influenced Rust's RFC process, which influenced Ember's.
[ Parent | on HN ]
Re:The road to Ember 2.0 RFC by porker on Monday November 03, 2014 @03:45PM (#8553369)
There is a long history behind the hating of 'internals' in PHP land. The RFC process has improved matters, but can't get rid of all the poison that already existed.
[ Parent | on HN ]