Medium
For further actions, you may consider blocking this person and/or reporting abuse
Read next
Custom YouTube Player Gadget with Javascript
Anwar Achilles -
Rust Source Code Reading: The thousands crate
Gabor Szabo -
WebAssembly + JavaScript: Building a Real-Time Image Processing Tool
Vladislav V. -
Finally got some time to play with the new JSONata and Variables support for Step Functions, and I have to say, it is massive improvement. Check out my latest blog post, where I walk through a simple example of how easy it is to handle pagination now
Ian -
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.