Interesting... though unsure about potential pitfalls or costs in the future. I tend to be extra leery if I don't see clear pricing, including anything related to distribution costs/fees from something that isn't open source.
Not against commercial efforts at all, and this definitely seems cool, just need more on licensing costs and plans for monetization before I would look deeper.
Just saw this on HN, and figured I'd share here. Definitely interesting, with a pretty clean take. Similar to other frameworks, not sure how well a more unified state (like redux) might work with it.
Not completely related to vrite.io, but definitely cool to see the relative evolution of blog software at this point. I do hope we see an evolution of more blog authoring software for at least article management, normalizing or at least configuring what front-matter is needed and blog article structure.
I know MS had an interresting blog editor at one point, that interfaced with a particular server api(s)... but would be nice for something similar that supported a markdown/html output for static generation. Maybe pushing/publishing through github.
Been playing with Deno+Lume and publishing static blog from Github to Cloudflare Pages. Crazy fast delivery https://tracker1.dev/ Need to figure out how I want to add/set article imagery as well as a couple other bits. Mostly experimenting.
Definitely more advanced than the block based nested gantt chart system I build around later 2000 that had to support NN4.0-6.x and IE4-5 at the time. It's like flashbacks of the v4 browser wars... I'm traumatized, I can admit it. Anyone that complains about how hard JS/Browser dev is today doesn't understand the pain... get off my lawn!
Kind of wish the readme had some kind of use case or example... I'm not sure when/why I would want or use this. And does "across browsers" mean browser windows/tabs in a single browser application or across browser applications. Does document refer to the DOM tree, or some external reference?
Not sure if this is cloned/duplicate content, but the sample code formatting is completely borked, whitespace is missing. Beyond this, the API itself isn't really detailed well and there is missing context for supported browsers [1]. Which does indeed seem to be well supported. Links to the MozDev API docs might help as well. [2][3] 1. https://caniuse.com/payment-request 2. https://developer.mozilla.org/en-US/docs/Web/API/PaymentRequest 3. https://developer.mozilla.org/en-US/docs/Web/API/PaymentResponseI tend to call it delay... const delay = (ms) => new Promise(r => setTimeout(r, ms)); ... await delay(1000); // wait a second