diegocg

... 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.

LWN merge window part 1 https://lwn.net/Articles/1067250/ Part 2 https://lwn.net/Articles/1067785/

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

> The total addressable market — every emerging-market saver who would prefer dollars to their local currency, every cross-border worker sending remittances home, every small-business operator outside the conventional banking perimeter — is, by any honest estimate, several trillion.

Emergent market savers are already buying dollars. Nobody in Argentina saves money in pesos, for instance, so there is no much demand there left (and Argentina is the country that holds the largest amount of physical dollars after the US).

It is a fantasy to suggest that there is a magic, hidden demand of dollars that can be measured in trillions (coming from emergent countries, of all the places). At least, not one that would not be controlled by local authorities, just like they do today. Governments can control who tries to buy some random crypto with the local currency. Not when it's done in small amounts, but anything sizable will be noticed. The idea that crypto or stablecoins can somehow enable capital flight measured in trillions without governments being able to do anything does not make much sense.

I could imagine it being promoted as a tool to launder money in some way, though. Just buy this stablecoin via some tax haven, we will make it equivalent to holding US debt, and we won't ask where the money comes from. I would bet that's where the tether/usdt money comes from. Drugs, arms trafficking, perhaps that could provide some of the liquidity that the US Treasury needs.

All this Mythos talk reminds me of fuzzing. The number of vulnerabilities discovered greatly increased. But bugs were patched (often, without even assigning CVEs), systems were upgraded, life continued. Outside of the tech world (and even within it), nobody noticed. Many software companies still have not adopted fuzzing.

If Claude finds security issues, so what. Some systems might not be updated, but these systems are vulnerable to even a single security issue, they were unsafe already. Systems that are upgraded don't have that problem. In fact a high rate of security fixes will make them safer, as zero-days kept in secret by government security agencies for long time become patched.

With fuzzing we didn't see articles talking about the geopolitics of security vulnerabilities. Investors didn't finance fuzzing startups with hundreds of billions. There is way too much propaganda.

Well, that's exactly what the article is about. Wayland put all together into one process I order to avoid unnecessary context switch. This protocol aims to keep the performance advantages of Wayland without giving up on separation of graphics c server and window manager.

Foreign operators are mandated by the EU, they can't be banned. Spain has been one of the first countries to allow foreign high speed operators (unlike other European countries that did attempt to delay their entrance as much as possible

Have you read the article? He didn't just ignore her. He combined periods where he ignored her with periods of caring only to hurt her in dark ways.

> Once, she says, as Jobs groped his wife and pretended to be having sex with her, he demanded that Brennan-Jobs stay in the room, calling it a "family moment." He repeatedly withheld money from her, told her that she would get "nothing" from his wealth — and even refused to install heat in her bedroom.

This isn't just a career driven person

I'm surprised that governments didn't take this problem more seriously. Obesity is a huge problem, people have been ignoring it only because improvements in medicine have been offsetting the general health decline. Without the medical improvements that save the life of obese people, life expectancy would have decreased. I don't expect the Trump administration to make the best decisions but at least they are taking it somewhat more seriosly.

There are certainly other use cases. git bisect was enormously useful when it was introduced in order to find Linux kernel regressions. In these cases you might not even be able to have tests (eg. a driver needs to be tested against real hardware - hardware that the developer that introduced the bug could not have), and as an user you don't have a clue about the code. Before git bisect, you had to report the bug and hope that some dev would help you via email, perhaps by providing some patch with print debug statements to gather information. With git bisect, all of sudden a normal user was able to bisect the kernel by himself and point to the concrete commit (and dev) that broke things. That, plus a fine-grained commit history, entirely changed how to find and fix bugs.

At this point it would seem that the cause for the current outages goes beyond the original DNS issue.

As someone who uses D and has been doing things like what you see in the post for a long time, I wonder why other languages would put attention to these tricks and steal them when they have been completely ignoring them forever when done in D. Perhaps Zig will make these features more popular, but I'm skeptic.

This makes me sad. AI is a product, these days being mentally healthy should imply having the emotional ability to be aware of that. If you become emotionally attached to a commercial product you should seek for help.

I wonder if it would even be helpful because they avoid the increasing AI content

I would say that the lesson here is that cross-vendor replication is more important than intra-vendor replication. It is clear that technology can (largely) avoid data losses, but there will always be humans at charge

Yep, for me it confirms all the reasons why I think python is slow and not a good language for anything that goes beyond a script. I work with it everyday, and I have learned that I can't even trust tooling such as mypy because it's full of corner cases - turns out that not having a clear type design in a language is not something that can be fundamentally fixed by external tools. Tests are the only thing that can make me trust code written in this language

Reminds me of all the optic fiber infrastructure that was built during the dot com bubble

The problem is that even when you give them context, they just hallucinate at another level. I have tried that example of asking about events in my area, they are absolutely awful at it.

Don't worry Mark we will also get AI based ad blockers

You can laugh but Google stats show nearly 50% of their global traffic being ipv6 (US is higher, about 56%), Facebook is above 40%.