Why even try an start a conversation with that attitude? Wayland doesn't get nearly as much hate as Windows, Chrome, or iOS. But I guess literally nothing is worth writing an article that has the word "fuck" in it 7 times, because that crosses some kind of ultimate line?

Do people recommend the API surface should be totally flat and the same for all developers?

Also I'm not convinced that borrowing a device presents a new or different failure mode. Children could always obtain physical contraband from their friends so nothing has changed here.

also doesn't need to IMHO

it solves the problem of it being too trivial for a 12 year old to access content which at best is quite problematic and at worst outright traumatizing

as in, the same reason we have laws that a clerk glances at the age on you id if you look young and buy alcohol but your parent are still allowed to let you drink with them if they think its right (or what a 16+ movie with them etc. etc.)

this is also why it really shouldn't be anything much more fancy then parent controls checking min age of content locally / indication of age for feed fetching. Everything else is disproportional (unrelated from all the other issue it might have).

Most web programmers fall into that bucket for example. If you're the type to recoil at XMLHttpRequest, reaching to fetch or other even newer stuff. Then you'll balk at Win32 and be in a never ending pit of new Windows technology. I'd argue this is true of basically all new software. It's worth starting with whatever the oldest most compatible version of your target and ignoring the advertising and hype.

You can copy/paste or drag code snippets the chat window and they automatically become context like. (@myFile.cpp:300-310)

You can click any of the generated diffs in the assistant chat window to instantly jump to the code.

Generated code just appears as diffs till you manually approve each snippet or file. (which is fairly easy to do with "jump to next snippet/file" buttons)

These are all features I use constantly as someone who doesn't vibe but wants to just say "pack/unpack this struct into json", "add this new property to the struct, add it to the serialization, and the UI", and other true busywork tasks.

you mean an image like this?

This is what I've been running on my generic x86-64 system for a couple of years now, 0 issues. Even migrated to a newer system recently because I wanted something that was slightly faster for ESPHome compilations.

The HAOS ISO cannot install itself onto a machine. That is my minor complaint.

While it is technically no longer supported, you can still install the whole kit and caboodle using pip in a Python virtual environment, but why would you?

This is how I did it, instead of the container or HA OS in a VM.

If you want the simplicity of everything preconfigured, managed, and hands-off, go with HA OS, whether in a VM on a beefier machine, standalone, or the HA Green/Yellow dedicated hardware.

But if you already have a home server and want to add HA, I found just pip installing to be easier than dealing with the container.

Maybe I'm just the silly type that enjoys fiddling with Linux, but I'd argue that it actually makes more sense to install HA bare metal over a container. HA doesn't actually have any major dependencies outside of what pip installs, so setup wasn't any more annoying than via container. And then you never have to deal with container annoyances like passing hardware through to it or weird failures and misconfigurations.

Contrast this with https://frigate.video/, which has so many fragile native dependencies and a super complex stack that trying to install manually is an exercise in futility. I gave up and used the container.

There's nothing wrong with running it on bare metal but this is easier with the VM image.

But clearly people in other cultures have a huge problem with it. Don't fall victim to survivorship bias + echo chamber.

There's not another obvious solution to the problem, it's debated in every thread. (no laptop + homeschool is not a real option for 99% of people)

The problem with this solution is it's far too overly broad while also not working well. It leaves out the most important parts from the legislation while specifying universal compliance.

What the law should have been is "Operating systems intended to be used by minors should have this age verification specification implemented" with a nice documentation of that specification and how it should work. As written, you'll basically end up with the potential that every single OS ends up with it's own age verification system, which defeats the entire point of these laws in the first place.

Saying "all operating systems" puts us in this complicated and dumb position where now an embedded OS needs to worry about age verification of it's user.

Did it in ~300 lines of node.js, was trying to learn how to use JS for server stuff, seemed like a good idea at the time. It still works 5 years later, but it stands as a reminder to me to never use async/await.

What issues did you face with async/await?

Of course you can go full sync if your app wouldn’t do anything useful during the time it’s blocked waiting for network or I/O.