Does a background check in the US imply that they'd never consider anyone with any blemish on their record whatsoever? Surely it just means they have to make an informed decision.
1,395 karma · joined October 6, 2016
Does a background check in the US imply that they'd never consider anyone with any blemish on their record whatsoever? Surely it just means they have to make an informed decision.
Once they transfer a secret to us, I just move it out of the guest vault into another one. When I transfer a secret to them, I ask them to confirm that they have it and then I remove it from the shared vault.
My understanding is that Chernobyl was caused by an experiment that went wrong due to errors in following processes correctly.
I would assume that most reactors just make electricity, and outside of smaller reactors used for research they aren't used for experiments. Is that correct?
I'm definitely interested to hear about similar games - I was never able to find anything that quite compared. Amnesia looked quite dated and unpolished by comparison after playing SOMA and I couldn't quite get into it.
But I'd suggest using Terraform really, once you get the hang of it, you won't want to go back to using the console.
I'm sure that you could either build your own using xterm.js [0] or by using one of the many projects that implements it. I'm not sure if systems manager uses this project but it certainly looks very similar.
Much as I loved it, I was keenly aware that I was a second class citizen without access to the integration or the mindshare. Also, git really isn't all that bad but I do miss Mercurial, I think it deserved to win.
On the other hand, if this plays out the way they want, then they get 100% of the income (less overheads) which would be an absolute win for them.
I don't think their motivation matters however - as an ISV getting kicked off the app store is no longer a potential death sentence or a wasted investment; you just need to get smart about how you distribute.
I think this has been inevitable for some time, but I think by making this mistake they have they they've accelerated the process and damaged their monopoly far earlier than they had to.
Note: Perhaps I am just seeing what I want to see here. I am hopeful that I and other independent software vendors will be able to avoid their app store one day.
It's not illegal however if you signed a contract to that effect, which is what you did when you started using the platform.
A better analogy is that you're renting some furniture and the furniture is found to be unsafe. The company can come and take it away, either replacing it with something else or refunding you.
In the software world nobody but the creators or IP holders of the software actually owns the software. They just provide you the license to use it.
It's illegal in many countries to modify the software so if you had a closed-source word processing application it would be illegal to mod it or to use it as part of a data transformation pipeline. You can only use it for the purposes stated when you bought it.
If there was a way to limit your oven to bake recipes the manufacturer allowed or to use specific approved ingredients, and would come with some sort of value-add to make consumers ignore that as a problem, I'm sure someone would actually do this.
(please note that I am stating facts as I see them and not necessarily agreeing with the state of affairs)
Terms like boxing and reference comparison come to mind but I can't stitch them into a narrative to explain this.
This is already an AWS feature: https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitori...
We have an internal tool that listens to a message queue, dumps a database (from a list of permitted databases), encrypts it and sends it to S3 to be investigated by developers.
When running on a container, the process takes 2-3 minutes with small databases, about an hour or more with larger ones. When running on a regular EC2 image, the process takes about 5 minutes in the worst case scenario and is borderline instant with smaller databases.
Mapping internal volumes, external volumes, editing LLVM settings, contacting AWS support etc yielded nothing. Only migrating it to a regular EC2 instance had any results and they were dramatic.
We run Docker containers for local development too but when restoring very large databases we need to use MySQL in a real VM instead of in our Docker setup because Docker crashes when faced with a disk-heavy workload.
So to conclude, the only reason I wouldn't want to containerise a workload is when the workload is very disk IO heavy, whereas most of our apps are very network IO heavy instead.
I think when working with a piece of hardware that requires a specific driver the user is best placed to go to the manufacturer website and download it.
You should upgrade - it'll be a considerable boost to your computer's speed and your productivity. SSDs are pretty cheap now.
You can stay using a HDD if you like but I don't think it's going to get better.
It made it easy to spot this part, which I guess is normally tucked away. Respect for drawing my attention to it but I have a question - is this a standard thing that you would find in such a document? It feels like a pretty serious liability for a user to take on.
> SUMMARY: If we get sued by a third party, you will defend us and pay for all losses, damages, etc, if the lawsuit relates to your Content or use of the Service, your breach of the Terms, your violation of a third party’s rights, violation of your rights by a third party, or an action by you that is overtly harmful to another User.
Also, then let's say you get a mega-enterprise customer that wants to host it in their own cloud account, you simply apply the same configuration to that new account. It's quite something to see thousands of cloud resources created over the space of an hour, thinking how long it'd take to do it by hand.
However, as you say, the 'Simple' part is definitely a misnomer.
We'd definitely notice.
You can also set up workflows such as your client owning the encryption key that encrypts data held by you and they can revoke it at any time. Slack has a similar system and I was asked by a large financial institution about the same. I expect to see this more in future.
Doesn't include monitors though (£600ish for 2 27" monitors). It's a pretty beastly workstation, great for development.