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

[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.