I really have to agree with the "easier to debug" part. I one time had to debug a particularly nasty networking issue that was causing HTTP connections to just "stop" midway through sending data. Turned out to be a confusion mismatch between routers and allowed packet sizes. It would have been so much worse with a non-plaintext protocol.
That assumes that any amount of capitulation would have persuaded Trump to support Ukraine, and that any reasonable deal could have been reached. I obviously can't say what could have been, but every sign Trump (and those in his administration!) has given up to this point indicate that there's only one outcome they support, and that's Ukraine surrendering all or some of its land to Russia, along with a deal barring Ukraine from NATO.
I'm very curious to see how this comment ends up ageing. saved for follow up ;)
My prediction is ukraines got three options;
-Show europe that the US is an unreliable trading partner, and get them to commit atleast $500B, with SF troops coming to ukraine to train their troops.
- Make a deal with trump.
- lose their country.
Yes, and that's also the only outcome Russia would accept, unless Putin is replaced by a US puppet, which seems unlikely; such a puppet would be deeply unpopular in Russia and have great difficulty remaining in power.
The people in Crimea, Donetsk, and Luhansk would also reject any deal that doesn't involve Ukraine surrendering some of its land, either to Russia or to some sort of Republic of Texas limbo-state. So, even if Russia were taken over by a CIA asset, fighting there would continue unless extremely repressive measures were taken.
So that sort of deal is the only way to end the fighting with anything resembling humanity, even though Trump supports it. Stopped clocks, etc.
What software should be doing is using XDG_CACHE_HOME, if it is set (along with the other XDG environment variables). That way cache directories will be where the user expects.
1. short and easy to read,
2. good for users, and
3. can be implemented in five minutes.
If we can't have programs follow this simple decades-old convention, we have no hope whatsoever of voluntary consistency in our computing world. It's literally because of the mentality espoused in this article that we can't have nice things.
Unfortunately, we have nothing but social pressure and incensed HN comments to get developers to follow it. That's why the mobile world adopted a "you shall" model: a developer won't spent five minutes to save a million years of user time unless there's some social or technical guardrail forcing his hand.
Agreed. What op wants in this case, is for XDG_CACHE_HOME to default to ~/cache when unset.
The idea is quite reasonable: suddenly all tools that show disk usage will show this directory clearly and you can easily find what’s eating up you space with the same usual tools as always.
I think they'll find they're in the minority on that opinion, so they should just set XDG_CACHE_HOME, and maybe symlink ~/.cache to ~/cache for those programs that have just hardcoded ~/.cache
Are dot folders actually a problem? I have show hidden files turned on globally everywhere always. I don't really understand how people operate otherwise.
No idea. All I know is whenever I try to execute the module in e.g. VS Code's debugger, it somehow triggers the attack and enters a de-facto-endless 100%-CPU-load loop.
Several papers have already been published that modify the DeepSeek R1 model through further optimizations. The author is speculating that open source models will continue to be published and that DeepSeek is unlikely to be the front runner indefinitely.
I've always wondered why the name "Direct Rendering Manager" was chosen, given the existing definition of DRM. It could have just as easily been "Direct Rendering Layer" or some other alternative.
It always bugs me when I see that pattern in JavaScript, because each `map`, etc. call is an array allocation. Yeah, yeah, I know that the VM's memory allocators are likely optimized for fast allocation, but that doesn't make the allocation completely free.
At least with Java you can select a GC which is more aggressive in giving memory back to the system (Shenandoah and ZGC). With Electron/Node you don't even get that (not to mention the fact Electron apps always spawn multiple processes).
