3 ms·

Do you worry about this when you write Python/Ruby/Clojure/Scala/etc?

• JasonFruit 12y ago
  Not as much, because for at least Python — I don't use the others much — the community is mostly united around a single implementation. Scheme's more varied landscape makes me more concerned with writing portable code.
  • brudgers 12y ago
    By 'a single implementation' you mean Python 2 or Python 3, right? ;> In seriousness, what sort of portability issues do you see with Racket code? Racket has 32 and 64 bit flavors for *nix, OSX, and Windows. It offers backward/sideways/forward compatibility with R5RS and R6RS. Locked away in the cellar like a crazy aunt, it even includes mutable lists. http://docs.racket-lang.org/compatibility/mlists.html http://docs.racket-lang.org/compatibility/mlists.html
  • sigstoat 12y ago
    looks to me like the racket community is united around a single implementation. the scripting language community is all split up between perl and python and a bunch of shells. ugh. much more problematic.
  • samth 12y ago
    What sigstoat said. Put differently, we want you to think of Racket the same way you think of Python.
    • jarcane 12y ago
      I know I certainly do. The very things that make me like Racket over other Lisps are also the things that make me like Python over other imperative languages, ie. clear syntax, quick-to-prototype, big standard library, high quality documentation, etc. etc.