> pywebview is a lightweight cross-platform wrapper around a webview component that allows to display HTML content in its own native GUI window. You may think of as Electron for Python (minus huge executable sizes). It gives you power of web technologies in your desktop application, hiding the fact that GUI is browser based.
It's still as bad as electron and calling it native is a stretch.
I haven't looked at pywebview at all, and my experience with electron is also not very good. Apart from the 'native' misnomer, assuming the general concept of such a 'website-as-app' is an acceptable tradeoff in a certain situation, what exactly is bad with pywebview?
It uses a platform-native renderer instead of embedding most of Chromium like Electron does, so it's not the same thing. I'd imagine it's better in some ways (executable size) and worse in others (dealing with 4 different renderers).
Nery nice, although I'm yet to encounter a situation where I was using NetworkX for anything small enough to be rendered in d3, especially interactively (assuming SVG).
What do people do with it that has such small graphs?
