Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
API Freeze : Atom 1.0-pre #3041
The goal is to improve the package writing experience and settle on an API we will support through 1.0. This means cleaning up the API, writing better API documentation and redesigning the API webpage.
The result of the API freeze will be an solid structure on which we can build. A lot of methods and approaches will be deprecated, but nothing will be removed until we near 1.0. We will be able to add more APIs after the freeze, but will commit to not removing anything until the next major.
Punting on for now
See https://github.com/atom/atom/labels/api-freeze-roadmap for a list of open issues
What do you think about removing
I don't see the value in this one and it is really vague, we can always do this in the future, nothing about the 1.0 API would be dependent on it, since packages don't really expose APIs.
Was this referring to any packages specifically? If it is, it might be clearer to just list those.
I think this is valuable because we are going to be persuading people to use react to write their packages. They're going to look at the builtin packages, and think, "this doesnt use react. I know jquery, I'm using that." Or, "I'm copying this bit cause it mostly does what I want."
Also, we should rewrite a couple of the packages just so we know where the sharp edges are and nice patterns to use when writing with react.
As an unseasoned developer, I would suggest to document those re-writes, maybe in blog posts if they are interesting enough, which would help everyone getting to know the differences and advantages of using React or even to use Atom as a first test bed to start learning about it.