Australis13

Currently testing out Shiori. I have tried both it and Readeck on my Raspberry Pi 3B running 32-bit Raspbian ‘Bullseye’. From an installation and performance perspective, Shiori is easier: 32-bit binaries are available and its web interface is a bit more responsive. If you are not running a 64-bit version of the Raspberry Pi OS, you have to build Readeck yourself (which I successfully did).

The main attraction of Shiori over Readeck is that it has both a readable and archive view. The main downside for me is it lacks the read/unread feature of Readeck and Pocket (although that’s apparently something planned for future and in the meantime, it’s possible to workaround using tags).

Both have a browser extension to enable capturing pages that contain Javascript and do not gracefully degrade. Both also have an export-to-ebook function that may suit your e-reader.

Bottom line: if you have an RPi4 or later, then Readeck is probably want you want. If you’re running an older Pi, though, Shiori may be a better option.

Definitely #1. I’ve encountered #2 with a very specific IDE and #4 and #5 on occasion.

As the senior dev, please don’t.

We work in protoduction.

Nope, just inherited a colleague’s codebase when they left. It’s years later and I still haven’t sorted it all out.

As someone who has inherited code like that, I would like to strangle the first programmer in the comic.

Make sure it’s not whitespace sensitive and requires explicit typing, just to mess with everyone.

Ouch.

I have actually encountered those sort of potential differences between ground planes. They can indeed wreak havoc under the right circumstances.

I can’t decide whether to laugh or cry.

I think it’s just that we’re possessive/protective of “our” code, even more so if one is passionate about programming. We’ve put a lot of effort into it, then somebody else comes along and “ruins” our “perfect” (to our eyes) formatting/styling!

Some linters can do both. Getting one set up as an automated job whenever code is pushed to the repo is on my TODO list…

I felt that. I have a colleague whose coding style is different to mine and whenever they work on code that I originally wrote, I have to resist the temptation to modify things to camelCase.