Hacker News new | ask | show | jobs
by nimmer 1119 days ago
The author should really look at Nim.
4 comments
mrweasel 1119 days 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.
link
kobzol 1118 days ago
I will someday :) But unless there's Tensorflow and about a gazzillion other packages in Nim, it's not easy to switch.
link
esafak 1118 days 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.
link
davidatbu 1118 days 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).
link
cb321 1118 days 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).

link
davidatbu 1117 days 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.

link