please clarify om.now and om.next's relationship in this repo

[matanox]

It might seem a little elusive how both om.now and om.next co-exist in this repo. E.g:
I created an om project following the om.now tutorial. In project.clj I have the dependency:

[org.omcljs/om "1.0.0-alpha40"]

On the other hand the om.next tutorial implies the dependency:

 [org.omcljs/om "1.0.0-alpha34"]

It's a little fuzzy how exactly the two projects are separated. Could the exact way that both projects are managed in this repo be clarified here and/or in the Wiki? What have I missed? Thanks!

[anmonteiro]

Hi @matanster,

thanks for bringing up that concern. This repository contains both om.core and om.next. That said, it might not be clear to everyone why that is, so questions like yours might arise. I'll try to clarify why both projects live in this repo and try to answer your questions regarding versions.

Why do both projects live in this repo?

The answer to this question is two-fold:

1. Both projects share the om.dom namespace, and possibly a few others. This way we avoid code duplication (and maintenance) across two different repos.
2. om.next is still evolving (though really close to beta now!), so it was a way of both providing compatibility for people using om.core and iterating on om.next in a conflict-free manner.

• As a freebie, it also means that you get free React upgrades for om.core (more on this below)!

Why are there different dependency versions of Om listed in the Wiki?

The main reason for this to happen is that om.next is still in alpha so a lot of churn is still going on. This means that alpha versions are released somewhat frequently and the Wiki has been lagging behind (mostly because of the lack of time to update the tutorials with the new versions and check if everything still works properly.

Should I use [org.omcljs/om "0.9.0"] with om.core and the latest alpha with om.next?

The answer is "it depends" 😄:

• Om 0.9.0 uses React 0.13.3. If you're comfortable using that version, go ahead and depend on it!
• However, there's nothing preventing you from consuming om.core from the latest Om alphas . It simply means that you get the latest React version bundled with Om. There have been absolutely no changes to om.core between 0.9.0 and the latest alphas besides React compatibility updates.

How can you help?

As I said above, we don't have a lot of time to check if the code listed in the om.next Wiki tutorials work with the latest Om alphas. If you (or others) want to contribute in some way, running those tutorials locally against the latest released versions and checking that everything still works would be a huge help! Then versions can be safely updated in those tutorials for other newcomers. This both helps their first experience (having a breeze through the tutorials) and Om maintainers (such that we don't get reports for bugs that we already fixed!).

Hope the above helps!

[matanox]

Thanks, excellent!
So I gather that it is the same code base, and that to use om.next (which I've never tried before) I would just require / use different names in my program. Did I get that right too?

[anmonteiro]

That's exactly right. Provided you are on a 1.0.0-alpha<insert number here> dependency you can either require om.core or om.next.

[matanox]

Thanks a lot!

[matanox]

Looking forward to om.next too :-)
Any estimate when it's stable or not alpha/beta any more?

[anmonteiro]

If you have any more questions, swing by the #om channel on the Clojurians Slack. You can get an invite at http://clojurians.net/

[matanox]

Sure

[anmonteiro]

Closing as the question has been clarified.

[matanox]

Thank you :)

On Tue, Sep 27, 2016 at 2:27 AM, António Nuno Monteiro <
notifications@github.com> wrote:

Closing as the question has been clarified.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#765 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AEw744jtcsDWf-Kwm27O84vauPLGhHJZks5quFT9gaJpZM4J8cY7
.