You could use just a regular 5 min epoxy. I frequently use CA glue, but depending on your use case, it might be too brittle.
Yes, not gonna happen. You know how many new devices get sold simply because old ones are no longer getting updates/software support? It's planned obsolescence. No modern country would pass a law like that.
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.
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.
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.
Hard to tell From the photo, but might be Ash. If so, it would make a great axe handle. But you can of course make an axe handle out of any hardwood, it will mostly be fine.
Well, I think it's a valid comment. I'm a big fan of her work and I watched a few streams, but the voice seems like it's heavily processed, and to me it's barely intelligible, which makes me concentrate really hard to try and understand what she's saying. I ended up not listening to her streams. I now prefer to read blogs and other people's articles about her and Asahi linux in general.
Wow, 3nm, we're nearing Moore's law ceiling, what a time to be alive. 55% is impressive to me at least.
Is the game playable? Might try it if so.
Well, I've been a C/C++ dev for half of my career, I didn't find Rust syntax ugly. Some things are better than others, but not a major departure from C/C++. ObjC is where ugly is at. And I even think swift is more ugly. In fact, I can't find too many that are as close to C/C++ as Rust. As for logic.... Well, I want to say you'll get used to it, but for some things, it's not true. Rust is a struggle. Whether it's worth it, is your choice. I personally would take it over C++ any day.