492 karma · joined August 21, 2019
cperciva - tarsnap founder, Animats - nagle, zx2c4 - donenfield, jart - justine tunney,
HTTPS can mitigate some of that, just like it can for VPNs, but the site you're going to is still very much visible.
Don't get me wrong, Tor is a very useful service if anonymity is your goal, but it requires a solid understanding of what can go wrong, which torproject provides a decent list for: https://support.torproject.org/faq/staying-anonymous/
so replace a vpn, which might be logging your traffic, for a service which absolutely is logging your traffic?
Tor is an anonymity service, not a privacy service.
it might be optimized to a memset, but it's the clone codepath, as opposed to the u8 specialization codepath as discussed in the article
But the original commenter is talking about how the benchmark isn't useful because it doesn't touch memory, but you get similar results even if you do touch memory.
- 33 are under investigation
- 61 unrelated to the vaccine
- 52 had insufficient information to determine if the vaccine was linked to the death
and finally the piece of information we're interested in:
- 6 due to TTS (a known side-effect), all from people who received the COVISHIELD/AstraZeneca vaccine
Sure you could throw unsafe everywhere and not check anything, but that misses a major reason to use rust--safe abstractions over unsafe behavior. Once a safe abstraction exists for unsafe behavior, all the heavy lifting of guaranteeing code will not result in undefined behavior is offloaded to the compiler, instead of the programmer having to keep track of it all.
https://play.rust-lang.org/?version=stable&mode=debug&editio...
It looks like it still misses some of the cases (specifically with decomposed vs precomposed).
As a side note, it looks like the playground editor also doesn't correctly render some of the lengths (the cursor is 1 character off on the decomposed case)
you could even look at Red Hat, one of microsoft's competitors, who showed microsoft's market share at 49.6% in 2017: https://www.redhat.com/en/blog/red-hat-continues-lead-linux-...
I don't have access to the full numbers, but I'd bet on the linux side being majority red hat for the same reason.
> In 2019, the Windows operating system was used on 72.1 percent of servers worldwide, whilst the Linux operating system accounted for 13.6 percent of servers. Compared to 2018, both companies experienced an increase to their overall market share.
Edit: Because people seem to think that the numbers are made up, here's some more sources with not quite as high, but similarly dominant numbers:
Red Hat: https://www.redhat.com/en/blog/red-hat-continues-lead-linux-... - microsoft @ 49% in 2017
t4: https://www.t4.ai/industry/server-operating-system-market-sh... - microsoft @ 47% in 2018
The reason this limitation exists is because it was decided that an array length of 0 should impl `Default` even if `T: !Default`, so `impl<T: Default, N: usize> Default for [T; N]` can't be used.
This may be possible in the future if specialization is stabilized, but for now we're stuck with that limit for `Default`.
For example: you are in a class and someone asked a question about a topic. The person next to you turns and says "I can't believe they don't understand this topic." Your neighbor is making the assumption that you also understand it. So if you didn't understand the topic, a response could be "Nah, even I had some questions about it."
Although someone could definitely use it to be condescending, or just trying to be cheeky.
the AI will still avoid losing, but it also won't be able to find the endgame strategy to win
Rings are code privilege levels, they don't "protect" memory, page tables do that, and the implementation to protect the stack has been around for over a decade - DEP
call/return stack detection is very new, afaik only current generation intel processors have it under the name CET (control-flow enforcement technology). This works by a processor-level "shadow stack," which is pushed to on calls and popped from on returns, and throws a fault if the actual stack is returning to a different location
Pointer encryption is available on ARM as PAC (pointer authentication). Afaik there's no equivalent on x86 processors.
Hardware mitigations are gaining more and more traction, so hopefully all of them will be available across all major architectures within the next decade or so.
EDIT: another huge mitigation that's starting to gain traction is process-level virtualization. Qubes is most known for it, but Windows has been building more support for it (currently only edge and office support it, under the name "Application Guard"). The idea is that if a malicious actor is able to exploit a program, they would also have to break out of the vm the app is in to gain access to the full system, which can be a much more difficult task.