[doubletgl]

Yes, and it's nonsense.

"I needed something to convert markdown to html", "I like the component mental model", "I wanted to use Node libraries for date formatting etc.", "Next has a great developer experience"

None of these justify using React. It all boils down to "I'm doing it because I can and I'm familiar with those tools".

[hazz99]

> None of these justify using React. It all boils down to "I'm doing it because I can and I'm familiar with those tools".

"I'm using x technology because I'm familiar with it" is exactly what most people should be doing. Many people try to create production sites with tooling they're not familiar with, or take too long learning something new.

Why do none of these justify using React? They probably care about different things than you do.

[pxtail]

> "I'm using x technology because I'm familiar with it" is exactly what most people should be doing.

Not necessarily, there are multiple tools in the world and not without reason - almost all of them were created with specific purpose. One can be very familiar and skilled with using hammer but it doesn't mean that it will be efficient to cut a slice of bread with it.

For software tools makers it is very tempting to try to make it versatile enough to be able to use it for every possible case, however this is not possible and never will be without sacrifices - and most frequently speed, clarity and ease of use is sacrificed first - there are multiple examples of this: jira, gitlab, facebook, clickup. Complexity, bloat and cognitive load is growing, users are starting to have difficulties to grasp all options and possibilities - and boom suddenly from most loved to most hated.

[sgzfx]

You're right in that it boils down to that, but that does also inherently justify using React for them.

Why would the author prefer unfamiliar tools in favor of tools they are productive with that produce the same output?