Good question. I think it's important to address this seriously.
Om.next is a very different architecture from Om today. Many companies are using Om, and David has assured everyone that it will continue to exist <https://twitter.com/swannodette/status/604085574803263488>. That said, it's unsure how much will still apply in Om.next. It will definitely have components, the component lifecycle, the virtual dom, all of which we will cover in the course. The course covers cursors and atoms for storing state, which will not be used in Om.next (as far as we can tell). And Om.next will manage your interaction with the backend, which won't be possible for everyone. We don't know how long it will take for Om.next to be production ready. Meanwhile, more and more people are coming to Om and developing code using what's available today. I think today's Om will still be used for a long time. As far as making a course for Om.next, that will have to wait for it to be released. Thanks Eric -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to [email protected] Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
