• 2 Posts
  • 27 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle


  • 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.










  • 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.







  • 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.




  • If it works for you, don’t touch it, great. Manjaro mostly just works, but occasional headaches I kept getting, like packages being broken for days at a time, no easy place to look for solution (their repo being different to arch’s makes 99%of the difficulty) made me switch to arch/endeavorOs. Eventually, they may get stable enough to be acceptable, but I don’t think their way is the right way to do it and they may even harm or slow down arch development and community in the process. Just looks like arch with extra steps, so I always recommend endeavorOs, Garuda or plain Arch, before Manjaro. But that doesn’t mean Manjaro is trash and in some cases, it may even be the best solution.