riv991

I liked Matt Levine's take in his latest podcast. You buy an index because you want to own the market. If you want to own the market in 2026 you want to own SpaceX and Anthropic, and probably OpenAI too.

That said, if you think this is as bad as the article claims you'll obviously buy SpaceX at IPO, then sell it when Index funds are obligated to buy.

High Scale is so subjective here, I'd hazard a guess that 99% of businesses are not at the scale where they need to worry about scaling larger than a single Postgres or MySQL instance can handle.

> So it is in a bad state because it does not receive enough money, that's it

In real terms the budget is the largest it's ever been, it's a relic of the time when people worked and died shortly (a decade) after retiring, not when they live for 30+ years longer.

It's much easier to maintain, as headsets have become integrated it's become harder and harder to work with anything that runs from the brake levers through the frame.

Microsoft were very quick to highlight their extensions being safer after this.

https://x.com/code/status/1943720372307665033?s=46

In his earlier blog post that this one links, he says:

> I've spent just under 10 years of my life in Prison (all for non-violent drug crimes.)

Isn't that the most impressive part? That the abstraction makes it seem so simple

Something really similar happened to me, I broke my radial head cycling last year.

2 days later I got a call from the doctor telling me to start moving it as much as I could, I asked when I should stop with the sling and he told me yesterday.

I think it's great to see blogs like this, debugging all the way through from the Web UI to the Linux Kernel.

You can argue the complete opposite point with Novo Nordisk. It's up to the foundation to use it's influence

The foundation still owns the vast majority of the company

The eBPF website has a list of projects using it, that can give you a decent flavour of what people use it for. https://ebpf.io/applications/

I really hope Intel succeed here, not because I'm a massive Intel fan, but we need some competition

So sad seeing nuclear energy falling despite all the other good news

Tidal energy is not renewable! We'd be tidally locked to the moon in 1000 years if we used Tidal for 1% of our energy consumption.

https://cs.stanford.edu/people/zjl/pdf/tide.pdf

Great to see Microsoft deploying some of it's capital to develop SMRs, the potential seems great, but governments don't seem to have gone further than nuclear submarines.

It was, they talk about it here: https://sre.google/sre-book/service-level-objectives/

They wrote a pretty interesting blog about the rewrite.

https://github.blog/2023-02-06-the-technology-behind-githubs...

Incredible how you can see CS7 extending from Elephant and Castle to Clapham and Tooting on the map.

I was knocked off there earlier in the year, and the LCC said it has the most dangerous junction for cyclists in London on it.

https://lcc.org.uk/campaigns/dangerous-junctions/

Previously we had no limit. We observed gains in both latency and throughput by implementing Automaxprocs and decided to roll it out widely.

This aligns with what others have reported on the Go runtime issue open for this.

"When go.uber.org/automaxprocs rolled out at Uber, the effect on containerized Go services was universally positive. At least at the time, CFS imposed such heavy penalties on Go binaries exceeding their CPU allotment that properly tuning GOMAXPROCS was a significant latency and throughput improvement."

https://github.com/golang/go/issues/33803#issuecomment-14308...

I love ko, so simple to get a container running in one line and now integrated with GoReleaser.

`docker run $(ko build -L main.go)`

I've seen significant performance gains from this in production.

Other people have encountered it too hence libraries like Automaxprocs existing and issues being open with Go for it.

I intended it to be applicable to all containerised environments. Docker is just easiest on my local machine.

I still believe it's best to set these variables regardless of cpu limits and/or cpu shares

Hi I'm the blog author, thanks for the feedback

I'll try and clarify this. I think this is how the sympton presents but I should be clearer.

The feature I'd love is history.

I'd like to know if my builds are getting slower over time. I'd be able to detect flaky tests automatically.

It seems basic, but I know third-party solutions exist for this. It's out of the box in Circle CI and Buildkite and feels like it should be here.

I think Open Telemetry has solved the stream processing problem issue with span links[1]. Treating each unit of work as an individual trace but being able to combine them and see a causal relationship. Slack published a blog about it pretty recently [2]

[1] https://opentelemetry.io/docs/concepts/signals/traces/#span-...

[2] https://slack.engineering/tracing-notifications/

You don't need prices to fall for inflation to slow (that's deflation). You need the rate that prices are rising to decrease