Yes, although that's not new. The amount of different exploits and RCE I've seen in the past decade from just "opening" an PDF is mind blowing. Not sure if it's slowed down but around 8 years ago ghostcript would patch a couple of RCE from PDF processing every few months.
It's worth noting that GPUs have a much higher failure rate than traditional CPUs. Over 10x the failure rate due thermal stress. The amount of heat generated is very different. You can't really replace a GPU in a satellite (at least today?) which would place most of these satellites as space debris in a ~5 year horizon.
It's been a while since I've checked this but a few years ago we tried to limit test kine on a large-ish cluster and it performed pretty poorly. It's fine for small clusters but the way they have to implement the watch semantics makes it perform poorly (at least this was the case a few years ago).
The node failure rate is much higher than that. On a 1M node cluster of cloud-managed instances (AWS, GCP, Azure, etc.) you'd likely see failures a few times a month, if not more.
As someone who recently interviewed (although not at Facebook) the number is the _annual compensation package at the time they signed their offer_ (it includes base salary + annual stock grant + bonus). If someone got $1,000,000 in annual compensation 2 years ago, the stock portion per year will likely be larger now due to appreciation of the stock. These numbers are crazy high and before I interviewed this time around I was somewhat skeptic of how real these numbers were outside of a few outliers but now I'm pretty sure it's pretty common.
Ive never had a good experience with whiteboard paint. The walls are not smooth so you always leave some residue when removing the ink. Over time it becomes pretty noticeable unless you spend a significant amount of elbow grease cleaning it.
It all depends on your use case. If your input is bound to a small N, I’ll take the simplest to understand implementation regardless of algorithmic complexity. Future you and other people will thank you later.
I think it depends on what you’re doing. The author of the the Reddit post mentioned he’s primarily working with data systems. I can see the appeal of someone running quick, ephemeral data analysis not wanting to deal with static typing. But for long term use cases the static typing guard rails is definitely nice.
I was referring to the root accounts in your organization. The blast radius is more limited, but still a root account that has access to everything within that AWS account.
They just raised more funding in a Series D[1]. CircleCI isn't the only player in the space and GitHub entering the playing field doesn't change that either. There's enough space for a few competitors and having competition will probably push everyone to build a better product.
https://www.youtube.com/watch?v=4FdGIRBUds4