86 karma · joined October 1, 2015
I somehow feel like making good history just that isn't necessarily a bad outcome given there is always a reasonable chance the site will be butchered by new leadership. Camera pros must have a discord channel or something by now and not need a newly managed site?
Edit: it looks like there may indeed be such a button / command. Really strange they wouldn't communicate the option to keep customers on their services!
- random provider to generate a db password, cloud provider to provision db and admin user, random and mysql providers to provision additional non-admin users, k8s provider to upload credentials to secrets
- tls provider to create ca, k8s provider to create namespace, create certs for each k8s namespace, upload to k8s secrets
- Cloud provider to issue service account key, GitHub provider to upload to GHA (don't do this anymore since oidc is supported, before it was rather important)
While I haven't used CDK much, I believe it is still basically about provisioning aws resources and would not have such cross cutting configs, though I think they may have had a mechanism for importing tf providers.
Terraform can have its issues but overall being able to provision such diverse resources with a single command has been great for onboarding/reducing human error. I'm sure there are plenty of cases where CDK is easier too, these are just to demonstrate why you may use TF even when locked in.
The underwear is for all the "Spend the night at xxx" situations you can probably imagine anywhere in the world (pun intended).
It's unfortunate that this news seems to be captured only for bashing on Amazon or big tech, when it seems to be more interesting as the end of an era - cameras have been eaten by smartphones for almost all non-professionals, and this seems like a capstone to the camera era. Sad in terms of nostalgia but happy in terms of a reflection that tech advances forward. Pros should still do fine, an alternative will come, and maybe use newer tech like Discord or something. Seems like a great opportunity.
Correct - PHP is a scripting language with managed memory, quite different from C. Probably not all, but most WordPress vulnerabilities have to do with issues like sql injection, bad configuration defaults, etc, all in business logic. All of these will continue to exist when compiled to Wasm.
Assuming you actually have access to a database in the first place, while wasmer may have some vendor locked in solutions for it, generally with Wasm you won't get beyond SQLite for the near term.
Then it's just a risk reward calculation - if the possible upside of a crime is $100B with a small chance of eventually being convicted and sentenced to a couple of years in prison, then it's up to each individual to decide whether it's worth taking the chance. I suspect there will be at least one person that does - but once the possible downside is 100 years, then maybe not. A lower value than that may also be fine, but it's all just an expected value calculation in the end.
This is why punitive penalties are needed - both to prevent the same person from recommitting but others from copying. And with money crimes, given the size of the potential upside, it is natural to need a large potential downside to compensate.
It's somewhat unfortunate that the penalty for a mental health crime like murder is actually in comparison meaningless - generally the perpetrators are not going to be making the ROI calculation either way...
新型コロナの起源、研究所から流出の可能性高い＝米エネルギー省
To retranslate back to English as a relatively direct translation
The cause of COVID, there is a high possibility it spread from a lab.
Notably missing are something like 一番, to mean most. This title is in absolute terms. The reason I found this in the first place was because a Japanese colleague was surprised that it did come from a lab! after an initial moment of doubt before accepting it because WSJ is reputable.
I sent the news deck an email pointing it out but do expect it's intentional. Reading as absolute rather than relative is likely "correct" and a great example of misinformation from the WSJ. Presumably reputable news sources just don't exist anymore, or perhaps they never did :(
Any other text such as definitions for the term AI is valid as long as it complies with RFC101HN.
FWIW cold builds (i.e., in docker with no cache) of cargo are much slower than go, hanging for a long time on refreshing cargo.io indexes. I don't know exactly what that is doing but I have a feeling it is implemented in a monolithic way rather than on-demand. Rust has had plenty of time to make this better but it is still very slow for cold cargo builds, often spending minutes refreshing the crates index. But Go misses easy optimizations like creating strings from a byte slice.
So it is what it is - Go makes explicit promises of fast compile times. Thanks to that, build scripts in go are pretty fast. Any language that doesn't make that explicit might be slow to compile and might run fast - that's totally fine and I would rather have two languages optimized to each case than one mediocre language.
Used to spend much time to optimize Gentoo Linux but eventually switched to Ubuntu to be productive. I feel Conda is similarly useful, especially if not considering Docker i.e. local dev, and am disappointed hackers seem to be dismissing it.
My guess is yes and these are issues that would affect both languages equally, with Rust it just happens to be in an `unsafe` block.
In a general sense, this is why there will always be the concept of a loophole, and there will always be those that take advantage of it. Going through every trick to reduce tax liability from millions to 0 seems like behavior that is defrauding the government, but no actions are actually provably defrauding the government.