googh

37 ms·

1.
by googh 2y ago
I just wrote that as an observation, and I did not mean to offend the parent. Now, let me explain why I felt that way. First and foremost, the phrase "undefined behavior" only applies to C and C++ because the specifications of tho
2.
by googh 2y ago
Most HN users already use languages with GC which are more memory safe than Rust. People still use C++ either because they are maintaining existing code, or they work in domains where memory safety is not really necessary (games, HFT, ML).
3.
by googh 2y ago
Most (if not all) of your posts here on HN boil down to "C/C++ bad, Rust good". I wonder what you are trying to achieve by this, but I assure you that this does not do Rust any favor other than giving the impression that the
4.
by googh 2y ago
Funny how the HN submission has more points than the original SE question.
5.
by googh 2y ago
Just curious: Why didn't you email the moderators?
6.
by googh 2y ago
Can someone shed some light on why the parent comment (by varjag) is downvoted?
7.
by googh 2y ago
I think this problem can be solved using either a linter or formatter-like tool that makes naming consistent before the code gets committed.
8.
by googh 2y ago
Not parent, but take a look at these: https://news.ycombinator.com/item?id=32117148 https://news.ycombinator.com/item?id=39641552 These threads are absolutely painful to read. The Rust community/leader
9.
by googh 2y ago
AI is probably the only field in science where even scientists behind the thing talk like salesmen. Hinton in particular comes off as a dishonest person: he clearly knows what he says is wrong but does it anyway because he wants to hype the
10.
by googh 2y ago
The thing is, these problems rarely arise for programmers who daily code in C++. People who don't use C++ love to enumerate different C++ gotchas. In reality, most C++ projects define a coding style that dodges most of these problems.
11.
by googh 2y ago
Could you explain what Fedora does better than the Debian-family of distros? I find Fedora's overall performance to be worse than other distros (including Ubuntu).
12.
by googh 2y ago
> "but we don't know how often it happens!"-bollocks I am not sure why you describe that as bollocks. The most surprising part of the xz backdoor is that it was discovered by sheer luck. Imagine what would've happened
13.
by googh 3y ago
> I would say that you want more than 32 bit pointers Fil-C uses fat pointers to retain bounds and type information to make existing C code safe (typical C is filled with pointer arithmetic and casts). Languages like C++/Zig/D
14.
by googh 3y ago
There is hardly any difference between indices into vectors and isoheaps (ie. an allocator that reuses the same pool for the given type). Except that the latter is faster and much more ergonomic. Both prevent remote code execution. I wonder
15.
by googh 3y ago
If preventing remote code execution is the goal, then C/C++/Zig can also achieve this using isoheaps (see Fil-C[1] for example). Even without isoheaps, CFI mitigations are able to prevent jumps into code not known at compile time.