I don't understand why people like Tauri - the fact it uses the system web browser completely destroys the main advantage of Electron: that you can test it locally and be absolutely sure that it will render like that on any other system since the browser is shipped with it.
Tauri binding for Python through Pyo3
31–40 of 61 posts
Re: Tauri binding for Python through Pyo3
#32I don't understand why people like Tauri - the fact it uses the system web browser completely destroys the main advantage of Electron: that you can test it locally and be absolutely sure that it will render like that on any other system since the browser is shipped with it.
For a lot of people the main advantage of electron was just being able to use the webdev stack for a desktop app. Tauri makes it less portable but is less bloated. Different tradeofs I guess. Also: I think it’s kinda funny that Tauri is basically a very straightforward of example of trading developer comfort for benefit of the user, and you can’t imagine people using it.
Re: Tauri binding for Python through Pyo3
#33I don't understand why people like Tauri - the fact it uses the system web browser completely destroys the main advantage of Electron: that you can test it locally and be absolutely sure that it will render like that on any other system since the browser is shipped with it.
For a lot of people the main advantage of electron was just being able to use the webdev stack for a desktop app. Tauri makes it less portable but is less bloated. Different tradeofs I guess. Also: I think it’s kinda funny that Tauri is basically a very straightforward of example of trading developer comfort for benefit of the user, and you can’t imagine people using it.
Re: Tauri binding for Python through Pyo3
#34Python, along with C++ enjoys the benefits of Qt. You can build great stuff with cross-platform Qt. And it won't be webview(Electron / Tauri) based. What would be the benefits of this? I can't think of any yet.
Re: Tauri binding for Python through Pyo3
#35Earlier quoted context omitted.
For a lot of people the main advantage of electron was just being able to use the webdev stack for a desktop app. Tauri makes it less portable but is less bloated. Different tradeofs I guess. Also: I think it’s kinda funny that Tauri is basically a very straightforward of example of trading developer comfort for benefit of the user, and you can’t imagine people using it.
I have never seen a Tauri app that was significantly less bloated than Electron. Can you share any?
Re: Tauri binding for Python through Pyo3
#36Nice. It might be worth copying some of the introductory text from the Tauri package explaining what this does. Otherwise a person to lands on the readme gets a lot of technical detail about how it is built without any idea what it actually does.
Re: Tauri binding for Python through Pyo3
#37Since Tauri is just a thin wrapper over the system webview, what's the point of having a wrapper over a wrapper? I don't think the Python ecosystem was lacking in browser wrappers up till now.
Re: Tauri binding for Python through Pyo3
#38I don't understand why people like Tauri - the fact it uses the system web browser completely destroys the main advantage of Electron: that you can test it locally and be absolutely sure that it will render like that on any other system since the browser is shipped with it.
Re: Tauri binding for Python through Pyo3
#39Since Tauri is just a thin wrapper over the system webview, what's the point of having a wrapper over a wrapper? I don't think the Python ecosystem was lacking in browser wrappers up till now.
Re: Tauri binding for Python through Pyo3
#40Since Tauri is just a thin wrapper over the system webview, what's the point of having a wrapper over a wrapper? I don't think the Python ecosystem was lacking in browser wrappers up till now.
This isn't true. It's a thing wrapper over various things, including that.
Even if it were true - so what? There are probably 30 nested wrappers you could name even if you started at WebView as the outermost wrapper.