News for hackers. Stuff that matters.
Re:I missed Nim (2014) by aikah on Thursday January 21, 2016 @02:49PM (#10947791)
It's crazy that in 2016, people are still seeking the holy grail of statically typed, memory safe, no VM programming languages that retains most of the advantages of dynamically typed languages. My point is it should be there already!

Well , I guess language design is just hard... Yet the demand exists, and it's huge no question.

Out of all of these, i still think D is the most interesting one (I like C#, I want generics ...).

I don't agree with some choices Nim made but it still look interesting. Go is way too rigid for my programming style. Yet Go set some expectations when it comes to developer experience, so it was a step in the right direction.

Re:I missed Nim (2014) by amyjess on Thursday January 21, 2016 @06:17PM (#10949330)
Yes, of all the new-style AOT languages, Nim and D are by far and above my favorites.

Go and Rust just never appealed to me. Actually, I never liked Go for the same reasons as you...

Re:I missed Nim (2014) by otabdeveloper on Thursday January 21, 2016 @03:49PM (#10948206)
> statically typed, memory safe, no VM programming languages that retains most of the advantages of dynamically typed languages

Those requirements contradict themselves in numerous ways. As always, engineering tradeoffs are paramount.

As for "statically typed, memory safe, no VM" -- C++ fits all those perfectly. (Provided you put in the effort of learning C++. There's another tradeoff you'd need to keep in mind.)

Re:I missed Nim (2014) by pjc50 on Thursday January 21, 2016 @05:39PM (#10949079)
C++ is not memory-safe and cannot be coerced into being so.

You can write nice C++ in the C++14 style, but you can't turn off or ban the unsafe features. Until I can make my program fail to compile if there is a bare pointer in it (and how would that work with the standard library and system API?), it's not a memory-safe language.

Re:I missed Nim (2014) by Gankro on Thursday January 21, 2016 @04:53PM (#10948696)
There isn't any definition of memory safe, nor any published version of C++, for which this is a true claim.
Re:I missed Nim (2014) by steveklabnik on Thursday January 21, 2016 @04:25PM (#10948502)

  > Those requirements contradict themselves in numerous ways
I'd be interested in hearing more about how.
Re:I missed Nim (2014) by xaduha on Thursday January 21, 2016 @09:56PM (#10950465)
> It's crazy that in 2016, people are still seeking the holy grail of statically typed, memory safe, no VM programming languages that retains most of the advantages of dynamically typed languages.

I have my eye on Red and its system programming dialect Red/System

http://www.red-lang.org

http://static.red-lang.org/red-system-specs.html