4 ms·

Blame communities and past lack of OSS spirit. E.g. Clojure CLR is doing well, Scala kind of missed the opportunity to win C# devs with their CLR version by aba

by CmonDev 12y ago

Blame communities and past lack of OSS spirit. E.g. Clojure CLR is doing well, Scala kind of missed the opportunity to win C# devs with their CLR version by abandoning it. CLR is the enabler, not implementator.

k__ 12y ago
> Blame communities and past lack of OSS spirit The communities aren't to blame, but Microsoft. Like you said, the past lack of OSS spirit. But maybe things are changing now :)
moomin 12y ago
The thing is, ClojureCLR is a demonstration of of exactly what's wrong with the CLR: it isn't Clojure. Instead it's a language with similar decisions and similar syntax but slightly different semantics.
- joshuacc 12y ago
  Would you say that is true of ClojureScript as well? If not, what sort of differences are there in ClojureCLR?
  - nickik 12y ago
    The problem with ClojureCLR is not technical, its just that most people dont care about it. There are some things moving there but not anywhere close to Clojure or ClojureScript. Clojure has never, ever been about equality between diffrent versions, the were always meant to be simular but diffrent when the platform is diffrent.
    - moomin 12y ago
      I think you're getting mixed up. ClojureCLR demonstrates that CoreCLR doesn't deliver on its intended functionality, not that Clojure's approach is wrong. Indeed, Clojure's approach is dead on: don't even try to make platforms compatible. With that said, I'd like a better lib story between Clj and Cljs.
      - nickik 12y ago
        > I think you're getting mixed up. ClojureCLR demonstrates that CoreCLR doesn't deliver on its intended functionality What do you base this on? I have not heared major complaints, I clearly remember Rich saying that it was not technical early on. > With that said, I'd like a better lib story between Clj and Cljs. They are working on feature expression, that should help.

4 ms·

Blame communities and past lack of OSS spirit. E.g. Clojure CLR is doing well, Scala kind of missed the opportunity to win C# devs with their CLR version by aba

by CmonDev 12y ago

k__ 12y ago
> Blame communities and past lack of OSS spirit The communities aren't to blame, but Microsoft. Like you said, the past lack of OSS spirit. But maybe things are changing now :)
moomin 12y ago
The thing is, ClojureCLR is a demonstration of of exactly what's wrong with the CLR: it isn't Clojure. Instead it's a language with similar decisions and similar syntax but slightly different semantics.
- joshuacc 12y ago
  Would you say that is true of ClojureScript as well? If not, what sort of differences are there in ClojureCLR?
  - nickik 12y ago
    The problem with ClojureCLR is not technical, its just that most people dont care about it. There are some things moving there but not anywhere close to Clojure or ClojureScript. Clojure has never, ever been about equality between diffrent versions, the were always meant to be simular but diffrent when the platform is diffrent.
    - moomin 12y ago
      I think you're getting mixed up. ClojureCLR demonstrates that CoreCLR doesn't deliver on its intended functionality, not that Clojure's approach is wrong. Indeed, Clojure's approach is dead on: don't even try to make platforms compatible. With that said, I'd like a better lib story between Clj and Cljs.
      - nickik 12y ago
        > I think you're getting mixed up. ClojureCLR demonstrates that CoreCLR doesn't deliver on its intended functionality What do you base this on? I have not heared major complaints, I clearly remember Rich saying that it was not technical early on. > With that said, I'd like a better lib story between Clj and Cljs. They are working on feature expression, that should help.