Why though?
fushuan
When you think about it, low humms sound soothing so... I guess he was right? I do enjoy humming to myself sometimes.
Shared poibters are used while multithreading, imagine that you have a process controller that starts and manages several threads which then run their own processes.
Some workflows might demand that an object is instantiated from the controller and then shared with one or several processes, or one of the processes might create the object and then send it back via callback, which then might get sent to several other processes.
If you do this with a race pointer, you might end in in a race condition of when to free that pointer and you will end up creating some sort of controller or wrapper around the pointer to manage which process is us8ng the object and when is time to free it. That's a shared pointer, they made the wrapper for you. It manages an internal counter for every instance of the pointer and when that instance goes out of scope the counter goes down, when it reaches zero it gets deleted.
A unique pointer is for when, for whatever reason, you want processes to have exclusive access to the object. You might be interested in having the security that only a single process is interacting with the object because it doesn't process well being manipulated from several processes at once. With a raw pointer you would need to code a wrapper that ensures ownership of the pointer and ways to transfer it so that you know which process has access to it at every moment.
In the example project I mentioned we used both shared and unique pointers, and that was in the first year of the job where I worked with c++. How was your job for you not to see the point of smart pointers after 7 years? All single threaded programs? Maybe you use some framework that makes the abstractions for you like Qt?
I hope these examples and explanations helped you see valid use cases.
Anniversary of tiannmen square I suppose, talking in to account that the latest complaint posts were about people that were banned for sharing link about it.
As stated in my comment:
You shouldn't tolerate intolerance
Bro, I'm gonna asumme you are just creating fake outrage, holy shit.
It's not really about the hardware, is it? The option you mentioned won't enable an alternative app store, it won't enable access to android app emulators (which would be a huge boom in the open source app offering). The level of trust iPhone users give to appeal is wildly higher that what android users that tweak their phones give the manufacturers. It is what it is, but don't delude yourself in thinking that it's about what they do in the kernel level, it's about the fact that they store tons of sensitive data in their american servers and that they have an obligation to share that data with the country, and as someone from Europe that doesn't sit well with me.
I think that it's about intolerance, some people are using a term in the intended non-slur manner, and others are intolerant about that rational desire. Even tolerant people shouldn't torerate intolerance, so no, being pissed about people telling them to stop using the term in the intended non-slur way is not toxic.
If that really hurts you, it's a you thing. It's not intentional, the meaning isn't derived from the slur, it's not a micro aggression. You won't like the answer, but toughen up.
Apple issue then, quite the anti feature. In any case, I hope the IT team learns from it and they create a company ID or several company IDs so this doesn't happen again haha.
100% agree, just take into account that most people you encounter on lemmy, specially on posts about security, are in that 1% that tweak stuff and if you throw blanked statements they will think you are talking to them specifically.
Oh, I assumed that you would be forced to type your password or have enough rights to install stuff in a computer, be it in person or remotely, so I assumed that whatever 3rd party program they used required to have enough access, and that apple would use the apple id as a master password, given that it's what is being used to lock down the device itself.
Well, yet another issue with apple lol, why add a ownership id if it's not even what gives root access. Lmao.
The issue here is that while baseline apple is more secure than baseline android, a user with knowledge or a guide can improve the android security by a lot, whereas the apple baseline is also the ceiling. There's stuff you can do with iPhones but if you don't trust apple, you are kind of fucked.
Android people that mention security won't be using a stock phone from the store, they will have disabled stuff, enables alternative stuff, or even installed a completely new android based OS, and this can't be done with iPhone or iOS.
I did create one in the nsfw instance and it has the same username as this one, but it's not been used since it was created mostly, so just one.