expression

Maybe you should gift her with a newer pasta machine. :)

Pasta certainly isn't a staple of Finnish cuisine, but through family I have Italian relatives, and my parents have been making handmade pasta since before durum wheat was widely available here (it certainly was a very different world back then). Their hand cranked pasta machine has among other “heads” a tool for ravioli, taking in two sheets of pasta dough and automatically applying contents for each one it cuts. Certainly faster than filling them one by one, can't tell if you can taste the difference. (I really used to like pasta, shame that certain grains and I don't get well together.)

Ubuntu has done that a long time if there's a problem with graphics drivers. Don't know more specifics for your issue, since I haven't run Ubuntu in a VM in years.

Or ramdisk if you have a stable system.

Luckily you don't need to maintain electric cars at all.

Did you know you can start the command with the redirection operator?

    <input-file grep stuff

Unless you are concatenating stuff, I see no reason to use cat.

I guess I'm never to actually “get Lisp” to appreciate its syntax.

>Aside from the prefix ordering, Common Lisp’s syntax is already a bit more elegant because you can set arbitrarily many variables without repeating the assignment operator over and over again:

    ; Have to type out `=` three times
    x = 10
    y = 20
    z = 30

    ; But only one `setf` required
    (setf x 10
          y 20
          z 30)

I utterly fail to see the aforementioned elegance, although I certainly can't miss the line where it happens.

If the projects GitHub page is anything to go by, I doubt that. The only thing that's been changed in 9 months is the readme, and the change was to remove the note about the project being in "active early development".

How about this, too:

    var a = 1 ^ 2

As it stands, I find the thing entirely useless.

Must be a funny comparison group you have there.

I guess the site is served using PHP.

FWIW, files.kde.org does support HTTPS as well.

And if anonymity is of no concern, why not run OpenVPN on Raspberry Pi (or something similar) at home? Cheap to set up, and no running costs (assuming internet access at home).

Haven't been following this blog, but one thing caught my eye while skimming the post:

>The implementations of these methods need to modify the correct bits of the u16 without touching the other bits. For example, we would need the following bit-fiddling to set the stack index:

    self.0 = (self.0 & 0xfff8) | stack_index;

>Or alternatively:

    self.0 = (self.0 & (!0b111)) | stack_index;

>Or:

    self.0 = ((self.0 >> 3) << 3) | stack_index;

>Well, none of these variants is really readable and it’s very easy to make mistakes somewhere. Therefore I created a BitField type with the following API:

    self.0.set_range(0..3, stack_index);

>I think it is much more readable, since we abstracted away all bit-masking details.

Personally, I disagree. Whilst it is easy to make mistakes when writing bit-fiddling code (there seems to be one in the second example, unless Rust has on of the more weird !-operators in programming languages), or any code for that matter, the meaning of all the bitwise operations is easy to recognise.

Without knowing the API, the transformed line rings no bells. How many APIs do you want to learn?

Yeah, but robocars don't honk. Or perhaps they will, too.