Love this, do you have an benchmarks around potential performance improvements over JVM clojure?
There are benchmark throughout my blog posts, but nothing which we run continuously yet, or which is easy for others to run. We'll get there!
I quit my job to work on my programming language
31–35 of 35 posts
Re: I quit my job to work on my programming language
#32From another independent language developer, good luck to you. 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.
Like CockroachDB? Such names are memorable--you've already memorized it.
"Testacular" comes to my mind too
Re: I quit my job to work on my programming language
#33Earlier quoted context omitted.
J is my name though!
Jet Jazz Just Jupiter Jalapeno JNet and similar Jumbo Jambo
I hate it when people name things random fun or clever words. It’s got to have some thought behind it. A name isn’t just a random label. That’s how you get variables all over your codebase named “stuff” and “thing” and “foo”.
Re: I quit my job to work on my programming language
#34Love this, do you have an benchmarks around potential performance improvements over JVM clojure?
Fwiw, there is an LLVM implementation of Scala you might be able to get a general sense from. It surprised me to see that in some cases a hot JVM is actually faster than native-compiled code (although PGO/BOLT can probably get it closer.)
Re: I quit my job to work on my programming language
#35This is the dream of any system's programmer. Also their demise...