6 ms·
My impression is that Nim was in the right place at the right time and unintentionally piggybacked on the interest surrounding languages such as Rust and Go. Th
by trwired 12y ago
My impression is that Nim was in the right place at the right time and unintentionally piggybacked on the interest surrounding languages such as Rust and Go. This perception may be completely wrong. However, I do remember all these languages started gaining popularity within the span of several months. Before that Nim (then Nimrod) existed, but remained in obscurity.
- vanderZwan 12y agoI do remember a well-timed post on reddit/r/programming about Nimrod (as it was called back then), shortly after Go's release. It contained a lot of "Go is disappointing (to put it mildly), this looks so much better"-comments about the language. The backlash against Go was pretty huge. I don't remember the guy behind Nim doing much trash-talking, which probably helped as well, especially in the long run. EDIT: fixed derailed sentence.
- aikah 12y agoThe problem of Go is the hypocrisy of its community when it comes to the expression problem. Obviously Go isn't expressive at all. Which make it verbose when one tries to write abstractions with it. A lot of devs just want a fast,type safe,memory safe language,that doesn't need a hungry VM to run but is expressive enough so "scripters" feel at home. Why is it so hard to get a language that does that? IDK .
- lucian1900 12y agoThere are actually several, of common lineage: OCaml, F#, Haskell.
- aikah 12y agoDoesn't F# work with .net and the CLR ?
- lucian1900 12y agoIt does run on .NET, yes.
- mercurial 12y agoYes, F# runs on the CLR.
- deleted 12y ago[deleted]
- kxo 12y ago> > expressive enough so "scripters" feel at home As much as I love all things Haskell, there is no way it fits the "scripters can use it" bill.