dmlittle
dmlittle on Hacker News
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.
It depends on how much effort you put into it vs. just using any of the base templates/components that Tailwind Plus (previously Tailwind UI) has to offer.
If you look at their Showcase section[1], you can't tell it's using TailwindCSS for most of them (imo).
[1] https://tailwindcss.com/showcase
Just an (uneducated) guess here, I don't believe capsules carry the necessary amount of fuel that it would take to accomplish this.
> C) Only one staging env per customer. Want to check what a new setting will do? Every developer is getting that setting turned on.
Stripe Sandboxes[1] aim to solve this problem!
(Disclaimer: I work for Stripe but not on this feature)
[1] https://docs.stripe.com/sandboxes
Thank you for TA'ing the class! I took it in 2015 and TAs really made the class for myself and most of my friends.
Is the end of semester Leisserchess competition still going? I believe I heard that the year you TA'd it (might have been a year before or after) a group finally compiled an opening playbook and beat everyone in the class
I believe the original Kubernetes proof of concept was written in Java
fly.io is another popular one
How do you go from "25,000 requests per second" (25krps) to "one request every 3 seconds"?
It might be plan dependent(?) but everything you’re describing is configurable on your PagerDuty profile. I have it configured to send me a notification immediately followed by a call if I don’t acknowledge it within a minute (yes, this is aggressive but I’m in a high urgency, quick response time SLA rotation)
Right. I meant to say there are groups capitalizing on the situation
> Shocked that no VC or group of them haven't stood up a short term bridge loan facility since it was them who triggered the chain reaction that took the bank down.
Several groups are. They're offering anywhere between 60 to 80 cents on the dollar for the uninsured amounts. https://www.reuters.com/business/finance/hedge-funds-offerin...
(Disclaimer: I haven't looked too much into this tool other than a cursory glance)
It seems this tool isn't meant mostly for testing how different components behave under different scenarios and/or load. This is probably particularly helpful for custom controllers or operators. What happens to your controller if it's constantly reconciling 100k pods? What about 5k nodes? Something else? If this tool makes creating a "loaded" cluster easy, it's definitely handy. Would have saved me some time doing something similar a few months ago.
For what it’s worth sometimes it’s worth abandoning old legacy context in a rewrite if the new solution drastically reduces operational complexity. For example, it’s cheaper/better to retrain everyone on the new solution than it is to continue to onboard new folks to the legacy one. This is not always the case, but sometime it is as the parent comment mentions.
> GraphQL forces you to write business logic on the client
Even if you have traditional REST endpoints, you still have to potentially orchestrate their usage client-side.
Depending on the size of your cluster, scaling out the apiservers is not necessarily cheap as the watch caches need to be initialized which puts load on etcd. Generally speaking, it's probably better to scale the apiservers vertically rather than horizontally.
Adobe removing support for their products in Apple products would have just created a void that someone else would have filled.
The same reason frontend and backend teams exist. At a certain point it makes sense to have centralized teams focus on specific verticals than requiring everyone to learn/know about everything. As with any tools, there are right and wrong ways of using it and using the wrong tool for the job can sometimes be more painful than not using it at all.
Despite its name CLRS goes WAY beyond an introduction
I was given the chance to vet my future manager once. I was presented with a candidate that had been in 11 different companies over the course of 8 years. We passed on them as soon as I pointed this out.
Job hopping a few times is not a bad thing by itself but the reason why you’re doing so might be. In my case I didn’t want to hire a new manager only to repeat the process again in 6 months (their track record suggested they’d do it again). There’s also a _huge_ difference between having 8 years of experience and 8 first year experiences. As pointed out by GP the hard and complicated things/decisions come after a while in the job and you’ve onboarded and gotten context.
AWS S3 does the opposite when querying objects that don't exist. If you don't have s3:ListObjects permissions on the bucket you'll get a 403 error (you can't differentiate between the object not existing vs. you don't have access to it).
I think either approach is valid as long as you're consistent. You can make a case for either 404 or 403 when you don't have enough permissions. In GitHub's case you can argue that it's a 404 because the resource does indeed not exist through your auth context. In AWS' case you can argue that a 403 makes sense because you don't have permission to know the answer to your query.
If you have any requests I'm happy to try to to implement them!
I'm not really looking at it from a cost savings perspective since the operational cost is so low that even an hour of work covers paying for multiple years of it running. It really boils down to what different platforms I want to try out but you're right that Cloudflare Workers is another one to consider.