273 karma · joined March 1, 2012
Isn't, literally, that the job of the government?
> In general, if the cores are SMT (Symmetric Multithreading) siblings, then you may observe random branches, and, if they're SMP (Symmetric Multiprocessing) siblings from the same package, then you may observe machine checks.
[...]
> However, we simply don't know if we can control the corruption precisely enough to achieve privilege escalation. I suspect that it is possible, but we don't have any way to debug μop execution!
The exploit they published crashes the machine, but it may be possible to write one that does other things, they just don't know how.
Actually useful blog post: https://bughunters.google.com/blog/5997221712101376/the-rept...
I'll admit that, yes, changing string to bytes and unicode to string was a bit annoying, but the change itself wasn't fundamentally 'of dubious benefit', it did have benefits, and related to this, the only major issue was that you couldn't, for a long time, have code that worked in both where it came to literals. The biggest problem here was the implicit conversion from 2, that I agree needed to go.
Most of the other things can be trivially fixed automatically, or at least detected automatically, but without type hinting, it wasn't really easy to fix the automatic conversion.
There were other changes that were a bit tricky, but the majority of issues stemmed from the str/bytes change.
Yes, they are single threaded, because using multiple threads brings very little benefit in most cases...
> If expecting extreme load (like Twitter scale), then Python is usually not the answer (rather go to a statically typed language like Java, Go, Rust etc).
So that means we shouldn't get any performance improvements, because there are faster languages out there?
Second is just how things work, the function is a closure that evaluates the non local variable when you run it.
Third one... Iterating over the generator does NOT yield an empty list, it raises StopIterator. As does trying to iterate after a generator is done, so there's no way for list to know what's happening. You can argue that's a bad design, but I'm not so sure, an iterator is something you need to make sure you don't try to iterate over twice...
I don't get the 4th. Comparison operators have the same precedence, so yeah.
Yes, the algorithm is much more complicated, and we obviously don't have the capacity to map a brain like that, but to imply that there's anything except the laws of physics that governs it is... well, not very scientific.
Because in cars that are at least 1000kg, a few grams definitely matter.
My mac is just painfully slow, if I start docker it becomes almost unusable. This is a 2019 Intel one, btw, it might not be so bad on m1s, but when I got the job (and the mac) , only the original one external monitor m1s were available.