This is one of the aspects of AUR which never fully convinced me: it purely hosts user-generated content, there's no review process or alike.
I'd really prefer to see a model where a 'community' repository contains user submitted packages which have at least one Trusted User review the package before it's merged in. This doesn't just prevent malware, but also common mistakes in general.
This is essentially what the [extra] repository is. Not using the AUR and sticking to official Arch Linux packages exclusively is a very valid and reasonable choice (that I follow myself actually).
A large number of "an Arch Linux update broke my system" is very likely due to incorrect AUR use that AUR helpers don't handle for you. There's an elaborate writeup here from just 2 months ago: https://lists.archlinux.org/archives/list/arch-dev-public@li...
I used GNUCash years ago in Argentina while we had high inflation. Some operations were in local currency and other are Dollars. The currency exchange changing hourly. Tracking finance is a nightmare, since you basically need an exchange rate for every operation.
> Yeah, this difference occurred to me while traveling in rural Mexico. To play soccer all you need is a ball. So you can go into the poorest villages that have little in the way in infrastructure and all the kids are playing soccer in the dirt road or a random field, etc.
The same is true in Argentina. And in school kids play almost every recess too.
A lot of very prominent player from Argentina had this kind of humble beginning too.
It’s also “the sport”. Americans don’t really do casual sports anymore and there is a ton of competition in the various leagues.
In many parts of the US, soccer is a fall sport that competes with football in school leagues. Football teams require a small army of players and tend to suck out the oxygen. It doesn’t help that there’s no little league equivalent for soccer, so there’s a ton of pay to play BS to a much greater degree than football or baseball.
In my area, you need to commit to a full year travel soccer team that’s often owned by the school coach to get any playtime in high school.
USAmericans casually play basketball still. Basically a few kids shooting hoops at every little court you pass, and lightly organized (just show up at a time) adult games are common too.
Woodworking sounds like a solid way to steer a career. Un-impacted by LLMs, or any trend/hyper or that matter. Great for keeping the body active after decades of sitting all day. Your produce (literally) tangible products. And above all: there's always a need for more skilled carpenters.
Most of us would not be able to become woodworkers or carpenters for a living. If white collar jobs get so affected by AI probably the competition in blue collar jobs would produce the worst race to the bottom.
There's guaranteed persistence, but there's no guarantee that the host will be up anytime soon. E.g.: I might leave a final reply with all the details on an issue before going on vacation (or maybe I don't work the next day but my colleagues abroad do!). I see that it's properly posted and close the laptop.
The reply with be delayed by days or weeks, but the UI indicated that it had been properly saved.
Edge case but playing devil’s advocate: a user can also uninstall the native app at any time, and might still expect their last change before they closed the app to be reflected in the web version.
You can never truly trust anything about a client because by definition you don’t control it
Corner case: actually, it can. Also, thats how auto-updating works ; depending on local state as a source of truth using browser apis is a terrible idea IMO.
The whole concept of "assume it is committed while we sync in the background" is, in the most cases, a terrible architectural decision, unless it is coupled with explicit feedback (eg. A small visual indicator indicating if the background queue is empty or syncing). Also, it breaks temporality: last-update-wins no longer holds, because update time and sync time are decoupled. And you also create a new problem, which is local cache coherence.
It may be a good fit for some systems (though I cannot think of a single one), but in general is just a horrible solution.
I'm sure there's a sum of compliance reasons why this is not allowed, but it doesn't make any sense at all.
reply