A year ago I was using claude and found it unexpectedly blowing-away already-settled code. I found this frustrating and just wanted to drop a "save point" where I could compare the before and after versions of certain files. So I built a little utility called "bup" that tarballs the whole code tree and gives it a unique name. It ignores prior backups and has options to ignore certain subdirectories, VCS directories, artifact directories, or secrets files. And you can add a single switch (-s) to create a shell script that automatically backs-up the current project. Yes I can use git for this, but this is honestly way easier, especially if I want to compare/edit different versions. No names. No files. No trees. Just "bup .". And it's 100% bash. https://github.com/maxk42/bup
I'm probably the only one who'll ever use it but I like it.
I managed an adult platform with 200 employees and $75 million in revenue and a dedicated Risk Analysis team. I think I know a thing or two about this, but thanks for the input.
The timeline expired 17 years ago. They've been granted numerous extensions. This deadline is neither new nor "suddenly tight". They were granted another extension last year. They're simply informing Liberty there will be no further extensions. If you have to wonder who's wrong: The utility that's been granting extensions for 17 years or the utility that's been missing their deadline for 17 years I think you'll have your answer if you think about it.
Tahoe is not a town. It is a region containing many towns. Most of it will continue to have power (mostly through NV Energy). This is a single utility that has failed to plan for this planned transition for 17 years. Invoking the data center bogeyman for political sympathy is the only thing going on here. Liberty has failed repeatedly to address this problem for nearly two decades and it's beyond time they were cut loose. I have sympathy for the people who have to suffer from their failure but this is not NV Energy's fault nor is it related to data centers at all: NV energy has been rapidly expanding capacity faster than growth in consumption and has 19 active geothermal plants in the area with more on the way as well as wind and solar.
Chargebacks. "Oh, honey, I don't know how that got there. A hacker must've stolen my card! I'll call the bank immediately!" Worked in the adult industry and traditional e-commerce. It's a perennial problem.
GameStop has zero debt and billions in cash on its books. It is not a stretch for them to be making this offer. It really does make sense here for both sides.
For my use case I need MSL to support fp64. Until that happens I don't care what hardware changes they make: I'm not going to be filling racks with M5s and they're not producing something I can use to even tinker with AI with in my spare time. Apple has lost the AI war before it even got started IMO.
My concern is Cloudflare will implement this plan in a way that makes it very profitable for large players and absolutely kills any new entrants to the market in the future.
...which explains the link to China. NK natives probably do not typically have access to computers or the open internet, but the children of certain elites are educated in China. There may even be a collaborative effort between the two states.
Rust is doing a lot more under the hood. C doesn't track variable lifetimes, ownership, types, generics, handle dependency management, or handle compile-time execution (beyond the limited language that is the pre-compiler). The rust compiler also makes intelligent (scary intelligent!) suggestions when you've made a mistake: it needs a lot of context to be able to do that.
The rust compiler is actually pretty fast for all the work it's doing. It's just an absolutely insane amount of additional work. You shouldn't expect it to compile as fast as C.
Reminds me of the time I spent ten days building a memory allocator based on a red-black tree to optimize lookup times for an interpreter that needed to be fast. When I compared its performance against a linear search, it failed miserably. Turns out the fixed overhead in implementing a red-black tree vastly outweighs a naive approach when you're only dealing with 20 terms or so.