This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # admin-announcements (1)
- # alda (44)
- # aws-lambda (6)
- # beginners (8)
- # boot (187)
- # capetown (5)
- # cider (25)
- # cljs-dev (24)
- # cljsrn (93)
- # clojure (45)
- # clojure-austin (9)
- # clojure-canada (2)
- # clojure-greece (1)
- # clojure-mexico (3)
- # clojure-poland (3)
- # clojure-russia (1)
- # clojure-spec (12)
- # clojure-uk (13)
- # clojurescript (86)
- # cursive (9)
- # datascript (3)
- # datomic (32)
- # defnpodcast (4)
- # devcards (23)
- # editors (3)
- # emacs (5)
- # hoplon (27)
- # immutant (3)
- # lein-figwheel (9)
- # leiningen (4)
- # luminus (10)
- # om (32)
- # onyx (2)
- # other-languages (1)
- # perun (1)
- # protorepl (8)
- # re-frame (13)
- # reagent (2)
- # remote-jobs (2)
- # ring (3)
- # spacemacs (4)
- # spirituality-ethics (3)
- # test-check (16)
- # untangled (65)
- # yada (50)
We launched our public beta today built using Untangled, gave the framework a shoutout in the comments. https://news.ycombinator.com/item?id=12165682
@tony.kay and friends thank you so much for making this modern lisp stack totally accessible!
@currentoor: I might be an idiot but I can't seem to get to your site from the hacker news link, found it on google though. Is the entire thing Untangled?
@shaun-mahood: oh it's silly that the HN post doesn't link to the actual product, I think one of our marketing people posted it.
We originally built the prototype in vanilla Om next. Then started with Untangled in April.
@currentoor: Very cool. I'd be very interested in any info you can share about the graphing and dashboards in there, they look excellent.
@shaun-mahood: I'm happy to answer any questions. We're planning on writing a blog post going over our experiences.
@currentoor: I’d sign up for a free trial to play around if I could! looks fantastic
@currentoor: Thanks, looking forward to the blog post. I bet it will be really, really nice to maintain.
@shaun-mahood: it was pretty straightforward to wrap, we used some lifecycle examples that looked very similair to what @tony.kay used for his d3 react component (i think that was posted on the om channel awhile back).
@currentoor: cool stuff, looks good! I’d love to see those chart components open sourced
@paul4nandez: it's just some syntactic sugar around
Just rooting for a wider adoption of Om Next. Pretty sure everything we can get out there to feed the (still tiny) ecosystem is very welcome
yeah that would be cool, we certainly had more fun with this stack than any other we've worked with
Out of curiosity, was this the first Clojure project you have undertaken at the company, or was there already some Clojure traction?
We already had some Clojure parts in our stack (for example the underlying metrics service we're grabbing most of our data from)
Well, it certainly still took a lot of pushing from @currentoor to get us to try it. 🙂
@shaun-mahood: yeah i had to sell my soul and take a second mortgage on it get this project approved!
I love that you guys pushed a public commercial product beta out in 4 months. That speaks volumes I think.
Initial traction was gained by getting a commitment to let us try a week long spike and see how far we could get. We were able to get a workable enough demo that it seemed like a viable solution
I think you guys should announce on the #C06DT2YSY channel as well. I think it could help the general crowd of om-next interested users to raise an eyebrow towards Untangled as a simplification for getting going.
I think you've beat everyone else to the punch on having a commercial om-next full stack app...including us 😕
(actually we do have an internal beta going on with real clients, but it isn't public facing)
Is there a way to query for all the entities of a particular ident? Like
[:dashboard/by-id *] vs
@currentoor: that’s one of the cool untangled nuggets — if a keyword is not part of a join, we assume it’s at the top of the app state and we return whatever is at that key
FWIW, it’s what Om will do too if you call
db->tree, which is what Untangled uses, IIRC
interesting, we treat it as a separate case in our custom read
untangled.client.impl.om-plumbing/read-local, but maybe we don’t have to
you treat it differently because the parser dispatches on top-level keys so you don’t really have the