It’s as easy as pie too; they show up right there on the boot menu:

I really don't understand why people have this little awareness of usability. Show the freaking date normally! At least add hyphens.

We tried Dolphin and Konsole as Flatpaks for a while, but the user experience was just terrible.

Yeah I'm fairly sympathetic to Flatpak. It's way closer to how software should be installed by users. But I have yet to actually use it successfully. Is it really ready?

I dunno I would say Lisp syntax is probably the worst option. Or APL style.

Assembly is very simple (at least RISC-V assembly is which I mostly work with) but also very tedious to read. It doesn't help that the people who choose the instruction mnemonics have extremely poor taste - e.g. lb, lh, lw, ld instead of load8, load16, load32, load64. Or j instead of jump. Who needs to save characters that much?

The over-abbreviation is some kind of weird flaw that hardware guys all have. I wondered if it comes from labelling pins on PCB silkscreens (MISO, CLK etc)... Or maybe they just have bad taste.

I once worked on a chip that had nested acronyms.

Still better than Device Tree though right?

I feel like the best option at the moment is egui. It's native. Works on the web too. Very easy to get up and running. The things I don't like about it:

• I personally think the default style could do with improvement. Mainly it's way too cramped. There's a happy middle ground between no padding and bootstrap. I mean Win32/Qt/etc. got this basically right.
• Immediate mode. Yeah it's easier, especially with Rust, but ... it's surely not how it's supposed to work.
• The low level drawing API (like if you're making custom widgets) is surprisingly amateur. Not something I'd want to target if I'm spending a lot of time e.g. writing a custom map widget or git graph or something.

I also tried Slint. Like the author I think the license is pretty reasonable. But it is pretty involved to set up a project and since it compiles everything from source it can take a very long time for a clean build of hello world. It's like if you were using Qt but instead of a binary package the sources are just included in your app.

Also I have bad experiences from QML (Javascript 🤮, weird scoping rules, etc.) but hopefully they learnt from their experience.

Looking forward to the 2030 edition anyway!

Ah yes phpBB those were the days. Wait, no they weren't. They sucked. Old forum software was one of the worst computing experiences I remember.

Want to download a custom Android ROM? Hope you like reading through this 120 page thread one page at a time. Oh and each message will be surrounded by a metric mile of profile pictures and signature.

RSS was pretty great though, I'll give you that.

Yes, use them. One big advantage is if you hover something in an IDE it will show you the docstring.

If you're writing Python you should be using Pylint (or Ruff) and it has a lint to ensure you write them.

The exception I usually make is for class member variables because it's super weird that the docstring comes after the variable. I think that's very confusing for people reading the code so I normally just use comments instead.

I assume he meant Linux on x86 laptops, where I can confirm battery life is atrocious and support for random display things is also pretty bad. My laptop still wont do more than 30 Hz over HDMI (works fine with DisplayPort though).

Oh yeah I can't read 😄

I would be extremely surprised if any compiler was smart enough to short circuit that.

I would be a little less surprised if checking the whole string was actually faster anyway though... but I would still bet against it.

One of the things I hate about merge-based Git workflows is git makes a default Merge 123234234 from user/dave/fsdf message which:

a) Is shit - it contains zero useful information (what's in the change??) and contains information you explicitly don't care about (the temporary branch name the author happened to use). a) Makes people think they are supposed to use that message.

It would probably be better if the default message was blank. But also squash & rebase is generally better anyway and it avoids this problem entirely.

I'm not sure hardware-based full disk encryption counts as a "highly specialized requirement". It's enabled by default on Android, iOS, Mac and even Windows usually. It's a basic requirement for businesses.

Yes. For the project I work on pip install takes about 60 seconds and replacing it with uv reduces that to about 7 seconds. That's a very significant improvement. Much less annoying interactively and in CI we do this multiple times so it saves a significant chunk of time.