Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add note to point devs at @most/core for new projects #526

Merged
merged 2 commits into from
Aug 24, 2018

Conversation

briancavalier
Copy link
Member

Summary

@most/core is the future of mostjs, and most 2.0 is close. Most 2.0 will be based on @most/core, will be directly compatible with it, and will be a trivial upgrade for folks who prefer a single dependency in their package.json.

The goal of this addition is to help devs make a more forward-compatible choice for new projects and let them know there will be a guide to help them upgrade existing projects. It encourages devs to pick @most/core now for new projects, and points existing most 1.x-based projects to the upgrade guide (still a WIP as of this writing).

Copy link
Collaborator

@Frikki Frikki left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tiny language update.

README.md Outdated
@@ -13,6 +13,16 @@ _ / / / / /_/ /____/ /_ /
[![Build Status](https://travis-ci.org/cujojs/most.svg?branch=master)](https://travis-ci.org/cujojs/most)
[![Join the chat at https://gitter.im/cujojs/most](https://badges.gitter.im/Join%20Chat.svg)](https://gitter.im/cujojs/most?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)

## Starting a new project?

Strongly consider starting with [`@most/core`](https://github.com/mostjs/core). It is the foundation of the upcoming most 2.0, has [improved documentation](http://mostcore.rtfd.io/), new features, better tree-shaking build characteristics, and simpler APIs. Updating from `@most/core` to most 2.0 will be simple and non-breaking.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Update to avoid over-used words, such as “simple”:

Strongly consider starting with @most/core. It is the foundation of the upcoming most 2.0, has improved documentation, new features, better tree-shaking build characteristics, and simpler APIs. Updating from @most/core to most 2.0 will be non-breaking and straightforward.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, updated.

@briancavalier
Copy link
Member Author

briancavalier commented Aug 23, 2018

I added the same note to the top of the API docs in 4934638

Copy link
Collaborator

@Frikki Frikki left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice!

@briancavalier briancavalier merged commit 13ca5c6 into master Aug 24, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants