blotz

I am the Anti-Rust programmer, I will call other code in Rust. I will call other code in Rust because it is coding is hard. As I am the Anti-Rust programmer, I will keep writing rust until my computer breaks, I will not use proper coding practices. Because I am the Anti-Rust programmer, my computer will be unstable and crash.

I will come to you when you are sleeping, and include random malloc(s) in your code. If I find javascript on your computer, I will use implicit type conversion. Do not try to stop me, if you try to stop me, I will do it anyways. I am the Anti-Rust programmer. If you program in javascript. You will be fine :).

You will be sleeping as I rewrite your computer. You will not notice me as I am the Anti-Rust programmer. I am slow, but I will make your computer slower. I understand your computer, as it doesn't understand me. After I rewrite your computer, you will hate your computer. You will hate your computer because it is unstable and crashes. I will do the same to all computers because I am the anti-rust programmer.

I will not stop at your computer. I will rewrite the world because I can. Your brain is written using good programming practices. If your brain is written using good programming practices, you will hate what I do. I will rewrite your brain. You cannot stop me from linking different languages together, as I am the anti rust programmer. After I rewrite you, you will enjoy constant memory leaks. You will forget everything all the time. I am the anti rust programmer.

I will rewrite the world. I will rewrite quantum mechanics because I can. I will not tell you all my plans before I rewrite you. It is because you are perfectly normal and will hate my changes. I am the anti rust programmer. You will forget me because you are full of memory leaks.

Took y'all's advice to heart and it's looks like it's working well!

Not my best bread ever but this is pretty normal issue. I totally over proofed it because I fell asleep during the proof xD

// At this point, I'd like to take a moment to speak to you about the Adobe PSD 
// PSD is not a good format. PSD is not even a bad format. Calling it such would be an
// insult to other bad formats, such as PCX or JPEG. No, PSD is an abysmal format. Having
// worked on this code for several weeks now, my hate for PSD has grown to a raging fire
// that burns with the fierce passion of a million suns.
// If there are two different ways of doing something, PSD will do both, in different
// places. It will then make up three more ways no sane human would think of, and do those
// too. PSD makes inconsistency an art form. Why, for instance, did it suddenly decide
// that *these* particular chunks should be aligned to four bytes, and that this alignement
// should *not* be included in the size? Other chunks in other places are either unaligned,
// or aligned with the alignment included in the size. Here, though, it is not included.
// Either one of these three behaviours would be fine. A sane format would pick one. PSD,
// of course, uses all three, and more.
// Trying to get data out of a PSD file is like trying to find something in the attic of
// your eccentric old uncle who died in a freak freshwater shark attack on his 58th
// birthday. That last detail may not be important for the purposes of the simile, but
// at this point I am spending a lot of time imagining amusing fates for the people
// responsible for this Rube Goldberg of a file format.
// Earlier, I tried to get a hold of the latest specs for the PSD file format. To do this,
// I had to apply to them for permission to apply to them to have them consider sending
// me this sacred tome. This would have involved faxing them a copy of some document or
// other, probably signed in blood. I can only imagine that they make this process so
// difficult because they are intensely ashamed of having created this abomination. I
// was naturally not gullible enough to go through with this procedure, but if I had done
// so, I would have printed out every single page of the spec, and set them all on fire.
// Were it within my power, I would gather every single copy of those specs, and launch
// them on a spaceship directly into the sun.
//
// PSD is not my favourite file format.

I mainly want to get a coffee grinder because beans have a longer shelf life and are cheaper. If I also get better coffee, that's a bonus! (Basically, I'm not looking for a premium option)

What is something I should pay attention to when buying a grinder. I see people mention "flat burr" grinders all the time. Is that something important?

A few years ago I bought a cheap terrible manual coffee grinder off Amazon. It took 5-10mins to grind my coffee. The grounds where too course and my hands hurt. Is the experience better with higher quality manual grinders? At the moment, I'm not a huge fan of manual grinders because of this experience and am leaning towards buying an electrical one.

What makes a coffee grinder better than others? What is the difference between premium and budget options?

Is there a way to directly support boost without going through Google play? If not, that's okay as well.

I'm between distros and looking for a new daily driver for my laptop. What are people daily driving these days? Are there any new cool things to try?

I have been using linux mint recently. I have used nixos and arch in the past. Personally, linux mint uses flatpacks too much for my liking. Although, I might have a warped perspective after using arch. (the aur is crazy big)

Does anyone run their own Lemmy instance on a pi? How was the process of setting it up? Were there any pitfalls? How is performance?

[Edit] So a lot of testing around. Compiling from scratch, etc, etc...

So far i have tried

• installing lemmy using rootless docker (on 0.17.3)
• compiling the image 0.18 docker image as arm

rootless docker did not work well for me. lots of systemd issues and i gave up after running into a lot of issues. I tried rootless docker for security reasons. minimal permissions, etc.

When trying to compile the latest lemmy image in arm, i ran into issues with muslrust not having an arm version. It might be worth investigating rewriting the docker file from 0.17.3 to work with 0.18.0 but i haven't investigated that fully yet! I tried compiling the latest image because i wanted to be able to use the latest features

At the moment, I'm trying to set lemmy to run under bare metal. Im currently attempting to compile lemmy under arm. If that works, i'll start setting up .service files to start up lemmy and pictrs.