News for hackers. Stuff that matters.
Re:C and C++ Aren't Future Proof by CJefferson on Sunday January 20, 2013 @07:01PM (#5088876)
Really? I should switch my apps from C++ to an unfinished language?

I'll consider once the Mozilla foundation have written any application of note in it.

Re:C and C++ Aren't Future Proof by zxcdw on Sunday January 20, 2013 @07:12PM (#5088925)
You should not switch your apps. You should stop creating new projects in C++ once Rust is mature enough for your liking.

The fundamental "problem" we're having/facing with C and C++ is the investments we've put in. Lots of "infrastructure" in modern day computing relies on C and C++ and will do so for ages. We can't just drop the projects and switch to something else(say Rust or maybe Go), but we can stop creating new C and C++ codebases to alleviate the problem for the future.

Re:C and C++ Aren't Future Proof by eropple on Sunday January 20, 2013 @09:55PM (#5089576)
No, we can't, because Go is unacceptable (garbage collection) and Rust is no better than a figment until all of the libraries I need exist in it.

And I have better things to do than port them, because C++ doesn't bother me.

Re:C and C++ Aren't Future Proof by shmerl on Sunday January 20, 2013 @09:58PM (#5089585)
Exactly, it's a chicken and egg problem. C++ has tons of libraries, while Rust has barely any. Rust can use external C bindings, but not C++ ones yet. I think if they solve the issue of using C++ libraries from within Rust, the transition will be much easier, and meanwhile more native Rust libraries will be created.
Re:C and C++ Aren't Future Proof by rplacd on Monday January 21, 2013 @01:37AM (#5090258)
Is the C++ ABI issue ever going to be solved?
Re:C and C++ Aren't Future Proof by pjmlp on Monday January 21, 2013 @03:21AM (#5090503)
Yes, in the cases where the operating system is done in C++.

The C ABI is the operating system ABI and it is only ubiquitous in operating systems done in C. Other operating systems use whatever ABI the system offers.

Re:C and C++ Aren't Future Proof by shmerl on Monday January 21, 2013 @01:53AM (#5090306)
That's part of the problem they are facing. C is much easier to deal with.
Re:C and C++ Aren't Future Proof by jhasse on Sunday January 20, 2013 @07:52PM (#5089097)
My new projects rely on C++ libs, so I can't use Rust.
Re:C and C++ Aren't Future Proof by roel_v on Monday January 21, 2013 @04:16AM (#5090650)
How many Rust libraries are there for various tasks? What IDE supports Rust? What tutorials, books and conferences exist that teach and distribute the state of the art in development techniques? What example projects have been build in it to demonstrate its feasibility for large projects? What tools support Rust (continuous integration, code formatting/checking, build tools, ...)?
Re:C and C++ Aren't Future Proof by wbl on Monday January 21, 2013 @10:30AM (#5091867)
I'm sure make and git work with Rust like anything else.
Re:C and C++ Aren't Future Proof by roel_v on Tuesday January 22, 2013 @03:08AM (#5096115)
Well using make as an example of anything good is... let's say 'suspicious'. There is more to tooling than make and git (note that I deliberately omitted version control from my list)
Re:C and C++ Aren't Future Proof by jfb on Sunday January 20, 2013 @07:31PM (#5089028)
While switching now isn't feasible, keep in mind the sunk cost fallacy.