Yes, that’s the difference between “safer” and “actually safe”.
- 0 Posts
- 6 Comments
It’s also a fallacy that rust code is memory safe. I audited a couple of large rust projects and found that they both had tens of unsafe constructs. I presume other projects are similar.
You can’t use “unsafe” and then claim that your program’s memory safe. It may be “somewhat safe-ish” but claiming that your code is safe because you carefully reviewed your unsafe sections leaves you on the same shaky ground as c++, where they also claim that they carefully review their code.
deleted by creator
zik@lemmy.worldto Programming@programming.dev•What are the craziest misconceptions you’ve heard about programming from people not familiar with it?3·1 year agoThat might be true of VHDL / Verilog programmers I guess.
zik@lemmy.worldto Programming@programming.dev•Most and Least Verbose Programming Languages4·2 years agoDon’t you mean:
class AgreementManagerClass { public static void main(String[] args) { System.out.println("I agree."); } }
zik@lemmy.worldto Programming@programming.dev•Most and Least Verbose Programming Languages1·2 years agoGo’s less verbose than Java in my experience. And I’ve written quite a lot of both. But YMMV.
zik@lemmy.worldto Programming@programming.dev•Most and Least Verbose Programming Languages2·2 years agoAnd yet C with its not at all comprehensive standard library did well. I’m a bit puzzled about these results.
There’s no way that Go is more verbose than Java. I’ve written both in decent quantities and Java was always way more verbose than Go for me. I suspect it’s the nature of code.golf giving these results more than the languages themselves.
deleted by creator