Yeah, because that's the exact sort of hardware musl is aimed at.
Here's my counter-bogus-statistic: musl is infinitely faster than glibc on a Nios II processor because musl will fit into memory and glibc won't. Therefore, don't use glibc if you care about your code being able to run. QED.
Internet Archive provides their scans in various formats and AA seems to mostly archive a very poor one. I think what you're describing is the result of a post-processing step for one of the space-saving derivatives. It's worth looking up the book on the IA and see how it looks there. Very often, I found that it looks excellent on IA, but terrible, borderline unreadable, in the AA copy. The difference is also obvious in the file size. Generally I found the quality of the original scans of books scanned by the IA to be excellent.
I liked the transparency very much. Had it enabled in Windows7 for all of the 14 years. Until software incompatibility forced me to install Windows 10.
Nuclear, while exorbitant, is necessary for security. See North Korea vs Iran/Venezuela. Nuclear scientists, supply chains, and a trained workforce takes decades to develop. Excess power production can be used to smelt aluminum. You can always have strategic excess supply of materials that can use flexible supply.
This is virtualization, so localhost will just be the virtual iphone itself. But you should have some command of how hosts are resolved, so you can always point the browser to the device hosting what you want to test, no?
Even easier, of course, is just using the iOS simulator included with xcode, which runs on your host computer. There, localhost resolves to your host computer.
> the fact that you mention the military "shooting back" when we're discussing a jet-engine being sabbotaged suggests that you believe a state is allowed to be / ought to be disproportionate in its violence towards its citizens.
That is in no way a good faith interpretation of what I said.
My original point was that, for many professionals, there is a strong incentive to go local with their AI models the same way you wouldn’t be able to use cloud storage without the assurance the data would be physically stored within a specific region.
> I'm substituting my own[0] vibe coding for buying[1] apps. Language mini-games to help with German? A few prompts. Fluid dynamics simulation for an airzooker? Vibed. A web app listening for a MIDI keyboard, upon which you can drop some .midi files, and get a rhythm action game to learn the piano? Vibed. Webcam for my Raspberry Pi? Vibed. Getting Marathon 2 (well, the open sourced and upgraded engine, Aleph One) working as a web app? Vibed. Isochrone maps? Vibed.
When do you have time for all of this? I don’t mean the vibing part but the using the app part.
I agree that agents are super good for one shotting throwaway code for tasks that would have required manual human actions previously but I would never have bothered buying an app for that.
Not having to deal with IT support for relatives is a win though since now I can just throw it at an LLM!
"After 2005 we have been constantly pestered by prosecutors and security forces (and even by the Vatican! [4]) asking us to hand over users’ data and identities and we are proud to say we were always able to answer: we are sorry, but we do not have them."
André Robert Breton was a French writer and poet, known as a principal theorist and co-founder of surrealism. His writings include the first Surrealist Manifesto of 1924, in which he defined surrealism as "pure psychic automatism"
I've never run a bank either, but their current setup is very cost effective. A true multi cloud architecture would be "much" (a couple of 9s) more available, but I believe it would introduce other issues. The goal was to ensure the use of a subset of features for short periods of time, which is probably already above the market standard.
Not sure how you managed to do it but you got it completely backwards.
If someone demands that the database should use fsync and only respond with success once the write finished, it is not some arbitrarily high reliability demand that needs to be implemented using reliable hardware. In fact, the entire point of implementing the power loss protection in software is so that you don't need perfectly reliable hardware. The power loss event turns into a downtime event which is often completely acceptable.
The requirement to have infallible hardware only emerged because the software refused to do its job. Infallible hardware is not a requirement decided by the user, it's a requirement decided by the developer of TurboKV to intentionally restrict his software to exclusively operate in a reliable hardware environment.
The fact that the user specified durability of the KV store during power loss does not make the user obsessed over hardware reliability, the software shifted the burden onto the hardware and forced the user to deal with this mess.
I don't know how exactly TurboKV works so let's talk about a hypothetical software instead.
Let's say the software cannot survive a power loss event and just corrupts the database. If the user wants to operate the software, he is forced by the software to operate it in an infallible environment where power loss can never occur. Based on how the software was designed, power loss is a catastrophic event. The SIL2 type reliability you're talking about only makes sense in contexts with catastrophic events.
So how it went is that the user made a reasonable demand with bounded reliability: "please survive power loss with durable writes" and the author says, sure just run the software on a SIL2 type reliability hardware environment.
It's not the user who blew up the hardware requirements.
I've never talked to someone for it, and I would've first done it in something like 2008. (It's 'always' been done by SMS, well before 'apps' that might let you (and I don't recall it on websites).)
160 square meters, which if ran in optimum conditions would reject between 100 to 150 kilowatts.
Micrometeorites is not a significant concern. There aren't that many of them and 100% reliability is not required. If one is hit then you end of life it or de-rate it (i.e. shut down some of the processors or underclock them) appropriate to the lost solar energy or lost radiating power.
Server clusters already replace racks every 5 years or so and dispose of them. (It used to be ever 3 years.) How is this any different?
