Downvotes are to show that the content does not contribute to discussion. This comment is not related to the top-level post, and looks to be low-effort trolling, so it is not contributing to discussion, and deserves downvotes.

Follow the link and go down to the third point:

Isn’t this just ReactOS?

ReactOS tries to reimplement the Windows NT kernel, and that has always been its Achilles heel, holding it back from a hardware compatibility and stability standpoint. The loss32 concept is to achieve a similar-feeling end result to ReactOS, but built on a more usable foundation, using components known to work well (the Linux kernel, WINE, everything that glues those together, and a sprinkling of ReactOS userland niceties). As a bonus, the OS would still technically be a Linux distro, so it would be possible to run Linux software when necessary, something ReactOS can’t do.

Follow the link and go down to the third point:

Isn’t this just ReactOS?

ReactOS tries to reimplement the Windows NT kernel, and that has always been its Achilles heel, holding it back from a hardware compatibility and stability standpoint. The loss32 concept is to achieve a similar-feeling end result to ReactOS, but built on a more usable foundation, using components known to work well (the Linux kernel, WINE, everything that glues those together, and a sprinkling of ReactOS userland niceties). As a bonus, the OS would still technically be a Linux distro, so it would be possible to run Linux software when necessary, something ReactOS can’t do.

That centralized low-power machine can even be your phone, if it has enough storage for your needs.

This is exactly how I use Syncthing, and as the author says, it sure would be nice if more things were just files. Really, most things are stored locally as files, but not always in a way that plays nice with syncing. Like, I can sync my Firefox profile between machines (it’s all in one folder), but I found it prone to conflicts, with little to resolve those conflicts.

In a similar vein, local-first apps built with Conflict-free replicated data types (CRDTs) can be another way to avoid server dependency. I haven’t seen any significant apps built this way yet (just occasional blog posts about it). I imagine the CRDT approach would work better for individual apps, since conflict resolution can be written in a way that works best for a given app, but I also imagine that such apps would not play nicely with a generic sync solution like Syncthing.

I believe that’s pretty much what happened after the dot-com crash. A lot of fiber was laid during the bubble, it went dormant after the crash, but it was useful afterward as the internet continued growing.

Thanks, that’s an excellent article, and it’s exactly what I was looking for.

I got hung up on this line:

This requires deterministic math with explicit rounding modes and precision, not the platform-dependent behavior you get with floats.

Aren’t floats mostly standardized these days? The article even mentions that standard. Has anyone here seen platform-dependent float behaviour?

Not that this affects the article’s main point, which is perfectly reasonable.

That sounds like an issue with the underlying OpenStreetMap data that is used by Organic Maps (and CoMaps, and OsmAnd, and others). Map quality depends on where you are in the world and who is contributing to the maps there. If data is incomplete around you, you could contribute to it (but easier said than done, I know).

I can’t say why the route would be hours longer than Google maps, but I’ve noticed OsmAnd~ tends to overestimate drive time for me (I think it overestimates delay from traffic lights). Or it could just be that calculating routes on your phone doesn’t always give results as good as calculating routes on Google’s servers.

I used to have scripts like that, but eventually switched to ssh aliases. You can set up an alias for each machine in ~/.ssh/config with lines like this:

Host p1
    HostName 192.168.1.123
    Port 22
    User pi

Then access with ssh p1. Slightly more typing, but avoids adding more commands to your $PATH. Also has the benefit of letting you use the same alias with other ssh-related commands like sftp.

Automatics also allow for engine braking. From a quick search, it sounds like a toss-up as to whether that triggers brake lights. Regardless, the article mentions the benefit is not only from cars slowing down, but also from indicating that a car is preparing to stop or “that a stationary vehicle might initiate movement”. Neither of those can be done by an engine brake, so front brake lights would still have a benefit even with a driver that likes engine braking.

Oddly enough, that convention isn’t universal. Top-to-bottom is typical in the US, UK, and Commonwealth, while bottom-to-top is common in continental Europe and non-anglophone Americas.

I feel like you may have misunderstood the article. It’s talking about how support is increasing for dedicated Copy keys, and that programmable keyboards make it easy to use dedicated Copy keys. The article does not mention changing the behaviour of Ctrl-C.

https://en.wikipedia.org/wiki/List_of_United_States_presidential_assassination_attempts_and_plots#Assassination_attempts_and_plots

You’re correct. You’ll notice every president in recent history has multiple assassination attempts listed. The bulk of them don’t go very far.