Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Indeed, and here I am targeting .NET Framework 4.7.2, because the ecosystem isn't fully compatible with Core.

Plus on UNIX, Java has 25 years of history, not 4 (not counting WIP mono here).



I'm well aware :) just wanted to clarify since this comes up a lot.

I spent most of last year maintaining a Web Forms app. It's no fun. Ironically, there used to be many more CLR languages, because Microsoft paid for their development. IronPython and IronRuby stand out. I wish ClojureCLR weren't dead too.


> I wish ClojureCLR weren't dead too.

A google search would tell you otherwise.

https://groups.google.com/g/clojure-clr/c/2v9xls5hreE

Last commit 6 days ago: Last code change 11 days ago: https://github.com/clojure/clojure-clr/commits/master


I stand corrected. I assumed that the low velocity was a sign it was flagging.


> I wish ClojureCLR weren't dead too

Is there any reason for saying that? Checking the commits history on Github[1], the project seems still alive.

[1]https://github.com/clojure/clojure-clr/commits/master


I don't have a huge amount of insight into the project but the commits over time don't look super healthy: https://github.com/clojure/clojure-clr/graphs/commit-activit...

Either way it's pretty clearly not a core platform for Clojure.


Using your yardstick, ClojureCLR might look like the primary platform if you compare to Clojure proper: https://github.com/clojure/clojure/graphs/commit-activity


As I wrote below, I misjudged the project because of the low activity in its issues. Clearly the projects are not managed through GitHub, which is what I am used to. I made a mistake.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: