Kamil Tomšík

Graffiti will always be just a subset of DOM/CSS so you'd need to only use what's supported but otherwise it should work. Currently, it's limited to inline styles only but...

> Never got beyond some hello world examples in a [crazy Nix environment](https://github.com/egasimus/graffiti-tutorial). Wow, that looks really great! > What subset of HTML5 DOM API support is to be expected?...

This is from-scratch HTML/CSS engine so no canvas (yet), but there's WebView (macos-only for now) so you could do that. You might also have a look at [tauri](https://tauri.studio/) - but...

oh, ok then that might be good fit for graffiti, you essentially just need to create `index.html` and one `main.js` file where you create window (like with electron) but it's...

Web browser complexity & overhead mostly comes from: - process isolation (and other security mitigations so you can browse safely) - excessive caching (so your favourite web page loads quickly)...

> > Kosmonaut would implement a small subset of modern web standards for layout, enabling rapid UI development for anyone who knows HTML and CSS. We can even map browser...

Yep, it's impossible to do lazy loading with coroutines but it is possible to do with fibers. Fibers enable true OOP (implementation hiding) and so they are in my opinion...

You can work around this with macro (`impl_xxx!(TypeA, TypeB, ...)`) - that way you're not using trait constraints because you are explicit. But this is something which definitely should be...

we are using this trick in our app module: ``` providers: [ ..., { provide: BIND_QUERY_PARAMS_OPTIONS, useValue: { windowRef: { location: { get search() { return window.location.hash.replace(/[^?]*\??/, ''); }, },...

we are little behind (2-3 versions), so I can't tell if it still works, but it definitely worked for us