We are having a casual Get Together this Thursday 12th of February (I know it's short notice). No talk lined up, just casual chat.
clojure.berlin/events/2026-...
We are having a casual Get Together this Thursday 12th of February (I know it's short notice). No talk lined up, just casual chat.
clojure.berlin/events/2026-...
WCOJ meets DBSP. This is the post I wanted to get at when starting the series. finnvolkel.com/wcoj-wcoj-me...
WCOJ meets DBSP. This is the post I wanted to get at when starting the series. finnvolkel.com/wcoj-wcoj-me...
The 4th post in the WCOJ series. An intro to DBSP, Z-Sets and connections to EDN Datalog indices. This will set us up for a WCOJ meets DBSP algorithm. finnvolkel.com/wcoj-dbsp-zs...
The 4th post in the WCOJ series. An intro to DBSP, Z-Sets and connections to EDN Datalog indices. This will set us up for a WCOJ meets DBSP algorithm. finnvolkel.com/wcoj-dbsp-zs...
Idea from a friend of mine. People who set off fireworks should be drafted immediately.
In section "3.1.2 A batching optimization to reduce memory" of the paper you mentioned, you seem to restrict the size of the extensions `propose` returns, but this then means batches might be quite different in size.
> benefit from imposing a limit on the tuples to produce at once (currently: 100M)
^from you post. When doing the joining of `a`, you don't know how many tuples you get if all variables have been unified. I was mainly wondering how you decide to cut your batches when being at the `a` level in GC.
Thanks. I also "stole" the GC interface (giving credit of course) from you old post. www.frankmcsherry.org/dataflow/rel...
I meant (2.). If the variable order is (a,b,c), naive GJ will produce all a's before looking at b's, so I was wondering what you do in datatoad (or elsewhere) besides potential cardinality estimation.
Hey. Love that you are blogging on WCOJ again. I was wondering how you deal with the limit on the tuples produced in GenericJoin. In Leapfrog this seems quite easy as you are producing the tuples one at a time at the bottom, but in GenericJoin you need (?) to take some decisions higher up or not?
The 3rd post in the WCOJ series. Implementing some logical datalog connectors in the context of GenericJoin. finnvolkel.com/wcoj-datalog...
The 3rd post in the WCOJ series. Implementing some logical datalog connectors in the context of GenericJoin. finnvolkel.com/wcoj-datalog...
The second post in the series is on an actual implementation of a WCOJ algorithm. finnvolkel.com/wcoj-generic...
The second post in the series is on an actual implementation of a WCOJ algorithm. finnvolkel.com/wcoj-generic...
I started to write a blog series on worst-case optimal join finnvolkel.com/wcoj-graph-j...
Wrote a blog post about continuation-passing style in @xtdb.com.
finnvolkel.com/continuation...
I know a bit old your posts. I also found this blog a really good resource for understanding WCOJ www.frankmcsherry.org/dataflow/rel.... It implements the one from arxiv.org/abs/1310.3314.
I confusingly said it would be next Wednesday. It's Wednesday in a week (23.7) from now.
We are having a Berlin Clojure meetup next Wednesday. The topic is going to be clojure-mcp, so bring your 💻 for some experimenting.
clojure.berlin/events/2025-...
Evaluation of a paper from 1977 arguing for handling events as first class members in data- defined systems. I wish people would have listened to this guy at the time.
xtdb.com/blog/update-...
To our US customers: Yesterday, the Trump Administration announced that they will be ending the de minimis exemption for all shipments from Hong Kong and China on May 2. They also raised the minimum import tax on products made in China or Hong Kong to 54% of the sale price. While we design our keyboards in the US, like most consumer electronics companies we manufacture our products in southern China. These new rules will drastically increase how much it costs you to buy our products. (1) If you've been considering buying anything we make, now is the time. According to the new policy, you will owe a 54% import tax on any package from Keyboardio that arrives after May 1. Once the de minimis rule is gone, no sale we can offer will ever make the Model 100 or Atreus as inexpensive as it is today. Starting in May, US customers will be charged $188 in new taxes (tariffs) on a Model 100 + additional customs clearance fees. The new US taxes on the Atreus will be $80 + additional customs clearance fees. We're really proud of these keyboards—we designed them to be the most comfortable tools to help you be productive, and to help you enjoy the experience of typing. We think they're worth the investment. We don't think a 54% tax is reasonable.
I expect to be getting a lot of emails like this soon. This one is from @s.ly and @keyboard.io about the tariffs.
Such a pointless destruction of US small businesses.
I found this to be a really good article harper.blog/2025/02/16/m...
@xtdb.com beta6 is out today 🚀
Containing the sorts of changes that don't make for very exciting release-notes, but all the little things you'll appreciate when you're actually working with it day-to-day/deploying it into production.
No buzzwords this time I'm afraid!
xtdb.com/blog/v2beta6
🚀 Need accurate reporting and seamless data corrections in your #Database?
📹 See how XTDB's bitemporality makes auditing and historical queries effortless. Correct mistakes, track changes, and retrieve past states—all with simple SQL queries.
youtu.be/gKXpljRpHlo
Blogged: "The Missing SQL Sub-queries"
SQL's had sub-queries since SQL:92 - but it's still a challenge to return properly nested data through SQL queries.
#XTDB has first-class support for nested values, as well as `NEST_ONE` and `NEST_MANY`, which fill this gap:
xtdb.com/blog/the-mis...
Just wanted to mention that the links to the companies mentioned in the report do not work. Keep the great work up.
Exciting news! clojure.berlin is live!
Join us for a Clojure GetTogether the 19.12 at Trespassers. #Clojure #Berlin