6 ms·

Can anyone compare this to Clojure?

• t_crayford 17y ago
  Ioke has lots of mutable state (rather than Clojure's strict lockdown on mutable state). Ioke isn't concerned at all with concurrency (which Clojure is). They both have macros, and ioke's syntax looks nicer to non-lispers than clojure's. Ioke (iirc) is considerably slower than clojure, and kinda difficult to optimize.
  • smikhanov 17y ago
    Do you have any idea why it's hard to optimize Ioke?
  • viraptor 17y ago
    > Ioke (iirc) is considerably slower than clojure, and kinda difficult to optimize. Throughout last year Ola mentioned many times in his blog, that he's not concerned with speed optimisation at this point, but mainly features. I'm not sure about the "hard to optimise" part... Also if you look at the Ioke manifesto[1]: > This is really the full manifesto of Ioke, if you ever had to choose just one. In any situation where I have to choose between expressiveness or performance, expressiveness is always the answer. Don't remember him mentioning anything about concurrency though. [1] http://olabini.com/blog/2009/05/the-ioke-philosophy/ http://olabini.com/blog/2009/05/the-ioke-philosophy/
  • stevedekorte 17y ago
    Immutable state is not necessary for scalable concurrency. Exhibit A: The Internet.
• xtho 17y ago
  "Ioke" != "Clojure" => true (not (= "Ioke" "Clojure")) => true
• viraptor 17y ago
  This might be a bit related: http://olabini.com/blog/2009/01/ioke-is-not-a-lisp/ http://olabini.com/blog/2009/01/ioke-is-not-a-lisp/ - Ioke -vs- Lisp post by Ioke's author.