Live data from Hacker News

Rust Language, and Why C/C++ Will Never Die (2015)

viva64.com

61–66 of 66 posts

Re: Rust Language, and Why C/C++ Will Never Die (2015)

#61

C (and, to a lesser extent, C++) absolutely will die. The way the languages are managed guarantees this. It's a myth that garbage collection is slow, and it's furthermore a myth that manual memory management is easy. So C (and, to a lesser extent, C++) will continue to lose ground for new projects to languages that take the requirement to manage memory off the programmer. Furthermore, while C and C++ require low-leve…

> C is too high-level for system code Aren't most systems written in C?

Modern computers aren't PDP-11 like anymore.

Multicore vector based CPUs with branch prediction, GPGPU, NUMA architectures....

Some of those features are exposed as compiler intrinsics or C dialects for GPGPUs (e.g. OpenCL).

However none of those features exist in the abstract hardware model of ISO C.

Re: Rust Language, and Why C/C++ Will Never Die (2015)

#62
post #38
post #33

I really wish people would just forget about unsafe ("unsafe" as in Ruby is much safer) languages completely and embrace languages with safe run times. Rust, C, C++, Go and many more languages all need to "die" and be replaced with high-level languages; Lisp, Python, Ruby, Javascript, etc. I guess the fanboys will complain for me calling Rust unsafe. You can write "safer" programs in Rust just like you can in C++. Th…

Is it possible to write an operating system or a browser if we forget about the languages you want us to forget about?

Not only it is possible, it has been done multiple times, the first OS written in a high level language was developed in 1961, about 8 years before any line of UNIX was written in Assembly.

And the first hypertext based software was developed at Xerox PARC, which also did not use any Bell Labs languages.

Re: Rust Language, and Why C/C++ Will Never Die (2015)

#63
post #7
post #3

Per HN guidelines, this article should have its publication year of 2015 in the title (the article itself seems to not include a date, but one can find the various submissions on Reddit where this was originally discussed). In fact, it's old enough that it even predates the Rust 1.0 release. I haven't gone ahead and read it in full again this time, since the irony of a company selling C++ static analysis software den…

benchmars game is great, but sadly not well maintained anymore. Rust has it's flaws, but it's not runtime speed (much more compilation speed, IDE support, distributed compilation support).

> benchmars game is great, but sadly not well maintained anymore.

?

rustc 1.32.0 as-of Sat, 19 Jan 2019

https://benchmarksgame-team.pages.debian.net/benchmarksgame/...

Re: Rust Language, and Why C/C++ Will Never Die (2015)

#64
post #6

The Rust - C++ speed comparison is sadly quite bad. On a modern machine, some of the benchmarks from the benchmarks game ran faster in Rust than in C++. It usually depends on the explicit / implicit vectorisation support, and a lot of it is taken care of by LLVM. Also if you look at the C code, the multi-threaded optimizations are quite hard to write in C, while Rust has Rayon (which is not yet used in the Benchmarks…

> Rust has Rayon (which is not yet used in the Benchmarks game examples)

Yes it is!

Since or before May 11th, 2017 —

https://web.archive.org/web/20170511062152/http://benchmarks...

Re: Rust Language, and Why C/C++ Will Never Die (2015)

#65
post #33

I really wish people would just forget about unsafe ("unsafe" as in Ruby is much safer) languages completely and embrace languages with safe run times. Rust, C, C++, Go and many more languages all need to "die" and be replaced with high-level languages; Lisp, Python, Ruby, Javascript, etc. I guess the fanboys will complain for me calling Rust unsafe. You can write "safer" programs in Rust just like you can in C++. Th…

https://www.inf.ethz.ch/personal/wirth/Oberon/index.html

Re: Rust Language, and Why C/C++ Will Never Die (2015)

#66
post #33

I really wish people would just forget about unsafe ("unsafe" as in Ruby is much safer) languages completely and embrace languages with safe run times. Rust, C, C++, Go and many more languages all need to "die" and be replaced with high-level languages; Lisp, Python, Ruby, Javascript, etc. I guess the fanboys will complain for me calling Rust unsafe. You can write "safer" programs in Rust just like you can in C++. Th…

Python, Lisp, Ruby and JavaScript are all slow as fuck languages. And you are completely wrong about Python being faster. Python is up to 100x slower than C++. How much crack did you smoke before writing this?

Translation: I'm a webshit programmer who doesn't understand low level languages, and therefore they shouldn't be used

Post reply on HN