Live data from Hacker News

RawJS is a better way to call document.createElement()

squaresapp.org

11–20 of 135 posts

Re: RawJS is a better way to call document.createElement()

#13

Big 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.

So it implements core SPA functionality?

Re: RawJS is a better way to call document.createElement()

#17

Big 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.

The modal when showing a single colour also suffers from backdrop stacking issues, which the back button navigation doesn't undo.

I guess rendering the UI as a function of state still has its merits.

Re: RawJS is a better way to call document.createElement()

#18

Big 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.

When you click links it changes the URL, so the back button takes you to the previous URL.

I absolutely hate when pages hijack the back button, but this ain’t it.

Re: RawJS is a better way to call document.createElement()

#20
post #9

You never _needed_ React in the first place.

exactly, unless you like exchanging time for food and shelter via rendering anything in the browser

It just strayed so far. Everything has gained so much complexity.
Post reply on HN