RawJS is a better way to call document.createElement()
squaresapp.org
RawJS is a better way to call document.createElement()
1–10 of 135 posts
Re: RawJS is a better way to call document.createElement()
#2Big 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
Re: RawJS is a better way to call document.createElement()
#3Getting a broken SSL cert accessing this site
Re: RawJS is a better way to call document.createElement()
#4The page needs some code examples. It's just marketing talk, needs to be more oriented to it's audience.
Re: RawJS is a better way to call document.createElement()
#5The polar opposite of htmx. . .
Re: RawJS is a better way to call document.createElement()
#6Feels worse than something like dom-chef
Re: RawJS is a better way to call document.createElement()
#7https://medium.com/@arannadelwar361/embracing-the-power-of-r...
https://dev.to/paulgordon/after-using-rawjs-im-never-touchin...
Both links helped to explain, the landing page is indeed not very good.
Re: RawJS is a better way to call document.createElement()
#8I guess they forked Vapor.js? :)
Re: RawJS is a better way to call document.createElement()
#9You never _needed_ React in the first place.
Re: RawJS is a better way to call document.createElement()
#10Big 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.