[HN Gopher] Bun: cgroup-aware AvailableParallelism / HardwareCon...
       ___________________________________________________________________
        
       Bun: cgroup-aware AvailableParallelism / HardwareConcurrency on
       Linux
        
       Author : tosh
       Score  : 39 points
       Date   : 2026-04-03 11:09 UTC (11 hours ago)
        
 (HTM) web link (github.com)
 (TXT) w3m dump (github.com)
        
       | saagarjha wrote:
       | I feel like https://github.com/oven-
       | sh/WebKit/commit/35315978baee84ed1bd... is the more interesting
       | commit tbh
        
         | jasdfwasd wrote:
         | > p = (char*)"";
         | 
         | yikes
        
           | lioeters wrote:
           | I thought that was a typo or the forum software removed
           | something, but no - it's a pointer to an empty string
           | literal. If I understand how that works, this creates a null
           | byte (in the read-only memory section of the compiled
           | output?) and points to it. Before this line it checks if p is
           | NULL.
           | 
           | I wonder what is the advantage of doing this? Maybe to make
           | sure that p is an actual pointer, so later code can just make
           | that assumption.
        
             | lokar wrote:
             | Yeah, it simplifies later code, and is safer in the face of
             | future changes.
             | 
             | Or put another way, it tightens the API/contract of that
             | chunk of code to always return a valid string.
        
               | lioeters wrote:
               | That makes sense, with that "guard" at the top, the rest
               | of the function can return the pointer anywhere. And I
               | imagine the compiler will ensure the empty string literal
               | is created only once. Good to know!
        
       | elffjs wrote:
       | Something from the PR description that I had to look up to
       | understand: "WTF" is "WebKit Template Framework".
        
         | dboreham wrote:
         | That comment put my brain into an infinite loop for a while...
        
         | himata4113 wrote:
         | I had to take a moment to find out why all primitives in chrome
         | were in the WTF namespace.
         | 
         | WTF is just kinda funny. Seen it used in loggers too
         | log.wtf("this should never happen")
        
       | phplovesong wrote:
       | I had high hopes for Bun, but looks like it has gone down the
       | shitter after they went all in on vibecoding.
        
         | gear54rus wrote:
         | Any specific links to problems? I was planning to start a new
         | project on it :(
        
           | pjmlp wrote:
           | Anthropic acquisition, what do you expect as outcome?
        
             | gear54rus wrote:
             | Best case is they throw their endless amount of paper at it
             | without touching it. At least something useful comes out of
             | this AI crap then. One can dream.
        
         | pier25 wrote:
         | it's been flawless for me
        
           | embedding-shape wrote:
           | That's maybe more worrisome, everything has tradeoffs, if you
           | don't know them yet, search for them :)
        
         | loevborg wrote:
         | This was pre-Anthropic but the fact that Bun automatically
         | loads .env files if they're present almost disqualifies it from
         | most tasks https://github.com/oven-sh/bun/issues/23967
         | 
         | It makes it hard to take them too seriously with such a design
         | choice - a footgun really. It's so easy to accidentally load
         | secrets via environment variables, with no way to disable this
         | anti-feature.
        
           | rvz wrote:
           | Damn. That one is absolutely horrific.
           | 
           | What a find.
        
         | hu3 wrote:
         | I still have high praises since one of my clients use it in
         | production.
         | 
         | I personally use it's tooling part which is screamingly fast.
        
       | boomskats wrote:
       | Haha, did I just hear someone whisper GOMAXPROCS?
        
       ___________________________________________________________________
       (page generated 2026-04-03 23:02 UTC)