diegocg

This is a project that insists on using CVS so yeah, it's not surprising that they do not try the most modern development techniques

... do not migrate old repos? I'm not sure why people would do that. Or, if they do, why would they replace the current repo name instead of creating a different one and keeping the old one closed to make the references work.

I don't think this is going to be a problem at all.

KDE has clipboard history, for the record. Persistent across reboots. I can't understand why it's not more prevalent

So the article shows how visa and mastercard are, by far, not the ones taking the largest fee, and the solution is to get rid of them?

Where are you going to do the transactions in your scheme? Because credit card transactions are not the same as sending money from one bank account to another. There are settlements, disputes, chargebacks, etc.

How is the central bank going to offer the same variety of products described in the article? I.e..

> Interchange fees vary dramatically based on the kind of card, category of spend, and even the metadata attached to a transaction. The network’s goal is to set fees that incentivize desired behaviors on their network, including using more secure payment methods (lowering interchange fees for merchants), or for companies to do more business spending (higher interchange fees on commercial credit cards).

Your scheme sounds like all these crypto guys who think they can replace credit cards with bitcoin transactions, as if they were the same thing

Yeah, that point was weak. The argument went from "Unix pipelines are not simple" to "unix based operating systems don't have an equivalent to Clojure's frequency function by default so it's worse"

OK but how would it look like if you had such a program? Shells are not known for having the extensive set of functions that real programming languages have.

Ask the luddites

Which, as the post notes, it's incredibly stupid. So much for artificial "intelligence"

Linux 7.2 modifies the task scheduler to be more cache-aware and is able to co-locate tasks that share data within the same Last Level Cache domain. It also adds a fairer GPU scheduler for better scheduling of GPU jobs; better memory reclaiming that can provides large performance increases in some situations; more performant and leaner swapping implementation; support for USB4STREAM, which allows to send data streams through USB4 cables; performance improvements in Btrfs; a new dm-inlinecrypt storage target for inline block device encryption: new flags for the openat(2) system calls; faster reading of /proc/filesystems and /proc/interrupts; and preparations for the introduction of sub-schedulers in sched_ext. As always, there are many other features, new drivers, improvements and fixes.

Oh, that UI paradigm already exist. It's just that browser makers are too busy with things like webasm, webgpu, or allowing pages to launch location/notification popups at users, so they don't have time to fix fundamental flaws.

If things were that simple...

I have to use more than one Python type checker because there is not a single one that works. Not only different tools catch different issues. They also have different bugs, and different configuration requirements. Different teams have different preferences.

It's a nightmare. If Python taught me something about typing is that a language that doesn't have a clear definition of types in the reference implementation, it will never get it fixed with external tooling.

The worst part for me are the false positives. I frequently need to get into the spam folder to discover emails that Gmail thinks they are spam, even though there is absolutely no reason for it. I have been thinking about leaving it.

Anything running on a battery will need hardware acceleration

This is way vague to not be AI slop