om.core and beta2

[danielsz]

Hi,

I've been using om.core happily for years now. I mean the original version of Om, in opposition to Om.Next. I was also happily updating Om in my dependencies because om.core didn't change and everything kept on working. This allowed me to leverage om.core with more up to date versions of React.
I was happy to see the release of beta2 because it comes with React 16 which solves a bug in React 15.x (I'll spare you the details because this is unrelated to Om). Unfortunately, this time it didn't go well due to the deprecation of React.createClass.
Going forward, is there any chance to keep users like me happy?

[zentrope]

I just hit this as well. I have a bunch of old prototypes and concept apps I like to keep up to date, but it looks like the time has run out for om.core.

[wilkerlucio]

I recommend you guys check Fulcro, right now it's a fork of om.next, om.next is not likely to be maintained, so Fulcro has a lot of improvements, a lot more docs and is constantly improving.

[danielsz]

That may very well be.

We are interested to use the same API as om.core, but on the latest React.
I started using Om years ago, and I would like to continue using it. om.core is a thin wrapper over React, om.next is a different beast (broader and more ambitious scope).

[wilkerlucio]

Humm, gotcha, yeah, if you want to use the om.core then you might have to do some fixes yourself, Fulcro only has the om.next parts, but IMO it's so much better, it's harder to understand for sure, but once you do, there is no way back :)

[danielsz]

Duly noted. Thanks.

[danielsz]

For anyone interested, I've brought the modifications myself so as to be able to use om.core as explained above. No guarantees beyond "it works here".

[org.danielsz/om "1.0.0-beta4-SNAPSHOT"]

[timds]

Hi @wilkerlucio , I'm confused about the current status of om.next. Commits are still being made, including an apparent transition from alpha to beta. @swannodette , do you have plans to abandon or stop maintaining om.next, or are things just going slow and steady?
Thanks,
Tim

[wilkerlucio]

@timds, I don't know what David plans are, but for what I've seen it's just about getting it to stay working, the latest changes were related to fixing breakages due to the new cljs version. But feature wise it's been a long time since the latest one.