This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # adventofcode (153)
- # announcements (29)
- # architecture (6)
- # babashka (5)
- # beginners (197)
- # calva (71)
- # clj-kondo (27)
- # cljfx (4)
- # cljs-dev (33)
- # cljsrn (1)
- # clojure (52)
- # clojure-australia (5)
- # clojure-boston (1)
- # clojure-europe (38)
- # clojure-france (1)
- # clojure-hungary (5)
- # clojure-italy (1)
- # clojure-nl (19)
- # clojure-uk (5)
- # clojurescript (12)
- # conjure (4)
- # core-async (3)
- # cursive (21)
- # datalog (70)
- # datomic (32)
- # deps-new (8)
- # emacs (79)
- # events (2)
- # fulcro (15)
- # graalvm (15)
- # leiningen (2)
- # lsp (5)
- # minecraft (1)
- # off-topic (37)
- # polylith (11)
- # re-frame (9)
- # reagent (1)
- # reitit (3)
- # releases (1)
- # reveal (2)
- # shadow-cljs (35)
- # spacemacs (1)
- # tools-build (4)
- # tools-deps (55)
- # vim (11)
- # xtdb (6)
New version of https://github.com/msolli/proletarian, a durable job queuing and worker system for Clojure backed by PostgreSQL: https://github.com/msolli/proletarian/blob/main/CHANGELOG.md#1054-alpha---2021-12-02
This version features some improvements with how certain exceptions are handled, as well as some API polish. There is one breaking change in that regard: The
retry-strategymultimethod has been replaced by a
:proletarian/retry-strategy-fn option for
Follow-up in #proletarian.
good news, everyone: Slack has sponsored a Pro account for this fine community :-)
thank you @U0509NKGK for pushing on this: https://twitter.com/RobStuttaford/status/1465577349018226688 🙏
Note: it is for one year only -- we have to reapply each year (which we shall do).
This is huge! Just last night I had a Q and I knew it would have been asked in Clojurians…3 pages deep I found it! Blessings 🙏
She's not a Clojurian so may never see this, but public thanks to Kiere Shaffer from the Asheville dev community, who clued us in that tweeting directly at the Slack CEO had worked for another large community she's part of. 🙏
Wow. Did not expect this outcome. Awesome job @U0509NKGK ! This has been a long time coming. As a side note, here is the grunt-level response I received today from slack support:
: ) +1 for skipping up the org chart to the absolute top @U0509NKGK :punch:
If your question is about pricing for community teams then I'm so sorry but the answer would still be the same as when you last chatted to us. There is currently no pricing plans that differ from our business plans for community workspaces.
https://vlaaad.github.io/reveal/ v1.3.250 and https://vlaaad.github.io/reveal-pro v1.3.293 are released! This release brings a bunch of improvements to how you can interact with Reveal from your IDE, which unlocks a "sticker overlay" development workflow that is described in this introductory blog post: https://vlaaad.github.io/reveal-stickers Follow up in this thread or in #reveal!
the sticker idea looks really neat! here's a few thoughts:
• for me, the caption is covered up by the player video controls
• the text in the videos is really small and hard to read unless I zoom in or go full screen
• when I first saw the custom stickers example, I thought it would take the comment block:
(start!), (slurp) (stop) and automatically turn that into a UI. That might be a cool idea!
That looks really awesome, love the idea! This looks like the killer feature that will make me start using reveal
Haven't even tried it yet, but I'm already thinking that a per project setting that restarts the same stickers of the last session would save a lot of time arranging them in the right spots
ah ok. I have some improvements in mind for my ffmpeg wrapper, so I'm curious what people are currently using.
@U02EMBDU2JU thanks! I thought about automatically restored stickers. There are some problems with them that I couldn't solve yet — they accept any object in the JVM as an argument. It might be impossible to reconstruct these objects between JVM runs. For example, at the first JVM run you start a sticker that shows the status of database connection. Then you remove SQL dependency from the app and restart the JVM — how should Reveal behave?
@U47G49KHQ I haven’t looked at the way you do your data connection, but I’m thinking stickers would be the most useful when watching an atom or a var. So reveal would restart with a “watch” of some kind for that var in that name space. If it never shows up again the user can always close that sticker. I’m thinking of re-frame apps that would want to watch the db atom or like you said, a db connection or even an “in function” def for debugging. if i just tap a map into it it’s probably not as interesting to see the same data on the second run, but who knows, the user can always close it.