News for hackers. Stuff that matters.

A comment on Clojure Async Flow Guide. Parent comment

Re:Clojure Async Flow Guide by pjmlp on Monday August 18, 2025 @05:03AM (#44938686)
Indeed, JVM and .NET are the only two major ecosystems out the whole Xerox PARC ideas[0], and the reason that to this day they are my two main workhorses, plus JS runtimes, because Web.

[0] - Technincally Objective-C and Swift could also be considered, but they lack the industry wide adoption, as many cool tools only exist in Apple land.

[ Parent | on HN ]
Re:Clojure Async Flow Guide by raspasov on Monday August 18, 2025 @09:54AM (#44940627)
I agree.

Swift is quite good. I assume the tooling is catching up to Objective-C. It has been a couple of years since I had to solve something with Swift.

Any reason, apart from outside requirements, to pick the .NET CLR over the JVM as a runtime in your experience? Outside of library/framework support, which I've heard is good with the CLR.

How's the garbage collector with the CLR?

[ Parent | on HN ]
Re:Clojure Async Flow Guide by jiehong on Monday August 18, 2025 @10:46AM (#44941219)
Today the CLR has better SIMD and struct alignment than the JVM.
[ Parent | on HN ]