Python, 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.
Avoiding Qt licensing
Tauri binding for Python through Pyo3
41–50 of 61 posts
Re: Tauri binding for Python through Pyo3
#42Nice. 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.
Going further, what can I build using it? Basically, can I use Python on a Tauri project or can I use Tauri on a Python project?
Re: Tauri binding for Python through Pyo3
#43Python, 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.
Avoiding Qt licensing
Quite a few options there. Never really a problem.
Re: Tauri binding for Python through Pyo3
#44Nice. 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.
Going further, what can I build using it? Basically, can I use Python on a Tauri project or can I use Tauri on a Python project?
Tauri in Python project
Re: Tauri binding for Python through Pyo3
#45Earlier 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.
It's not for the benefit of the user when you get dozens of issues in Github because webkit-gtk or WebView2 changed something.
If you stick to good old HTML5 with CSS3, without cutting edge Blink-only features, you should be safe.
Re: Tauri binding for Python through Pyo3
#46Python, 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.
I worked on a team the switched v2 of our product from Python + QT to Tauri specifically to get away from QT. If you have any kind of specific design requirements, QT is pain. The ability to use the frontend web stack is a huge win especially for a team that already has frontend developers.
Rust was a nice bonus.
Re: Tauri binding for Python through Pyo3
#47Since 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.
Tauri also has their own experimental Servo engine: https://v2.tauri.app/blog/tauri-verso-integration/ So it's not necessarily a wrapper over system webview.
Verso just got archived :(
As the project progressed, multiple significant revisions to Servo were released, and the Verso browser was unable to keep pace with these updates due to limited manpower and funding. Therefore, we will be archiving the repository for now and look forward to a future opportunity to revitalize the project and continue contributing to the Servo ecosystem. [0]
Re: Tauri binding for Python through Pyo3
#48Earlier quoted context omitted.
Rust and Python have very compatible ideas on a lot of topics. For example both think that a developer writing normal code should not have to worry about null pointers or be able to cause a use-after-free. It's just that Python achieves that with runtime costs and Rust with compile-time costs and a complex type system. So developers of one liking the other makes a lot of sense to me. And pyo3 is an extremely convinie…
> For example both think that a developer writing normal code should not have to worry about null pointers or be able to cause a use-after-free Like 99% of all languages currently in use. These things have long been solved way before Rust even existed. Rust has only filled the small niche of cases where you can't or don't want to use automatic garbage collection. > complex type system Python's type system is orders o…
> Like 99% of all languages currently in use.
That's true about memory, but nearly all mainstream programming languages have problems with null pointers: Java, C#, Go, etc.
Re: Tauri binding for Python through Pyo3
#49Earlier quoted context omitted.
> For example both think that a developer writing normal code should not have to worry about null pointers or be able to cause a use-after-free Like 99% of all languages currently in use. These things have long been solved way before Rust even existed. Rust has only filled the small niche of cases where you can't or don't want to use automatic garbage collection. > complex type system Python's type system is orders o…
> Like 99% of all languages currently in use. That's true about memory, but nearly all mainstream programming languages have problems with null pointers: Java, C#, Go, etc.
This is mostly solved in C# - https://learn.microsoft.com/en-us/dotnet/csharp/nullable-ref...
Re: Tauri binding for Python through Pyo3
#50Python, 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.
I worked on a team the switched v2 of our product from Python + QT to Tauri specifically to get away from QT. If you have any kind of specific design requirements, QT is pain. The ability to use the frontend web stack is a huge win especially for a team that already has frontend developers. Rust was a nice bonus.
Doesn't qt also offers a webview solution?