Note that Clojure also supports OO style with rotocols http://clojure.org/protocols and multimethods http://clojure.org/multimethodsp in fact stuff like Om https://github.com/omcljs/om/wiki/Quick-Start-(om.next) is fairly object oriented in nature.
Clojure is also very fast thanks to running on the JVM and it supports type hinting. There's also core.typed for static typing support.
In Common Lisp Koansomcljs
om
Clojure2013–2026
omcljs / om
om
ClojureScript interface to Facebook's React
61Distinct people
67Mentions
0Explicit recommenders
6.6KGitHub stars
What to know before exploring
What it is
ClojureScript interface to Facebook's React
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
- reagent-project/reagent · linked in 3 of the same discussions
- ckirkendall/kioo · linked in 2 of the same discussions
- r0man/sablono · linked in 2 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 9:02:44 AM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year67 dated mentions
Observed mentions: 2013-12-22 19:43:54 UTC to 2026-02-25 19:11:18 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2013 | 2013-01-01 00:00:00 UTC | 2014-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2014 | 2014-01-01 00:00:00 UTC | 2015-01-01 00:00:00 UTC | 31 | 1 | 30 |
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 18 | 5 | 13 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 7 | 0 | 7 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 4 | 0 | 4 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 3 | 0 | 3 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 1 | 0 | 1 |
From the project README
An excerpt from the repository, fetched Nov 13, 2026.
Read the project’s introduction
Om
NOTE: This project is no longer under active development. If you'd like to use
a library that's well maintained that was inspired by some of the ideas
presented here see Fulcro
A ClojureScript UI framework and
client/server architecture over Facebook's
React.
Om UIs are out of the box snapshotable and undoable and these operations have
no implementation complexity and little overhead.
Om borrows ideas liberally from Facebook's
Relay and Netflix's
Falcor with a dash of inspiration from
Datomic pull syntax to avoid the typical
incidental complexity that arises from client/server state management.
Dependency Information
Latest release: 1.0.0-beta1
Leiningen and Boot
dependency information:
[org.omcljs/om "1.0.0-beta1"]
Maven dependency information:
<dependency>
<groupId>org.omcljs</groupId>
<artifactId>om</artifactId>
<version>1.0.0-beta1</version>
</dependency>
Example
(ns example
(:require [goog.dom :as gdom]
[om.dom :as dom]
[om.next :as om :refer [defui]]))
(defui Hello
Object
(render [this]
(dom/h1 nil "Hello, world!")))
(def hello (om/factory Hello))
(.render js/ReactDOM (hello) (gdom/getElement "example"))
Tutorials
There is an Quick Start tutorial that will introduce you to the core
concepts of Om
here. There are
also a variety of other guides here.
Documentation
There is documentation here
Contributing
Please contact me via email to request an electronic Contributor
Agreement. Once your electronic CA has been signed and returned to me
I will accept pull requests.
Community
If you are looking for help please get in touch either on the
clojurians.slack.com #om channel or the
om-cljs Google Group.
References
Worlds: Controlling the Scope of Side Effects
A Functional I/O System
Directness and Liveness in the Morphic User Interface Construction Environment
Learnable Programming
Relay
Falcor
GraphQL
Datomic pull syntax
Copyright and license
Copyright © 2013-2017 David Nolen
Licensed under the EPL (see the file epl.html).
Read the full README on GitHubWhat Hacker News says
18 sourcesIt sounds like you're asking some of the same questions that David Nolen is asking (and answering) with Om Next. If you haven't been following that process, you might find it informative. You can find some details about Om Next on the wiki https://github.com/omcljs/om/wiki and several talks by David are available YouTube.
In Whats the Point of GraphQL and Falcor?- Intro by David Nolen: https://www.youtube.com/watch?v=ByNs9TG30E8
- Github docs: https://github.com/omcljs/om/wiki/Quick-Start-%28om.next%29
In Ask HN: Suggestions on good resources to get started with 'OM.Next'Lots of new stuff in Om Next. Unlike Relay and Falcor we have recovered HTTP caching https://github.com/omcljs/om/wiki/Remote-Synchronization-Tut.... And due to the redesign Om Next now has a really fantastically simple automated testing story https://github.com/omcljs/om/wiki/Applying-Property-Based-Te...
Happy to take any questions.
In Om Next Quick StartApplying Property Based Testing to User Interfaces
1 points · Open discussion> Why the new declarative query language for fetching attributes (columns) from objects (tables)?
SQL isn't very composable- It was the right idea, but there's been a lot of progress in the last 50 years on how to traverse a database. It is all string-based, and it lacks a "pull syntax" (i.e. after the query completes, give me this graph-represented chunk of the result)
> Why build yet another transport mechanism on the top of HTTP, when there are so many to choose from already?
Relay is mostly agnostic on what mechanism is used to fetch results.
> Oh, my god, boilerplate everywhere! What is this, Java?! /s
Yeah, it's kind of awkward to do this stuff in Javascript- Look at what people are doing in more flexible languages, like here https://github.com/omcljs/om/wiki/Quick-Start-%28om.next%29
In Facebook Relay: An Evil And/Or Incompetent Attack on RESTSome early ideas have already hit the repo[1]. David Nolen has been focused on ClojureScript bootstrapping work[2] of late, but I expect he'll get back to Om Next in the coming weeks.
1. https://github.com/omcljs/om/blob/master/dev/om/dev.cljs
2. http://swannodette.github.io/2015/07/29/clojurescript-17/
In Netflix Releases Falcor Developer PreviewHow is there no mention of Om[1] or Reagent[2]?
[1] https://github.com/omcljs/om
[2] https://github.com/reagent-project/reagent
In Modern ClojureScriptI'm somewhat new to web dev and new to functional programming. Can someone tell me how this is fundamentally different that ClojureScript + OM (https://github.com/omcljs/om) ?
In Developing Web Applications with HaskellIt's extremely serious.
The deployment is the very well understood JVM and standard web servers. There's a common HTTP middleware framework (Ring), lots of choices for HTML generation and ClojureScript allows some code-sharing with your client side (compiles to JS).
On the back-end, you could use any Java library. On the front-end, you could use any JS framework (e.g. see https://github.com/omcljs/om)
In Running Lisp in ProductionThis is the approach that many ClojureScript frameworks take, and I find it to be a much more elegant approach than Flux proper.
You use a single, immutable data structure to store your application state, and components use functional lenses to look into the part of the state they're dependent on and listen for changes.
In doing so, you get a free application history stack and deltas (for undo/redo, offline/online sync and some powerful debugging capabilities), extremely efficient shouldComponentUpdate implementations for all components, and opportunities for many more advanced optimizations like batching updates for rendering on requestAnimationFrame.
Check out Om if you'd like to take a look at the original ClojureScript implementation, or Morearty.js if you're interested in a pure JS alternative.
https://github.com/moreartyjs/moreartyj
Read the rest
Showing the 15 most recent of 18 sources. Enable JavaScript to search and browse every indexed mention.