It would be nice though, if syntax like the following would be supported:
struct A
{
int a;
};
struct B
{
int b;
struct A a;
};
void foo (struct A * a)
{
struct B * b;
&b->a = pa;
}
struct B b;
foo (&b.a);
Deleted Comment
And while the kernel is quite secure against hacks from userspace, the hardware interfaces are generally more trusted. This is not a problem on smartphones or embedded devices where you can obfuscate everything on a small SoC but the whole PC/x86_64 platform is much more flexible and open. I doubt there is a way to get reliable attestation on current desktop systems (many of which are assembled from independent parts) unless you get complete buy-in from all the manufacturers.
Finally, with AI systems recently increasing in power, perhaps soon the nuclear option of camera + CV + keyboard/mouse will become practical.
Obviously not an approach that scales, but I think it can also work decently well as a dev environment, where you want to run "stock" for most of the components in the system, and just be syncing in an updated workspace and restarting the one bit being actively developed on. Being able to do this without having to reason about a whole tree of interlinked startup units or whatever does lower the barrier to entry somewhat.
If it's super fast, it's just for a few items, and a cashier would've been just as fast. If it's for a lot of items, there's a decent chance I have to look up some codes or something; which a cashier is better and faster at.
The trade off of self checkout is cost savings for the business. These savings are not passed on to me. Therefore, I don't give a flying rat's ass about them.
I'm with OP. If I'm working for the business, they will compensate me. Willingly or unwillingly.
Deleted Comment