This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # aleph (1)
- # bangalore-clj (5)
- # beginners (24)
- # boot (113)
- # cider (42)
- # cljs-dev (2)
- # cljsjs (2)
- # cljsrn (3)
- # clojure (37)
- # clojure-austin (4)
- # clojure-brasil (3)
- # clojure-france (55)
- # clojure-greece (15)
- # clojure-ireland (4)
- # clojure-italy (13)
- # clojure-russia (37)
- # clojure-spec (50)
- # clojure-uk (31)
- # clojurescript (49)
- # component (12)
- # consulting (1)
- # cursive (6)
- # datascript (9)
- # datomic (27)
- # editors (2)
- # garden (1)
- # hoplon (18)
- # jobs (1)
- # klipse (25)
- # lein-figwheel (1)
- # leiningen (1)
- # luminus (2)
- # om (53)
- # om-next (8)
- # onyx (5)
- # parinfer (4)
- # perun (4)
- # re-frame (13)
- # remote-jobs (1)
- # ring (1)
- # ring-swagger (3)
- # rum (52)
- # spacemacs (36)
- # specter (13)
- # sql (3)
- # untangled (49)
- # vim (11)
- # yada (9)
@currentoor I'm curious if you'd be willing to mention Untangled in your talk/blog titles? You seem to like it, and I think it would really help us with adoption if it had more of a headline inclusion...e.g. "w/ Om Next, Untangled, and Datomic"
and I think it would save a lot of ppl a lot of pain to know there's an easier route to getting Om Next working than writing emitters for a parser and all of the other plumbing details. So, seems like a win-win
@tony.kay I have a slide with these speaker notes > Probably the part of our stack that this audience is least familiar with. > It’s a lightweight framework and I strongly recommend using it if you’re using Om next. > Makes Om next a lot easier to work with. > We started out without it but added after a few weeks. > It’s written by some very talented Clojure developers. > Does things like provid all the network plumbing and write the Om.next parser for you (and a whole lot more that I don’t have time to go into). > Gives you a lot of well thought out conventions and a clean architecture. > Plus the untangled team is super helpful.
Let me know if there’s anything else you want me to mention on the untangled specific slide.
@jasonjckn if you want to implement a server side SQL for Untangled, this may help you: https://github.com/daveconservatoire/dcex-cljs/blob/master/src/server/pathom/sql.cljs
it's a SQL base code that implements readers for Untangled, this one is for Node.js, but I believe most can be ported
@tony.kay changed the title of the blog post and added an
Untangled tag on it.
If you or anyone else posts on medium it’s probably a good idea to use the
Untangled tag as well.
@tony.kay I just found out about Untangled today. This is so amazing. Thank you so much for your hard work. 😍
I’ve been looking for something that makes Om Next easy. The value propositions over Reagent are just too incredible to ignore for my use case. You just saved me so much time from having to write all this boilerplate:)
I asked a long question in the #om-next channel and @jasonjckn really helpfully and quickly pointed me to this.
Curious — in Tony's Portland Meetup talk he said then you didn’t have support for microservices yet, but that that could be implemented in like ten minutes. I’ve been looking hard into Dockerizing my app. Is there support for this, or would it be easy to implement?:)
@currentoor Where does Sente come into play? (I didn’t see anything explicit about Untangled in that post).
Sente is what we used to push data from the server to browser clients. Should be in two of the code examples.
Does Untangled use Ring? Sorry if that’s a stupid question lol I’m just trying to learn all this stuff and the state of Om Next dev.
I’m sort of a beginner developer. I’ve only been learning software for like 7 months. But the Clojure world won me over.
Oh cool! My unsolicited advice is just to go slow. There’s a lot to learn and a shaky foundation, from trying to do too much too quickly, is not fun at all.
@keatondunsford Love your enthusiasm 😄 I'd have to re-watch my talk to know what I was referring to on microservices. Can you point me to the timestamp where I say that?
@currentoor Cool! I'm sure everyone here that's using it (particularly commercially) appreciates the efforts to get more ppl using it. Future proofing sure is nice.
I just tried to create a new project using the untangled template, and got an error:
ok, I just figured that the
 must be omited, I suggest we change the example, it's confusing since
[:devcards] looks like valid clojure snippet
@wilkerlucio this one is currently better (just clone it): https://github.com/awkay/untangled-template-workspace
@keatondunsford oh, multiple remotes. Yeah, that is pretty simple, just need to make the networking be a map of networking objects keyed by remote. Om takes care of most of the rest.
it would be a relatively minor refactoring. We would want to decide if the serial queue for network requests should be a singleton, or one-per-network channel. Perhaps that should be configurable. Anyway, future work. We haven't needed it yet, but would be glad to help anyone understand it that wanted to implement it
@tony.kay did you have any issues with Cursive not being able to generate the stubs on this project?
don't remember having that problem no...but I do remember having that problem with something...OH beta doesn't work right. I had to turn off EA updates
@anmonteiro thanks, I found that, but since it was installed I think I can't revert, I'm going to just re-install it
[:option] indicates that it is optional, and the
-- is because lein will assume any arguments before a
-- are for it and not the template
Common Quotes in http://www.tfug.org/helpdesk/general/man.html