5 ms·

The author should really look at Nim.

• davidatbu 3y ago
  You know: this always tempts me, but I hold back because nim is not memory-safe (or has a clearly delineated memory-safe subset like Rust), and I would rather pick up an actually memory-safe (even if GCed) language even if some perf-cost (like F#, Ocaml, Swift, Vale ..etc).
  • cb321 3y ago
    There is a fairly clear subset of Nim which is memory safe. There are discussions once in a while to reduce that from a small set to one..two keywords, e.g.: https://forum.nim-lang.org/t/9280#61243 which has links to some others. The resolution is usually: Eh - it's already a very small set. There also may well be libs (that you feel unable to not rely upon) which use these language constructs, and trust sure is tricky (in any PL ecosystem as well as just in life).
    • davidatbu 3y ago
      Definitely learnt from that link, thanks! That still hasn't won me over from prioritizing definitely-memory-safe languages over "fairly-memory-safe" nim tho.
• deleted 3y ago
  [deleted]
• mrweasel 3y ago
  Isn't that more equivalent of "I really want to have a typed and compiled language, but I'd also like to keep the Python like syntax". Nim is an underrated language, it's easy to pick up and plenty fast.
• esafak 3y ago
  The language is dandy, but it needs better tooling. If I wanted to support the project, that's where I'd direct my energy.
• kobzol 3y ago
  I will someday :) But unless there's Tensorflow and about a gazzillion other packages in Nim, it's not easy to switch.