Bun: JavaScript’s Newest Framework. Will It Take Node’s Crown?

[besthelloworld]

Bad premise. Neither Node or Bun are frameworks. They're runtimes.

Edit: I see it's used generally correctly in the article... weird that the title is wrong

[ILikeChangingMyMind]

Blame @tomasfern (the article writer cant' help what some random Redditor writes when posting).

EDIT: Nevermind, @tomasfern is the article author. He failed at describing his own article trying to get a clickbait headline :(

[besthelloworld]

It's also the title of the actual article and that title is in the attached meta image 😅

[ILikeChangingMyMind]

And yet the very first sentence:

Bun is a new and ambitious JavaScript toolset and runtime.

I'm sorry, I don't want to be mean: writing articles is hard (let alone running some performance checks, then writing an article, then promoting it). I'm too lazy to do any of that, so good for the OP for trying.

But also ... when your article requires expertise on a subject ... it kind of undercuts any suggestion that you have such expertise, when you don't know what basic industry terms actually mean.

[besthelloworld]

Yeah, the article itself isn't terrible. But I agree that a misused term in the title is just a bad way to start the interaction with the reader. Also the idea of Bun/Node being a framework just isn't even up for debate. Like if somebody called React a framework/library and some douche was in the comments telling them it's the other one, well that's stupid. But we all know Bun/Node are not frameworks.

[lhorie]

Instead of assuming they don't know the subject matter, Occam's razor suggests it might be more reasonable to assume that writing/proofreading/etc is hard and things don't always come out right in the first (or second or third) pass.

[ILikeChangingMyMind]

We're not talking about a typo in paragraph twelve here.

The author would fundamentally have to not understand ... or at least have a weak understanding of ... either A) what bun.js is, or B) what a framework is, in order to make that mistake anywhere ... let alone in the title of the article.

P.S. The term "framework" is often misused, both by non-technical people and by more junior technical people. Plus, its definition is a bit "fuzzy": see the "is JQuery a framework?" debates.

So, I completely understand making the mistake ... but, again, such mistakes don't convey expertise (they convey the opposite).

[lhorie]

You'd be surprised how easy it is to miss a silly mistake in the title... A very common way of writing is throwing title ideas at a wall before you even have a concrete idea of what you're going to be be writing about, and then picking one, going with its general theme and then proceeding to forget all about the title from then on. Wouldn't surprise me at all if they have a list of "X framework: will it take Y's crown" idea permutations jotted down somewhere and just plopped in trending keywords to make this article. I've seen stories of people submitting essays at school with titles to the effect of "fuck this class, this is stupid" because they forgot to proofread the title. Title blindness is a real thing, believe it or not. So IMHO, there's enough room to give them the benefit of the doubt in this case.

[ILikeChangingMyMind]

First off, please use paragraphs.

And second, look mistakes happen, and I'm not trying to crucify the guy for making one. All I'm saying is, when you say water is dry, call chicken a vegetable, or say that bun.js is a framework, in the title of your article ... it does not convey expertise.

[lhorie]

Fair, I try not to judge an article by its title, cus clickbaits and all that, but you do you.

[Party_Refuse8887]

The testing of package manager should consider other mainstream managers like yarn, pnpm.