Steam store rendered in Servo
I'm a C++ developer, and Rust looks very exciting to me.  Maybe I'm optimistic, but Rust really looks like it can be a serious C++ contender in the long run.Talking with other C++11/C++14 users here, the general feeling is that, yes, C++ is a good language because of the performance you can get out of it and some of the nice features that have been added, but the language carries around a lot of cruft that is unavoidable due to its age and maturity.C++ has always been an expert's language.  These days it's the expert's expert language++.  There are no shortages of landmines and gotchas in the C++ landscape.Modern C++ is a new language, and it really does help, but for the first time there's another language that can actually fill those same shoes.A really big deal that isn't really addressed by golang is the fact that you can produce shared libraries with rust, and call them from existing C/C++ programs through a C interface.  That's a really big deal in places with a lot of legacy code.Another big deal (from the scientific computing POV) is the lack of garbage collection.  Yes, GC is helpful, but replacing C++ means squeezing every last bit of performance out of your hardware.  Rust does not sacrifice in this regard.I really hope that Rust has a bright future.  It's almost like "C++ done right", but I would stray away from such a label since someone might Linus you and say, "there's no way to do C++ right".I also view golang as the successor to Python.  It's faster, modern, addresses concurrency, and makes things easier for developers.  It takes a strongly opinionated stance, and that's exactly the right choice for many problem domains.Python, unfortunately, is dead to me.  The GIL is a deal-breaker, and even though we have lots of Python code in production, I can definitely see a future where Python is phased out in favor of something like golang.Basically, I'm bullish on Rust + Golang, neutral on C++, and slightly bearish on Python/Ruby-like languages that do not address the concurrency problem.