That moment when when the CEO is back in the hotel room, and realizes he just authenticated to a laptop that was not his would be an ideal moment for the assassin that looks very similar to him to exit the hotel bathroom, pop the CEO, dress in his clothes, and proceed to the bank for wire transfer shenanigans.
Node has a low barrier to entry(JS), and that shows in the quality of the work. If anyone remembers QBasic, it was hated for the same reasons. It's great to grasp core concepts with, but inappropriate to build something like an ERP system. It's a toy, although a powerful one.
> What's your position on the current third shot issue? Should we listen to the scientist panel that said no, or the government that said yes?
We should listen to ourselves. If we don't have enough information to make an informed decision, then study and acquire that information. No one is responsible for you except for you - with the caveats of children/dependents being not responsible for themselves.
What Youtube or any other internet information says is irrelevant until you decide otherwise.
> Do you think that YouTube did a good thing by allowing that content?
They didn't do a good or a bad thing - they were a blank canvas someone put their art(video) on. Recently, that blank canvas is only willing to have certain art present on it - that's not a good thing. The only thing keeping it going is an inertial mass of subscribers, which over [possibly a long] time will dissipate.
Could you share a little more about your experiences with mp? I'm in the other camp - I use multiprocess in several python applications and am more or less happy with it. My real curiosity I suppose is what data you are trying to pass around that isn't a good candidate for mp.
My own use cases normally resemble something like multiple worker-style processes consuming their workloads from Queue objects, and emitting their results to another Queue object. Usually my initial process is responsible for consuming and aggregating those results, but in some cases the initial process does nothing but coordinate the worker and aggregator processes.
My main issue with multiprocessing is that the pickle module is incredibly unhelpful when something can't be picked. Given that there's quite a lot of context shared between types of analysis, and that context tends to change a lot, using pickle means I'm looking at quite some time debugging every now and then to see what's failing.
Regarding the data itself in this case, there are some objects that are references to in-memory structures of a C extension. Last time I checked I didn't see simple ways to share those structures via pickle. Shared memory was an option, but it required me to implement and change quite a lot of things just to get things working, not to mention that whenever the C extension gets new features I need to invest extra time in making those compatible with pickle. It wasn't worth it, specially knowing that I would still run into problems every now and then due to pickling the context.
In other news, operational security is just as important as technological security measures. This means not leaving your device unattended, and if you do, implementing tamper detection of some variety. This can be as simple as a battery operated motion activated video recorder hidden and aimed at your equipment. You can pick one up for $25 on amazon.
Well... I think meritocracy is perfect, it mirrors evolution in rewarding superior contributors(ie, on their merit). However, being in the "elite" mentioned in the article does not imply you have merit. People in that "elite" might have merit, but they might also just have rich/powerful parents, connections, and friends. If that's the case, then they aren't "elite" based on their merit, but based on who they know.
That moment when when the CEO is back in the hotel room, and realizes he just authenticated to a laptop that was not his would be an ideal moment for the assassin that looks very similar to him to exit the hotel bathroom, pop the CEO, dress in his clothes, and proceed to the bank for wire transfer shenanigans.