acuteaura

You’d have some standing if Anthropic actually acted in the interest of the public.

You do realize the NSDAP won elections too, right?

I mostly avoid this place these days, but there are certain topics where people hyperrationalize, i.e. they (silently) accuse others of being reactionary because an argument looks like reaction to them on the surface.

I started self-censoring on HN because I knew some very normal and on-topic things to say would be voted to oblivion because they had the shape of a controversial topic that the average HN commenter can not relate to except through some mainstreamed right-leaning cultural narrative. The mere mention that I was an affected party in some culture war adjacent thing was treated as if I had invoked a thought-terminating cliche. It was very... anti-curious.

So I principally agree on the conclusion, when emotions get activated this site gets worse. I just see the impact differently - anything that deviates from the libertarian-right leaning default is pushed away. I'm still relieved I had my pseudonymous account with a lot more HN internet points wiped and don't have to care about this site on an emotional level anymore.

My secret hope is that Tim Cook was the main weight behind cutting off half the new features from Apple software in the EU an attempt to weaponize their users against legislators. Even features that have had analogues where nobody would've ever asked for interoperability (i.e. Handoff/Continuity exists in the EU, but iPhone mirroring doesn't)

This is not how politics works here.

I should clarify that my doctor explicitly lied to me (found out by requesting my medical file after moving) to shock me on purpose because of his own fifth grade understanding of psychology.

There is a fine line between being opposed to fat acceptance and thinking performative cruelty works.

(It's does not. It made me so much worse. I have nothing but bad things to say about the medical "professional" who catastrophized my diagnosis to "wake me up" and then shrugged when my response was depressed resignation.)

I don't see the contradiction to what I said or what the prior commenter said.

CPU requests still protect you from something using all the resources, because the weights correspond to your number vs all the other pods on that node, and the scheduler will not schedule pods so they exceed the total available resources.

So more accurately, requests prevent exceeding limits under contestion, and limits always do.

Where do you think the contradiction is? A CPU limit of 1 does not prevent an application from using 8 cores worth of compute at once, it just limits the compute to 1 core per 100ms slice on average, and usually that means getting unscheduled for 7/8 of the slice, if the app is using all available resources and nothing else contests them (weighted by requests).

Some workloads will also consume all the resources you hand them without being latency sensitive at all.

I've handled outages of CPU time available getting suddenly compressed (we were running pod priorities with staging/prod on one cluster and up to 70% spots in 2019) and then learning that some very important applications outgrew their original requests, gone unnoticed because limits were removed a year or so prior. You can fix this with monitoring/right-sizing tools, but that requires your org to not be dysfunctional, and my style of platform engineering usually has to account for the org being very dysfunctional.

It's not as much an "overhead" as it will mess up your latency. Limits don't stop you from using available resources until you hit the relative allowance in a CFS window, so a 1 CPU limit on a 32 CPU machine at worst gives you 32 cores for 3.3ms every 100ms.

More literally a Microsoft product. As in, rebadged Azure Pipelines.

I'm not sure if this is a joke or not, because it has all the signals of a joke, but it might be closer to true than I'd like to admit.

At my work, the average quality has gone up with "blindly trusting Opus". The failure modes are horrendous and the code is verbose as shit, but it still works better. Most "engineers" aren't very good at writing code.

Oh, what a wonderful shorthand to dismiss an entire article.

GitHub Actions was always a mess. Because it is a Microsoft product.

If you want to have a horrible time, try reading some of the runner code. It's early 2010s-style Windows-First, MSFT C# crud that has trouble not racing several threads to inconclusive status codes.