This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-06-03
Channels
- # announcements (6)
- # babashka (14)
- # beginners (17)
- # biff (3)
- # calva (19)
- # circleci (3)
- # clj-on-windows (1)
- # cljdoc (21)
- # cljs-dev (6)
- # clojure (119)
- # clojure-australia (2)
- # clojure-europe (28)
- # clojure-france (3)
- # clojure-norway (12)
- # clojure-survey (2)
- # clojure-uk (7)
- # clojurescript (25)
- # core-typed (1)
- # cursive (11)
- # datomic (53)
- # emacs (14)
- # events (1)
- # gratitude (1)
- # holy-lambda (21)
- # integrant (2)
- # jobs (1)
- # jobs-discuss (3)
- # juxt (3)
- # kaocha (1)
- # lsp (17)
- # nbb (14)
- # off-topic (25)
- # pathom (11)
- # re-frame (24)
- # releases (1)
- # remote-jobs (2)
- # rewrite-clj (10)
- # shadow-cljs (11)
- # sql (3)
- # tools-build (6)
- # tools-deps (83)
- # vim (26)
- # xtdb (10)
Got curious about how the number of respondents to the State of Clojure survey has changed over the years; looks like it’s held pretty steady starting in 2015 (other than the skipped year in 2017): [Note from @alexmiller which I fully endorse: ‘keep in mind that the survey has been open for different amounts of time every year, advertised in different ways, etc. so these are at least different kinds of apples you’re comparing’]
I wonder how that compared to community surveys for other languages in the same part of their lifetime -- if it happens elsewhere?
It looks like rapid growth in the first decade the language existed and then stability -- in terms of active, engaged community -- for the next decade.
keep in mind that the survey has been open for different amounts of time every year, advertised in different ways, etc. so these are at least different kinds of apples you're comparing
Also the graph doesn't explain the cohort; whether it's mostly the same people each year, or mostly new respondents each year I, for example, did not respond for a couple of years (maybe three) partly because I had nothing new to say, which was mainly because I wasn't doing anything actively with Clojure. I suspect there is a healthy proportion of first-time respondents.
I've seen this asked a few years now. Perhaps it would be a good question for the next survey, to ask how many previous surveys you have participated in.
Regarding 2014. My gut feeling is that organic marketing played a huge role back then. Lots of good content: Carin Meier with Robots, Tim Ewald's excellent talk, InfoQ Clojure content,...
I think that what happened is Clojurians Slack became a place to advertise the survey
Alex: > so these are at least different kinds of apples you’re comparing Absolutely! I’ll add a disclaimer now that few conclusions can be drawn from this — I was curious about it as a datapoint, but not one that singlehandedly explains anything.
The strangest crash issue I've seen in a while: https://github.com/PEZ/chromium-crash-mystery TL;DR: Chromium browsers crash on my machine for some very minimal HTML.
I believe I have very similar hardware to your machine, but no crash for me
Also M1 Max, 10 core, 32G, just 14"
I tried on my windows machine with: Internet Explorer (All compability versions), Brave, Firefox, Firefox Dev, Opera, Chrome and Edge (Chromium Version). So far no crash 😄
I filed a bug report. Let's see if they can make something out of it: https://bugs.chromium.org/p/chromium/issues/detail?id=1332445
I have a very naive question I don't know how to answer. Given something like Dart/Flutter (and #clojuredart 🙂), and assuming its performance is close to native, why build a web app and deal with browser limitations? (Dart can also target the web, but never mind.) One thing that comes to mind is that one doesn't need to download and install a web app (not an issue with some types of apps, I'd argue). Another thing is simpler updates. What else?
(repeating some of what you said but things that jump to mind): • ease of updates, just refresh the browser • easy "installation", users already have a browser • Accessible across devices
I think reach is really the big one. No install, working on everything that has a browser.
> assuming its performance is close to native I've heard that is very much not the case with Dart, that it stutters at 5 fps for even simple things like a button with a glow animation.
Thanks everybody. None of those are major trade-offs in my view - definitely worth thinking about the Dart/Flutter route. > I've heard that is very much not the case with Dart, that it stutters at 5 fps for even simple things like a button with a glow animation. > Not what I found with some quick Googling. Seems to be fairly close to native, but definitely better than React Native. Do you have a source?