7 Comments

It would be great if you share more details about the challenges you faced on going from React to vanilla JS

Expand full comment

>Almost nobody uses Vanilla JS nowadays to build web app

Do you have any reliable source for this claim?

Expand full comment
author

Look at the jobs. How many of them require Vanilla Browser API vs React.

Expand full comment
Comment deleted
Expand full comment
author

I agree. The state of the Web is still insane to me. The reliance on sloppy abstractions increases team sizes exponentially and reduces the quality of the end product.

In 2023 people expect the websites to be slow, that's the norm now.

Expand full comment

Go to tech companies. See what they use. See job postings. See startups and their stacks. See blog posts from developers. See new FOSS products coming out which have a JS web front-end how they're written. See what tutorials show in all developer websites regarding building front-ends. Such claims, even if Alex had said "nobody", mean "most", or "the mainstream fashion is". Doesn't mean there isn't some company in Utah, or some guy in France, whose web apps are written in vanilla JS.

Expand full comment

Sure, you might be correct, but I just think we as a developer are very much in a bubble. There are so many legacy applications built before React was popular, so there are still so many applications being maintained.

Claiming nobody uses Vanilla JS is just enforcing that narrative again without any data.

Also, looking at jobs doesn't say much. Those are green field projects usually.

Expand full comment

Yes, but there are green field projects that are requested to be that way (Knockout, Angular, React, etc) for a decade now. At which point there are already a majority of old projects from those years done in non-vanilla JS.

Besides it's green-field projects that shape the future. Else COBOL is still used a lot, but it doesn't mean those maintanance mode projects means it matters a lot for programmers today.

Expand full comment