Live data from Hacker News

Bun: cgroup-aware AvailableParallelism / HardwareConcurrency on Linux

github.com

11–20 of 25 posts

Re: Bun: cgroup-aware AvailableParallelism / HardwareConcurrency on Linux

#12

I had high hopes for Bun, but looks like it has gone down the shitter after they went all in on vibecoding.

Any specific links to problems? I was planning to start a new project on it :(

Anthropic acquisition, what do you expect as outcome?

Re: Bun: cgroup-aware AvailableParallelism / HardwareConcurrency on Linux

#14

I had high hopes for Bun, but looks like it has gone down the shitter after they went all in on vibecoding.

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.

Re: Bun: cgroup-aware AvailableParallelism / HardwareConcurrency on Linux

#15
post #12

Earlier quoted context omitted.

Any specific links to problems? I was planning to start a new project on it :(

Anthropic acquisition, what do you expect as outcome?

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.

Re: Bun: cgroup-aware AvailableParallelism / HardwareConcurrency on Linux

#16

I had high hopes for Bun, but looks like it has gone down the shitter after they went all in on vibecoding.

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.

Re: Bun: cgroup-aware AvailableParallelism / HardwareConcurrency on Linux

#17
post #13

I had high hopes for Bun, but looks like it has gone down the shitter after they went all in on vibecoding.

it's been flawless for me

That's maybe more worrisome, everything has tradeoffs, if you don't know them yet, search for them :)

Re: Bun: cgroup-aware AvailableParallelism / HardwareConcurrency on Linux

#19

I had high hopes for Bun, but looks like it has gone down the shitter after they went all in on vibecoding.

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.

Damn. That one is absolutely horrific.

What a find.

Re: Bun: cgroup-aware AvailableParallelism / HardwareConcurrency on Linux

#20
post #13

Earlier quoted context omitted.

it's been flawless for me

That's maybe more worrisome, everything has tradeoffs, if you don't know them yet, search for them :)

It's worse to assume something is completely broken and anyone who has had a good experience with it to be an ignorant.

I know the tradeoffs. For me it's way better than Node. Especially given the campaign targeting Node devs.

https://socket.dev/blog/attackers-hunting-high-impact-nodejs...

Post reply on HN