> I get DMs, emails, etc regularly with people asking if jank is ready for them to use. I've spoken with founders and tech leads of dozens of companies, at various Clojure conferences and meet ups, who are interested in using jank to solve performance, efficiency, usability, or interop problems with Clojure.<p>I’d be very curious how much interest is people looking to move to a Clojure from non Clojure code, and in those cases what domain they are working in (games?). And also how much is people in jvm Clojure looking / hoping for better performance from a c++ Clojure and in that case also curious what domains they are in (I’d naively expect jvm is better for Clojure webdev performance given jvm is historically optimized for webdev).
"Clojure and Rust were the only two which had real staying power"<p>rephrase in generic terms<p>"Lisp and SML were the only two which had real staying power"<p>These two languages are the pillars of high-level programming languages, period.
From another independent language developer, good luck to you.<p>I know this may not feel constructive but I'm going to say it anyway: the name of the language is a huge turnoff for me. I try to avoid janky things and use the word as a pejorative. It isn't that different to me than naming the language crap.
I love it. Send it!<p>Are you going to build an engine in Jank after you release the language? I think you could do some really interesting things with server-side multiplayer in a clojure-y way.
I wish you good luck. Except for perhaps 2 1/2 years as a paid Clojure developer over the last 20 years, I don’t much use Clojure for the important stuff: my side projects.<p>I have been following your project for a while but haven’t tried getting it installed on macOS yet. Clojure is a cool language and having a native code option is a nice contribution.<p>I also like the “Clojure like” language Hy, or hylang.
<i>I rewrote jank several times, during these eight years, with a different design each time, trying to find something which felt right. I wanted something</i><p>I'll be blunt here, I see it as just a proloned phase. You wanted <i>something</i>, we all wanted that something at some point. You're not the only one who sees problems and thinks "it could be done differently, if", that's why you gather auditory. You'll end up realizing that no language can replace all these years, and that the amount of real useful work that could be done in that time with boring tools is mind-boggling compared to what will ever come out of this optimistically. Every new real job brings some new insight into what could make it less job-y and more fun. These problems never end and most solutions do not fit together. Feeling that something is not right and it could be done more <adjectively> is just part of the job. If you truly believe in it and have a reasonable source of financial stability, godspeed. But I think you might be living an illusion that almost every programming enthusiast had at some point.