That being said, I'm really excited to see a single binary .NET application on Linux, as I like C# very much, possibly more than Go and Java.
For anything else, Rust will have to deal with existing languages that are also able to deliver results.
Regarding GC, not all GC were made alike and being able to use value types also helps.
Rust needs to find a sweet spot to pick up speed. Being yet another application language won't help.
Languages without a GC are a requirement for anything real-time and desirable even for soft real-time. A lot of applications fall into this space, including audio/video processing, real-time bidding systems or game engines. There's a really good reason for why a lot of software being built for the finance industry is being built in C++.
> not all GC were made alike and being able to use value types also helps
Value types don't help quite as much as people think, value types only help avoid some unnecessary boxing/unboxing, relieving some pressure from the young generation and that's it. The problem is storing a lot of data in memory which will imply heap management and dealing with a big old generation, no matter what you do.
And there are only 2 GC-enabled platforms suitable for many soft real time use-cases (but not all) and those would be Java and Erlang ... Erlang because it was built for such scenarios with its lightweight processes and the per-process GC and Java because it has fancy incremental and non-blocking GCs available, like the one from Azul.
Well, I have been coding since 1986 and the only systems programming languages that survived were the ones adapted by OS vendors.
If a systems programming language isn't adopted by an OS vendor, it becomes yet another application programming language and has to compete in already full arena.
> There's a really good reason for why a lot of software being built for the finance industry is being built in C++.
I do like C++, a lot, given its capabilities. But also dislike the unsafety it inherited from C.
However, I think one of the reasons C and C++ got so widespread is that 20 years ago, Java and .NET kind of killed all the other alternatives capable of produced standalone executables with optimizing compilers. At least from what mainstream developers are comfortable with.
So when a average developer goes looking for a programming language able to deliver binaries without dependencies his/her only options are C and C++, which feeds the circle.
I bet if Java, C# and VB.NET had gone the way of producing binaries like Delphi, Oberon and so on, the domain of C and C++ wouldn't be as it is nowadays.
For example, if Ada compilers were cheaper or if Borland had improved Delphi's toolchain across multiple OS instead of going astray in multiple directions, any of those languages could be in C++'s place.
Actually finance is one of the reasons why both Java and .NET are getting pure AOT compilation support nowadays.
> Value types don't help quite as much as people think, value types only help avoid some unnecessary boxing/unboxing, relieving some pressure from the young generation and that's it. The problem is storing a lot of data in memory which will imply heap management and dealing with a big old generation, no matter what you do.
Yet Mesa/Cedar, Oberon and Modula-3 were used successfully to build OSes that, in Oberon and Cedar's case, were used for quite a while as ETHZ and Xerox PARC workstations.
Delphi too lacked a GC. Java and .NET haven't killed Delphi, it is Borland that killed Delphi. This isn't a winner takes all kind of war (well, maybe it is in Windows land). We live in an industry in which multiple programming languages can coexist. For evidence of this you need to look no further than Linux, the Tower of Babel of our age.
And I disagree with you - besides the open-source operating systems that are developed by multiple parties, all "OS vendors" are interested in the lock-in of developers. You're mixing cause and effect I think ... when an "OS vendor" adopts a programming language that isn't created by themselves, that's only because the programming language in question is already popular and here to stay.
In any case, as language geek, I always wish all programming languages find their place, specially those trying to make programming safer.
http://joeduffyblog.com/2013/12/27/csharp-for-systems-progra...
I'd also love an arena system, so I could provide a context and allocate objects in it and enforce they never leak. (Say, per request in an HTTP app.) Then the GC could just free that chunk in one go, no matter how much garbage I've loaded in it. I know that generational GC is supposed to handle this in general, but it isn't free, plus fails when some requests take a long time (and thus all their stuff gets promoted).
I bet currently it already does better than Rust actual code generation.
Sure it still does have a GC, but so what. There are plenty of research OS with a systems language having one. What we need is a company with the guts to force one down developers throats.
In any case, there is still C++ for the unsafe parts available.
Given that only as of Windows 8, C++ was accepted into the kernel, it will take a while until another language gets to join it.
EDIT: Forgot to mention that .NET 4.6 adds more control over GC behavior.
However, the point I was actually trying to make is that for MS, the C# + C++ combo is the way forward and their tools offer great integration experience, so I don't see them adopting something like Rust any time soon. Specially given their relation with the C++ standards process.
According to the C++ code generation talk at Build, their new C2 compiler backend appears to evolve into something like how Apple is using LLVM for.