Just recently, Om Next added support for server-side rendering. This is a very exciting addition, which greatly improves Om’s fullstack story, making it possible to add considerable performance improvements to your app’s initial render.
On the 6th of September, I had the pleasure to speak at Full Stack Fest 2016 in Barcelona. The talk has been recorded and you can find a link to the video below.
A small number of changes to Om Next makes it possible to use it from self-hosted ClojureScript environments. Read on!
There exist a number of differences between Clojure and ClojureScript, especially concerning namespace declarations and require specifications. Some of these differences have recently been addressed with the introduction of Clojure namespace aliasing (JIRA ticket) and implicit macro loading. A further upcoming enhancement introduces the possibility to :rename referred symbols in dependency specifications.
There are several different options to implement routing in an Om Next application. However, any one of those approaches is not straightforward to accomplish, and often requires more time than one would like to get right. Until now.