RawJS is a better way to call document.createElement()
11–20 of 135 posts
Re: RawJS is a better way to call document.createElement()
#12Re: RawJS is a better way to call document.createElement()
#13Big claims and zero code examples? No I'm not going to go digging in a repo without so much as a top-level overview of the approach
The demo is here. https://rawjssample.pages.dev/ I immediately see that it ~hijacks my back button~ fills my back-stack such that I can't use the back button normally. Doesn't look promising.
Re: RawJS is a better way to call document.createElement()
#14You never _needed_ React in the first place.
Re: RawJS is a better way to call document.createElement()
#15Re: RawJS is a better way to call document.createElement()
#16Re: RawJS is a better way to call document.createElement()
#17Big claims and zero code examples? No I'm not going to go digging in a repo without so much as a top-level overview of the approach
The demo is here. https://rawjssample.pages.dev/ I immediately see that it ~hijacks my back button~ fills my back-stack such that I can't use the back button normally. Doesn't look promising.
I guess rendering the UI as a function of state still has its merits.
Re: RawJS is a better way to call document.createElement()
#18Big claims and zero code examples? No I'm not going to go digging in a repo without so much as a top-level overview of the approach
The demo is here. https://rawjssample.pages.dev/ I immediately see that it ~hijacks my back button~ fills my back-stack such that I can't use the back button normally. Doesn't look promising.
I absolutely hate when pages hijack the back button, but this ain’t it.
Re: RawJS is a better way to call document.createElement()
#19> You have to be disciplined to only use dependencies that are published on jsdelivr (npm install programmers need to clean up their act)
Yeah, no thanks, I'm sticking with my "unclean" ways.