Re:Bruce Eckel announces he's going to write Atomic Python
by dom96 on Thursday September 03, 2015 @05:26AM
(#10163975)
> Nim empowers the programmer to do just about anything, use GC or switch to manual MM, target any computing platform that supports C (i.e. everything), reinvent the language with macros, while packaging it up very elegantly indeed.
This is a very brilliant way to describe exactly what makes Nim excellent. I hope you don't mind if I quote you on this :)
Re:Bruce Eckel announces he's going to write Atomic Python
by fineline on Thursday September 03, 2015 @07:27AM
(#10164319)
You're very welcome.
Re:Bruce Eckel announces he's going to write Atomic Python
by _pmf_ on Thursday September 03, 2015 @03:54AM
(#10163772)
> Rust and Go don't do much for me
Go is useless, but Rust and Nim have much in common (easy integration with native toolchains, stdlib-less bare-bones development for embedded systems); why did you decide that Rust is not for you?
Re:Bruce Eckel announces he's going to write Atomic Python
by fineline on Thursday September 03, 2015 @07:25AM
(#10164307)
I guess the profusion of pointer types was one thing, and the syntax, while not a showstopper, didn't really "speak" to me the way Nim did. But I cut my teeth on UCSD Pascal (after Apple BASIC), that might have something to do with it...
Re:Bruce Eckel announces he's going to write Atomic Python
by kibwen on Thursday September 03, 2015 @12:56PM
(#10166030)
I'm curious when you last looked at Rust, because in the past year the built-in ~T and @T pointers were all removed. Nowadays there are just references and raw pointers (and the latter are primarily just for FFI).
Nim empowers the programmer to do just about anything, use GC or switch to manual MM, target any computing platform that supports C (i.e. everything), reinvent the language with macros, while packaging it up very elegantly indeed.
Elm promises almost the exact opposite. I mean it's elegant, but it's also limited - purely functional, immutable, no nulls, no unchecked list access. And that's the kind of limitation that addresses the problem that Bruce has with other languages - dealing with all the complexity of how something's working. The promise of Elm is that if your code compiles, it works, leaving you to focus on getting the important stuff right - information flow and business logic - instead of tracking down another silly invalidity that never should have made it to runtime.
They're both young, but I wish Andreas Rumpf (Nim) and Evan Czaplicki (Elm) and their teams all the best in taking on the "big boys" with these plucky languages, and would encourage Bruce Eckel to consider skipping ahead of the curve and writing for these alternatives.