Medium
For further actions, you may consider blocking this person and/or reporting abuse
Read next
What Can In-Browser JavaScript Do and What Are Its Limitations?
Md. Maruf Sarker -
🧠 Free Code Challenges, UX Trends Shaping 2025 & Duolingo's Retention Playbook
Adam Marsden -
Get Pending Transactions in Binance Smart Chain Mempool Using Ether.js and QuickNode
Quoc Huynh Website -
Schedule Events in EventBridge with Lambda
Ritul Singh -
Top comments (3)
Yet another post that doesn't see the current state of affairs is the same as the jQuery world in 2008.
There are now 60+ alternatives to Lit/Stencil
Only 2 or maybe 3 of these Vanilla JS Sucks; Make Web Components Better tools will survive.
If you bet on the wrong horse; you will end up with a stale Git Repo. And you have to "refactor" your code like the infamous Angular 1 to Angular 2 "upgrade".
Hi @dannyengelman, Thanks for your response. Your linked article is interesting and I agree with your concerns. I have had similar thoughts in the past.
So, what do you suggest? On what should we "bet" when developing more complex Web Components? The bare way without any external library?
In essence it comes down to taking 100% control of the code you use.
Note: I am NOT saying build 100% of your code yourself.
Learn the gory details of the BaseClass you use.
After I took jQuery apart; I copied the code native browsers couldn't do yet, and ditched jQuery itself.
Add a BaseClass in between the BaseClass of your choice and your own main code.
At first it will be empty, during time you can implement functionality you want (see above) or disable code that is surpassed by now native technologies.