646 karma · joined June 3, 2021
I don't know, because I think the whole purpose of a prop is to be a fan.
Go is super duper fast, so there's that.
It's not that bad, but doing simple stuff like adding a library can be a huge pain because you have to know how compilers link programs internally to know how to fix the errors you're going to get.
You're looking at it right now.
Not entirely true, as SiFive has had the P550 and P650 for years, and now the P570 and P670. Those should be a lot faster and they're already available to anybody who wants to fill out an online form.
This interview is now years-old and is now 100% false, as today we have several competitive-to-Cortex-A7 boards available and ready to ship right now.
I don't know, that is kind of the whole purpose of DDG to begin with.
That's the million dollar question that we're trying to solve right now.
Are constructions like these really the root cause of CVEs? As long as you do a correct check, then you're all good. If Rust can do the same thing in fewer lines, then that may or may not be a good thing because some people might want a lower degree of abstraction or a greater one.
let mut line = String::new();
stdin().read_line(&mut line)?;
This is what I'm talking about. This is so ugly and clunky and needlessly verbose like Java compared to C++ where you can do std::string input;
std::cin >> input;
and have it Just Work. Why can't Rust do something similar?> Linux is not a legacy system and is slowly adopting Rust and may see greater use with time.
100% USDA Grade-A Certified Prime BS, as shown by both projects' ages (15+, 30+ years) and maybe the definition of legacy. If you consider legacy to be something you have to keep a certain way so that it functions a certain way, then both are basically legacy technologies. What isn't legacy? I would say projects like Fuchsia and Rust itself aren't legacy because you can move fast and break things there. This also means stuff like C++ is legacy, so there's that too.