So, not the droid we Are looking for... :(

~~mexican~~ russian joker

From my small experience with Qualcomm in the past, I'm not too hopeful. In a company I used to work for, we wanted to use one of their SoC with Linux, which they claimed they supported. It was many years ago. But was full of closed binary blobs which even when signing NDAs, we couldn't get the source for. We're talking user-space drivers, sensors offloaded to a separate core with closed source firmware etc. It's Linux, but it's not Linux in spirit, it feels so closed and proprietary and secretive. They're coming from Android, which google architecturally enabled vendors to close their drivers by utilizing HAL. It's the single most significant blow to Linux by any corporation so far. It enabled thousands of vendors to close their shitty driver in user-space and not maintain it for newer kernels (kernel driver is just an IO proxy for user-space drivers). I get that without it, there wouldn't be Android phones we have today, but I expected them to slowly open up. 10+ years later, almost nothing changed, in fact - things seem worse to me.

Any PC that has virtualization features can be used. Unless it's very old, I'd say it's supported. But it may not be enabled in the bios by default. It's called VT-x for Intel and AMD-v for AMD, I think. But both are supported for at least 10 years on almost any PC.

It's a hypervisor level virtual machine host and you can use it to install multiple os's on the same machine with little overhead. I've been running haos like that for a few months now and I'm super satisfied.

Because you can't end to end encrypt if you don't have control over both ends. You'd need to trust the other end. Signal doesn't and their user base especially doesn't.

There is indeed multiple ways of doing anything in freecad. But over time, I prefer staying in Part design as much as possible as this makes it more modifiable and customizable and there are plenty of reasons more for me. But in the end - whatever works is good enough.

Shape binder is what you need. Shape binder can be used to reference geometry from another body. What I would do is I'd make one pocket on the main body. Then select another body and make it an active body. Then select the pocket you made (the surface or the edge) and create a shape binder (part design). This will effectively import the selected feature from the first body and you can reference it from second body. Make sure you hide the first body, as it somehow gets in the way of shape binder, for some reason. Repeat for third body.

Well, it's not 2024 just yet. And besides that, I don't think it's possible to completely control everything that gets imported, but I reckon it's going to be a rather rare occurrence in the future.

It's often about the money, yes. But highly sought after engineers who can choose where they want to work probably have other criteria too, like not getting stuck in MS corporate ladder long term. That being said, money compensates for a lot of things, that's just the world we live in.

One of the bigger reasons is ZigBee is capable of mesh network forming, which is useful if you want more devices to be smart. It's also low power. And the devices are in their private network isolated from the internet, which is also a desirable quality. In summary, ZigBee is built for smart devices, whereas wifi not so much.

This is great! I've only recently discovered jq and was thrilled to have it after bashing my head in bash for a couple of days. I replaced the whole operation with a single line. This tutorial is just what I need. I like that it's interactive and has neatly grouped examples! Bookmarking it, as I'll need it very soon again.