Another thing to notice is that JavaFX uses styling similar to how it’s done on the web: with inline styles or external CSS files. You may notice that it can use event maps (in addition to functions) for event listeners to decouple logic from representation. ( defn todo-view [)Īs you can see, it’s a simple function that returns simple data structures: bread and butter of Clojure code. Clojure has cljfx - declarative, functional and extensible react-like wrapper of JavaFX (which I wrote). JavaFX is the largest supported desktop application platform for the JVM. Funnily enough, Clojure’s equality semantics play extremely well with react model: reagent - ClojureScript wrapper of React - outperforms plain React a lot of the time due to optimizations that re-render components only when their inputs change. It brought it’s complexity sure, but also it made creating consistent UI wonderfully simple. React changed UI development for the better. Until recently there were 2 other huge selling points of the web over JVM that are finally getting addressed: react model and app distribution. Clojure’s REPL-aided development with fast feedback loop is perfect for tinkering with UI, as opposed to compile-and-restart-the-app-and-then-navigate-the-UI-to-see-your-change approach of other languages.javascript VMs choke on processing large amounts of data, which leaves them a better fit for advanced interactive forms than compilers or data processing pipelines.
JAVAFX EXECUTABLE WRAPPER FOR MAC OS CODE
browser-based technology struggles to utilize multiple cores in the same VM instance, while Clojure’s immutability by default, concurrency primitives and core.async make writing multi-threaded code a breeze.I think that even though the web is more popular then ever there are still use cases where JVM is a better choice as an application platform, and coincidentally, these use cases align perfectly with Clojure’s advantages over other JVM languages: Countless resources spent on making DOM and Javascript VMsĪs efficient and approachable as possible make it a solid choice for many types of applications despite the historical baggage. With web browsers eating the front-end world it’s a hard choice, especially with tools like Electron allowing to have the same code base for both web and desktop apps. An unexpected journeyĪnother area where JVM is useful is desktop applications. Java is also widely used on Android, but Clojure is rarely a good choice there due to it’s startup time. In practice, it’s mostly used on the backend for servers. What is Clojure’s use case? In theory, it’s any situation where JVM is a reasonable choice, but especially for high concurrency and processing large amounts of data.
0 kommentar(er)
