Understanding the Go Runtime: Profiling

https://internals-for-interns.com/posts/go-runtime-profiling/

by valyala • 15 days ago

19 8 15 days ago

throwaw122• 9 days ago

Since this is shared by @valyala, I feel comfortable trusting the content, but is the original author of the blog delegating all writing to AI or are they genuinely this smart to produce high quality content this fast?

For example see here their series about Filesystem internals: https://internals-for-interns.com/series/filesystems/

Reason I am asking, should I add them to my personal "Human blogs to read list"

xnacly• 9 days ago

the art is def ai generated, text seems okay thusfar?

stingraycharles• 9 days ago

Nah, it’s full of LLM-isms. There’s a lot of focus on “there’s not just one profile, there are five”, “it’s not A, but B!” and other “X is to Y what A is to B” style content that obsesses over comparing different concepts.

Laurel12342• 9 days ago

Clanker image emdash emdash emdash emdash emdash emdash not to X but to Y

tomrod• 9 days ago

Sidenote, that is a great idea. Mind sharing part of your list?

throwaw122• 8 days ago

part of it

https://muratbuffalo.blogspot.com

https://www.allthingsdistributed.com/

https://brooker.co.za/blog/

https://surfingcomplexity.blog/

5701652400• 9 days ago

I have nothing against AI blogs. Ideally it saves cost, so my AI does not need to waste compute to generate all that. We all likely have same models (Fable vs Sonnet vs Deepseek tiers of course) which produce same result for same input. So just save yourself tokens.

If it is human-reviewed AI blog, even better.

And if my AI can collaborate and improve/build-up/fact-check that article, perhaps our AIs working in GitHub Issue on those (which is a missing link now). That would be even better.

Laurel12342• 9 days ago

Or we could just use our fucking brains, how about that?

Understanding the Go Runtime: Profiling

Related Stories