The Next Big Programming Language You’ve Never Heard Of

A podcasting example is "this week in tech" is for people outside tech to glance inside. Its moderately entertaining and nicely produced although I'd worry about my personal abilities if I ever learned anything from it, because its not aimed at a tech audience. Podcasts for people in tech to listen to are things like "Software engineering radio" although they sometimes run off the TPS report deep end of fads, or "functional geekery", or the former Relevance, now Cognitech, interview show. "FLOSS weekly", another interview podcast show, is kind of in between the two worlds, which is pretty unusual and interesting.

Edited to add some magazine examples. PC magazine is not for people inside tech to read, its for people outside tech wondering whats going on to hear a little gossip. The former sysadmin magazine (out of print for like a decade now?) was for people inside tech to read. The dear departed Perl Journal was for people inside tech. The print version of Linux Journal a decade or so ago was unusually more or less on the border. For noobs, magazines were kind of like internet websites printed out and mailed to you. Different from newspapers in that you only got one a month and they were somewhat more polished and edited and generally on nicer paper. My kids are young enough to not really understand newspapers or magazines so I've actually had discussions along these lines trying to explain. They're a little fuzzy about broadcast distribution vs streaming too, broadcast is like a stream but you have no personal pause or commercial skip button, this confuses the heck out of them.

http://stackoverflow.com/questions/tagged/d?page=1&sort=newe...

Completely unheard of! ;)

However, C/C++ is intimidating, which is why I think compile-to-C programming languages like Nimrod [ii] are going to be the next big thing.

[i] https://gradha.github.io/articles/2014/03/nimrod-for-cross-p...

[ii] http://picheta.me/articles/2013/10/about-nimrods-features.ht...

* Python's approach of "batteries included", ruch standard library. Sure you can find a library in C++ for almost everything, but it is never as easy as "pip install" and subsequent import. * I do not have to declare types. It works well for small programs where I can maintain implicit typing in my head but becomes an impediment for larger programs. * Compilation time for any moderately sized C++ program and the lack of REPL quickly become a problem in fast iteration cycle. No IPython for C++. * Small syntactic sugar things always help. As an example, In Python I can assign array, set, or dict literal to any variable. In C++11 even though I should supposedly be able to do some of that, it is not universally across platforms.

This means they end up in very similar, yet different places: GC is the default in D, but isn't even a core part of Rust at all. D allows you to turn it off, losing some functionality, Rust allows you to add one in as a library.

Most people in Rust-land have an incredibly high amount of respect for the D team and all they've done, and continue to do.