It was hand drawn by an artist. Indiana Jones (the obvious inspiration) wore two belts, one for his pants, one for his whip/holster. The code was provided by Rich.
Thanks for the feedback! Flow monitor does now support filters on the process state (and more on that it is coming to flow itself soon). If you were able to use monitor, it shows the channel buffer states, I guess that was not sufficient to guess why values weren't flowing?
Note that newer things are always downloaded less because they have been around less time (lots of people continue using old versions).
Maven stats are available to artifact deployers, but they are useless for
estimating users or community size as downloads are largely from CI servers constantly downloading artifacts for testing. Download numbers are large and seesaw erratically. Unique IP counts are a little more stable but also inflated beyond relevance by CI.
I agree with your critiques, but I still don't think it negates the overall picture I see.
When I was a scientist, we were trained to look at the overall body of evidence when trying to assess a claim. Any individual study has flaws, but when we survey the literature as a whole, do we see many studies confirming a finding? Independent studies presumably don't share the same set of flaws (usually), and the more studies demonstrating something, the more likely it is to be true.
And I just haven't heard any counter-evidence. Are job postings increasing or decreasing? What's the change in MAU for Clojurians? Etc.
I looked for job/social media numbers, but it's hard to get those numbers. If you have better data, I'd love to see it.
Flow is intended for processes with long-running stable topologies. Rich has been thinking about options to "patch" the running topology but it is quite tricky due to the concurrency issues and I'm not sure that will ever be added.
Even though the flow topology is fixed, it's perfectly acceptable for a flow component to use other variable resources and act merely as a coordinator. So you could for example have a process that send data out to an external dynamic thread pool and gets callbacks via a channel.
Rich Hickey actually did a talk called "Language of the System" https://www.youtube.com/watch?v=ROor6_NGIWU way back in 2013 before core.async was even created that lays out a lot of the ideas. It even has a big section explicitly about "flow" which contains the germs of core.async.flow.
reply