coastalpuma

In that case, it will be their own dang fault. Modern MacOS is a mess of update nags, unwanted notifications, and permissions prompts. We want sandboxing and security patches but the UX around it is abominable.

Which are these "world-class delivery organizations" and are they the exception or the rule?

We can acknowledge that political volatility is a main cause but it's not some exogenous factor. It's inherent to the federal structure of the country and it hamstrings trying to build social goods, whether that's transit or healthcare infrastructure.

There is also nowhere near a culture of developing and trusting institutional planning expertise. Infrastructure is done on a pork-barrel basis of which promises will get who elected and create which jobs and allocate which contracts. Or who complains the loudest about the design of any given plan.

Canada's 20th century social system was also based on maintaining social stability through mass property ownership, which is now breaking down as unrestrained property speculation is displacing any kind of productive investments (while also ending the possibility of that mass property ownership in the near future).

Sorry to bring the negativity but I feel as a whole that Canadians are much too tolerant of institutional dysfunction (in the manner of the classic "Canadian nice") and think our society is far more advanced than it actually is. It's a completely complacent and naive culture that is quickly being left in the dust by more functional systems.

Wezterm is an excellent project but it doesn't have native UI chrome like Ghostty does.

Last weekend I was writing some quick notes in the Notes app, and I could not get it to stop performing nonsensical completions in blinking yellow text. Apple Intelligence disabled, predictive text disabled, various combinations of backspace escape etc. Nothing worked. How hard is it to code a Notes app that doesn't mess with you?

I really wish homebrew supported this feature. There are a bunch of terminal tools I have installed through it (and wouldn't make sense to sandbox) that are basically one-person projects, and I imagine subject to supply chain compromises. I don't urgently need the very latest versions for any of them, as they are unlikely to have exploitable security vulnerabilities on my machine (due to not being involved with any network facing service).

I do kind of think the solution to this issue lies at the OS level. It should provide a high degree of UI and workflow standardization (via first party apps, libraries and guidelines). Obviously it's an incredibly high bar to meet for volunteer efforts, but the user experience starts at the OS level. Instead of even installing a program like "Handbrake" or "Magicbrake" the OS should have a program called "Video Converter" which does what it says on the tin. There should also be a small on-device model which can parse commands like: "Convert a video so it can play on facebook" and deep link into the Video Converter app with the proper settings. Application-level branding should also basically not exist, it's too much noise. The user should have complete control over theming and typography. There has to be a standard interaction paradigm like the classic menubar but updated for modern needs. We need a sane discoverable default shell language with commands that map to GUI functionality within apps, and the user should never be troubled with the eccentricities of 1970s teletype machines.

> The benefits touted are very abstract

Not really? From someone's post here a year ago:

> The real innovation of a lot of these alternative DVCS systems is that they free the state of the source from being dependent on the history that got you there. Such that applying patches A & B in that order is the same as applying B' & A' -- it results in the same tree. Git, on the other hand, hashes the actual list of changes to the state identifier, which is why rebasing results in a different git hash id.

Anybody who's wrestled with reordering/rebasing git history or has done git archaology is able to understand this benefit.

From Pijul's site:

> Pijul is the first distributed version control system to be based on a sound mathematical theory of changes

After years of grudgingly tolerating using a deployed prototype for a VCS, yes, I want the mathematically sound alternative.

All that being said, I do wish you the best, because truly, I am tired of git and JJ does seems like an improvement.

Agree, the feature of commutative patches just seems obviously superior? Not sure why there's a critical mass to adopt jj over Pijul apart from jj's git backend.

I can easily imagine a world where you could install an open source PWA from an archive file into its own security sandbox without any further hoops to jump through, and it continues to just work indefinitely because the web has very good backwards compatibility guarantees. Instead, we have to get licensed and notarized by the monopolies and they keep you on a constant treadmill of drudgery just to stay up to date. Or you install somebody else's monopoly-approved "legitimate business" app which steals or leaks your data. Sad!

I think this is amazing work and I'm looking forward to trying it out and maybe adopting long term, but I can't help but think they're selling themselves short with the default theme. Personally find the electric blue pretty grating. Would be nice to see more examples of "calm" theming with more neutral tones, or even a preset alternative default for that.

If you're an amateur and really want to spend this much money, get a good enough knife (e.g. the classic victorinox) and a chef's choice electric sharpener, and you won't have any more issues.

We shouldn't accept "sideloading" as a term. It's meant to make "installing an app without monopolist approval" seem like a dirty/weird/niche trick.

Amen. I am praying for the day when cars honking on lock is banned.

I think people are dismissing the possibility of universally accessible self-hosting too quickly. We really need to be ambitious as engineers and imagine a future where people have sovereignty over their own computing. In 1990, we wouldn't have accepted someone else taking custodianship of our personal documents, memories, books, music, and films, and yet it's normalized today. With the benefit of hindsight, we need to brutally simplify every single layer of the stack and optimize it for being usable by non-technical people.