I am surprised this is not the norm, It looks like that this person have a tendency to lean into the extreme (like with his previous blog about chaining). I always feel like every syntactic sugar of any kind are to be treated like any other design/style philosophy. Too much of it is not good. Look at Java that is OOP to the extreme. Any language would quickly became unusable if any one of the features/design philosophy are (ab)used.
this post was submitted on 13 Jul 2026
20 points (100.0% liked)
JavaScript
2753 readers
1 users here now
founded 3 years ago
MODERATORS
Exactly my reaction!
It wasn’t a conscious decision anymore, it was just what modern JavaScript looked like.
I almost stopped reading here. I don't agree that modern JavaScript looks like that. Why would it. Friends don't let friends lean too hard into a single code style pattern. These things are situational ffs.
Also,
Objects carry context
Yes but:
const { email: userEmail } = user;
Example seems contrived, sure, but the feature exists. Context added.
I don't know, to me this just reeks of someone who is still struggling with code style and more focused on the how instead of the why, even though they give the appearance of thinking about the why.
I always treat things like projectStatus and userEmail as a kind of code smell.
If a variable name carries too much context, then I figure out why and how to carry that context in a better way (project.status user.email)
Isn't always doable. But that's why it's a smell, not a rule
This might seem trivial, but it's a sign of mastery.