timw4mail

There's a font manager in Crosspoint and Witch, you can download that font directly from the device.

I have not seen any support on the mini readers.

My favorite at this point is Witch reader (https://github.com/jpirnay/witchhunt-reader). All the features of Cross-point, with better book rendering, and more features. I've tried a lot of the various alternatives, and keep coming back.

If you want all your book series displayed together, AALU (https://github.com/dawsonfi/aalu) might be worth a look.

And Crosspoint OS itself is still really nice.

And I see the opposite: Safari is a valuable check on constant additions and bloat to the web platform.

Progress, or constant churn for the sake of Google's stranglehold on web standards?

While true, aircraft fatality statistics generally are not split that way.

The 747 is a safe aircraft, but there have been a lot of fatalities associated with it, due to pilot error, terrorism, improper repair/maintenance, etc.

Hard to beat other planes that have not had fatal crashes or hull losses, especially when you consider the Tenerife crash.

But the point of Deno was to try to avoid pitfalls that became apparent in NodeJS, so some over-correction was bound to happen.

Officially? A single cpu G4 tower. Beyond that, I'm not sure.

While I agree in terms of modern browser expectations (and books absolutely should not need JavaScript), I think books in HTML makes a lot of sense. HTML was meant for sharing text documents, after all.

As a crazy person with both, I have mixed feelings between them.

In favor of the X3:

- Crisper text

- Whiter display

- Slightly better battery life

- Top-mounted power button (subjective)

In favor of the X4:

- Larger display

- Plain USB-C charging

- Slightly better custom firmware support

- Backward and forward button on the same side (subjective)

More mass = more momentum = harder crash. That's physics.

For the bigger vehicle, perhaps, but a smaller vehicle, even if up to modern standards, is less safe due to the larger one.

...and that's why I've always hated that name

Confirmation bias, instant communication, hyper focus on Boeing mishaps, etc.

And here I felt like I was wasting money on an Intel B70 to run LLMs locally.

Syncthing

Beta it may be, but there's a good amount of software and programming language support. The 64-bit version is amazingly stable, even on the nightly version.

Resource efficiency is a huge one. If you are familiar with the Via Nano: it's a SLOW x86_64 chip (sometimes used in thin clients) that feels about half as fast as older AMD 64 cpu. Haiku feels great on a Via Nano, and it's really storage-space-efficient. Linux distros are slower, and use more storage space (especially important for using an OS on a thin client PC).

Wait...what year is it again?

I've never seen the appeal of GNOME 3+, the design seems so user-hostile to anyone who has used computers for a while: hiding menus for no reason, having super limited menu options, etc.

I'd rather use LXDE, XFCE, or KDE.

The only case where I care about an IPv6 address is for something I actually want to expose to the internet. A temporary address would be quite annoying in that case.

Some 486SX boards are even sillier: There's a soldered 486 SX, and a regular 486 socket, so you can add a socketed 486 SX to your board with a 486 SX. Obviously the point is to be able to add a regular 486 CPU, but it's still amusing.

Surely something like OPNsense/PFsense would be better for the average user than setting up all the software manually?

Pentium-compatible processors were more numerous than you think.

- AMD (K5/K6/K6-2/K6-III) - Intel (Pentium) - Centaur (IDT Winchip, later Via C3/C7/Nano) - Cyrix (6x86, 6x86MX) - Rise (mp6)

For the vast, vast majority of use cases, they are faster, yes.

Cyrix chips get too much hate because of Quake being optimized specifically for the Pentium and its FPU.

Homebrew wouldn't support Haiku anyway.

No.

And there was the same problem with early PS3s, on Nvidia's GPU package...it was a fairly widespread problem at the time.

The code style seems to be targeting some old version of PHP...but I'm absolutely sure typed properties require a newer version of PHP than existed in 2008. (If I recall correctly, that's around the days of PHP 5.4 or so)