Chilinot

PDFs can do all sorts of shenanigans, such as bundle executable javascript that runs when the file is opened.

142 results now, they are multiplying!

Lane keep assist is always enabled, this "copilot" or whatever it's called is an extra feature i can manually enable over the default lane assist. And it will steer and follow the road quite well in most conditions. But sometimes it starts the ping pong behaviour.

Should also be noted that i never take my hands of the wheel. And the volvo is quite fast at beeping at me if it detects that i dont hang onto the wheel.

My volvo also has a "not perfectly tuned" PID loop. With "autopilot" engaged it keeps weaving constantly left and right inside the lane im in. Have gotten used to keeping a firm-ish pressure on the steering wheel at all times to compensate. But drivers behind me must have thought me drunk before i got the hang of it.

Having installed Arch myself a couple of times, i think i would disagree. Not really much in that process that teaches you how linux actually works. It's more just about managing disk partitions and moving files around than anything else.

LFS is just on a whole different level, and is on my bucket list to complete the entire process one day.

Yea i think this discussion was quite interesting as well. And i can also verify that this issue exists in Zen (firefox based) as well.

> I also think “3 out of 3” is not a good idea, as it allows any single key holder to prevent election outcomes that they don’t like (something that may have happened here, too. I don’t think cryptography experts often lose such keys by accident)

It's also important to factor in the case of "a key holder was hit by a bus, and now we can no longer access their private key".

This point is brought up and discussed in the linked article.

What makes you come to that conclusion?

Thank you, was just about to task my team with figuring out how affected we are by this.

I have been an avid proponent of the way errors are managed in Rust and Go for a long time. However, this article raises a very good point. Before i started developing in Rust and Go, i did Java and python for several years. And damn, do i miss those stacktraces every now and then when something bad happens that isn't properly handled by the code.

Still, i do think returning the error as a return value is better than having a completely separate flow when dealing with exceptions. I like that it forces me to properly deal with an error and not just ignore it and think something like "meh, i'll get to this later". Because i will never "get to it later".

I like Rust as much as the next guy, but statements like this makes me roll my eyes:

> hk is written in rust, pre-commit is written in python. hk will be much faster.

I have no idea how fast hk or pre-commit is, i have never used them. What matters to speed is the algorithms used and their complexities. If you implement a shitty algorithm with exponential complexity in Rust it's going to be slower than a linear complexity algorithm in python.

Yea, that statement confused me as well.