For local usage on linux there’s virt-manager, has been good enough for my use at least, and the integrated spice client has relatively good graphics performance for normal desktop use.

Edit: don’t know about a good gui for running qemu on windows, though

I find it funny how whoever originally created this meme somehow ended up using a picture of Macintosh II (or IIx, IIfx) to represent a computer. An over 30 yo mahcine, which while capable of speech synthesis is not going to talk to you without being requested, unless you’ve configured something very incorrectly.

Feels a bit like a floppy disk still being the save icon; computers are still being presented with floppy drives and a CRT monitor in clip-art and such.

SEO is of course a problem, but it’s been a problem for a long time, and there are ways around it for those who know how to seek information. Proper use of keywords, blacklisting sites with known spam information, searching specific sites, mandating specific words and phrases to be contained in the search etc. It’s true, however, that information has become less discoverable during the latest decade – at least reliable information has.

While AI-written spam articles and such have been a pain sometimes, gatekeeping content is in my opinion as big of a threat to the proper use of search engines for finding information. As more and more sites require you to log in to view the discussion (social media is the worst offender here) much of the search results is unusable. Nowadays the results lead to a paywall or a login wall almost more often than to a proper result, and that makes them almost completely useless. I understand this kind of thing for platforms which pay for creating the content, e.g. news sites, but user-generated content shouldn’t be locked behind a login requirement.

I fear the day StackOverflow and Reddit decide the users’ discussions should be visible for only logged-in users. Reddit has already taken the first steps with limiting “NSFW” content to logged-in users only (on new reddit). Medium articles going behind paywall also caused some headaches a while back.

Well, the example was with a tent which is a single layer of cotton between you and the environment, and by no means resembles anything even remotely insulated. That’s why it needs a relatively powerful heater to stay comfortably warm. In normal use you have quite a lot of control over the temperature of the heater, mainly with the size and amount of firewood -> effective surface area of the fire.

For static buildings the situation is different, with enough insulation you can get by with almost no heating. Zero-energy building is a thing in Finland as well, and although it has its challenges, it’s still possible to keep your home warm with only your body heat in e.g. -40. The main difficulty you’ll encounter there is getting rid of the moisture in air, since being that energy-efficient will require having your home almost fully enclosed. You’ll also need to be careful to properly limit the moisture getting out from the house, as the dew point will be inside the insulation and any moisture getting out will condense inside, eventually leading to mold.

I haven’t actually reached the end game in Frostpunk 1, but at a glance it would require some efficiency improvements and better insulation – and given enough insulation and heating anything is possible. If your people are sleeping under the sky hugging the generator, I’d assume you won’t get past the end game. A real-world example that somewhat resembles the Frostpunk world would be people living in Yakutsk, Russia, where they have more of a brute-force approach to the -60 °C temperatures – just burn enough gas to keep your log cabin warm. Surviving outside at those temperatures without protective equipment would be difficult though, especially since most materials won’t stay flexible at -120 °C or -140 °C. You’d find it pretty difficult to move around.

Edit: But also, a mandatory “don’t quote me on this”, as building is my hobby, not my job. I’ve some knowledge, and some experience, but by no means am I a professional.

It’s safe enough, in the Finnish army we occasionally get the tent heater red hot, and as long as nothing flammable touches it or is too close, it’s fine. It will radiate heat quite well when that hot, but won’t be anywhere close to dangerous if you know what you’re doing. In the tent we of course have some water nearby to extinguish the possible flames but still.

You basically need to have it glowing red if you’re to keep the tent warm in -15 °C or lower. - 30°C needs something closely resembling the picture posted.

Here’s an example, unfortunately hosted on Reddit https://www.reddit.com/media?url=https%3A%2F%2Fpreview.redd.it%2Fjiquty6qz7s51.jpg%3Fwidth%3D1080%26crop%3Dsmart%26auto%3Dwebp%26s%3De4b8083400858eccc1786d7b32b94b759b2bc6c2

A Nokia 5310, before moving over to a ZTE blade gen1. Really liked the XpressMusic phones, and their proper headphone out and proper signal levels when using it. Trying to use the aux on car stereos with any following smartphones before my current Xperia 5 III was hopeless, since the maximum voltage levels were so low you had to turn the amplifier volume up to 11 just to hear anything…

A mercury arc rectifier. The mercury vapor is ionized, and used for increasing the current carrying capacity of the component – compared to how much a traditional valve design with complete vacuum would work.

In short, it makes DC out of AC.

My best guess is the dates on which the feature was added, which can also be seen on CanIUse. Firefox added OPFS support in March this year, and much of the userbase (AFAIK e.g. Firefox ESR) is still lacking the feature – in any case it’s a very recent change on Firefox. However, webkit/Safari has had OPFS for over two years by now. I was personally unaware of the support having been added to Firefox as well, last time I checked the discussion they told they weren’t going to implement the API.

By no means is this an acceptable excuse in my opinion, this kind of check should always be done by checking the existence of the feature, not the UA string. Though it might be that the check is still performed in the correct way as Safari users stuck on older version are also encountering the issue. But if they’re fine with using OPFS, where you need to export the files separately to access them outside the browser context (as the storage is private), there’s no reason to complain about recent Firefox versions that support this feature.

But, the same point still stands, kind of. The main underlying problem is Google forcing new standards through Chromium, without waiting for industry consensus and a proper standard. Then, as 80% of the userbase already has the feature everyone else is forced to get on board. I still don’t really see Adobe as the main culprit here, despite the apparent incompetence in writing compatibility checks, but Google with their monopolistic practices with the Chromium project. Adobe isn’t innocent and has done the industry a lot of harm in the form of being one of the original pushers of subscription software, but I don’t think this instance should be attributed to malice rather than incompetence.

Edit: So, a bit of additional advice for someone trying to get this to work: in case the UA spoofing doesn’t help, check the Firefox version in use – it has to be 111 or newer, as 111 was the release where File System API support was added. Firefox ESR probably doesn’t have it available. Also check that FS API / OPFS doesn’t need to be enabled through some flag or configuration parameter, and that it’s not blocked by some plugin.

Well, in this case it might even be a technological limitation, which can be solved with a workaround but leads to a poor user experience.

Firefox, for security reasons, doesn’t allow opening local files for writing. That means, it’s not possible to make a web application that can autosave to your machine after you open a file, meaning you have to download a new version of the file every time you save. You can get around this issue by importing the files in question to the browser’s local storage, or by using cloud storage via an API, but local saving is a feature that people have come to expect and missing it will lead to complaints from the users.

The missing API is called File System Access API and has been available on Chrome for years. I’ve personally had to write my web apps around this limitation multiple times, since I want to support Firefox. By no means is this a valid reason to exclude Firefox in my opinion, but I can also easily see why a company would want to not bother with user feedback on ctrl+s not working in their web application.