Live data from Hacker News

I am worried about Bun

wwj.dev

101–110 of 368 posts

Re: I am worried about Bun

#103
post #91

Earlier quoted context omitted.

January of last year. Yes. https://nodejs.org/en/blog/release/v23.6.0

That is type stripping and is incompatible with syntax that requires transpilation, so it is not native TypeScript support.

TypeScript is a wide umbrella. For instance, Experimental Decorators are shunned by many (including me), but they are still used by millions. If I don't use any syntax that requires transpilation, am I not still using TypeScript?

Now that we have `satisfies` and `as const`, there's really no reason to ever use an enum. In my opinion, TypeScript is best when it is simply used as Language Server, and it should never have had runtime implications in the first place.

Re: I am worried about Bun

#104
post #101

Earlier quoted context omitted.

Looks like AI slop https://github.com/PerryTS/perry/issues/139

the AI replies itt are cringe

Seriously. It's one thing to use AI to write code but spamming machine generated garbage when talking to another person is just rude.

Re: I am worried about Bun

#105
post #79
post #72

The author closes by enumerating some of the things they like about Bun which are not included in pnpm. The list is basically: native TS support, a vite-style bundler and a vitest/jest style test runner. Other than a bundler, Node already has all of these. Different test runner syntax maybe but otherwise TS "just works" out of the box and their built in test runner is totally capable. Not sure I see the need for such…

When did Node add native TypeScript? Can you run "node main.ts" directly without any dependencies?

v22.18 promoted type stripping from experimental

Re: I am worried about Bun

#106
post #91

Earlier quoted context omitted.

January of last year. Yes. https://nodejs.org/en/blog/release/v23.6.0

That is type stripping and is incompatible with syntax that requires transpilation, so it is not native TypeScript support.

Node v22.7.0 added support for TypeScript syntax that requires transformation:

`node --experimental-transform-types example.ts`

As for whether this matches your definition of "native support" or not...

Source: https://nodejs.org/en/blog/release/v22.7.0

Re: I am worried about Bun

#107

Regardless of Anthropic/ClaudeCode, PerryTS[1] looks like a very promising competitor to Bun. [1]: https://github.com/PerryTS/perry

Looks like AI slop https://github.com/PerryTS/perry/issues/139

> Good question, and you're basically right — let me show the smoking gun.

:vomit:

Re: I am worried about Bun

#109

I disagree with the overall premise: Before the acquisition, Bun had to figure out how to monetize at some point. Now, even though their parent company does some shitty practices with their other software (claude code), it's a stretch to assume this will also translate into making Bun worse: Being worried makes sense but I remain optimistic about Bun. Especially given the context of both of these different context: C…

It's interesting how quickly people buy the "abuse" line of thinking. We understood (and knew for a long time) that the large AI labs are not monetarily profiting from subscription users that make heavy use of their subscription. That is independent of which agent/harness is used. The fair/real price for profitable use is the pay per use token pricing.

These labs play the game of trying to kill competition in the harness game (because third party harnesses risk commoditizing the underlying LLMs once they are all good enough), while playing a game of chicken with each other how long they can burn money that way before they have to give up.

At some point they have to price their product fairly, and the only hope they have is to have killed all competition by then, which is of course a game that they seem to be loosing. Useful models are getting smaller and cheaper to run every year and it has hit a threshold at which we will see continued development of third party harnesses even without the userbase of subscription users.

Basically the prime bet that they made (that one needs extremely expensive hardware to have useful AI) has already failed. The secondary bet that they can lock users into their ecosystem (which requires them to subsidize their harness via unprofitable subscriptions burning their capital) and be able to monetize that later will also fail. They will have to compete on merit alone, and that is much less profitable.

Re: I am worried about Bun

#110
post #91

Earlier quoted context omitted.

January of last year. Yes. https://nodejs.org/en/blog/release/v23.6.0

That is type stripping and is incompatible with syntax that requires transpilation, so it is not native TypeScript support.

Modern Typescript does not need runtime features.
Post reply on HN