4 ms·
I am very intrigued by Nimrod. The language seems to have goals that overlap with e.g. Rust, but with a bunch of really interesting design decisions (e.g. GC by
by skrebbel 13y ago
I am very intrigued by Nimrod. The language seems to have goals that overlap with e.g. Rust, but with a bunch of really interesting design decisions (e.g. GC by default, but first class support for manual memory management). Given the amount of force driving Rust (and Rust's PR machine), compared to Nimrod which seems to be really pushed forward by one single person, I'm really impressed by how far Nimrod got.
I really want to start using Nimrod for real work.
- progman 13y ago> I really want to start using Nimrod for real work. I have actually used both Rust and Nimrod for real work (same project, first Rust then rewrite in Nimrod). My experience is that Nimrod is far easier to handle than Rust. It feels like Python with the native speed of C. There are a lot of nice features built into Nimrod, for instance native Perl regular expressions and seamless import of C functions. As for me it is the most productive language I ever encountered. I know many languages.
- pjmlp 13y ago> GC by default, but first class support for manual memory management Since Mesa/Cedar (1978) there have been quite a few systems languages proposing that approach. http://bitsavers.trailing-edge.com/pdf/xerox/parc/techReports/CSL-83-11_The_Cedar_Programming_Environment_A_Midterm_Report_and_Examination.pdf http://bitsavers.trailing-edge.com/pdf/xerox/parc/techReport...
- Dewie 13y agoInitially, I was kind of 'meh' towards Nimrod since Rust already looked so good. But when I recently read about the features, especially the metaprogramming and compile-time features, it seems like it could be really fun and powerful to program in.
- fedesilva 13y agoIf I understand correctly once you stop using the GC, Nimrod is not memory safe. Rust is.
- TylerE 13y agoThere's really no reason not to use the GC though. It's very lightweight and quick.
- ehsanu1 13y agoWhile you're right for probably most classes of application, this is not an absolute truth. There are reasons not to use the GC - eg you're developing a browser, or a GC for a language, and many besides. I see a similar thread where you made a similar statement, so in favor of not rehashing that whole thread, here it is: https://news.ycombinator.com/item?id=7061533 https://news.ycombinator.com/item?id=7061533
- TylerE 13y agoOh, I strongly disagree with that logic. A browser is exactly the sort of situation where a GC is useful. I mean, it only took Mozilla 2 decades to get Firefox to not leak memory like a sieve.
- ehsanu1 13y ago`it only took Mozilla 2 decades to get Firefox to not leak memory like a sieve` I'm sure you're aware that this is quite an unfair/exaggerated statement to make. But yes, I'm all in favor of language features that help prevent memory leaks. But the reason the smart folks at Mozilla don't just switch to using a GC for all of Firefox (as do none of the other major browser vendors) is due to GC pauses sucking for user interaction. If you don't think that's a concern, or have a solution for it, please elaborate.
- TylerE 13y agoI don't see how that's all that unfair. Development on the Mozilla codebase started in early 1998, almost 16 years ago.
- 13y ago
- DorianMarie 13y agoTo support the fact it's mainly one guy: https://github.com/Araq/Nimrod/graphs/contributors https://github.com/Araq/Nimrod/graphs/contributors His name is Andreas Rumpf and he is really impressive.
- zura 13y agoJust one thing to point out - people wrongfully consider that an alternative to a non-deterministic GC is necessarily a manual memory management. There are automatic and deterministic memory management mechanisms, e.g. smart pointers in C++, Rust.
- pjmlp 13y agoFully agree. To reinforce your point, many are unaware that the various forms of reference counting are also GC algorithms in CS speak.