PySimpleGUI VS tauri

Just a heads up: PySimpleGUI 5 isn't open source any more [0], and the official GitHub repo was replaced with a stub [1]. From the blog post, it sounds like the people behind it will probably remove the FOSS version from PyPI soon.

It's possible the community will fork it with a version of PySimpleGUI 4 that's still kicking around, but I haven't seen one yet.

[0] https://news.ycombinator.com/item?id=39369353

[1] https://github.com/PySimpleGUI/PySimpleGUI

Their old CONTRIBUTING file <https://github.com/PySimpleGUI/PySimpleGUI/blob/1fa911cafee6...> said:

> Pull requests are not being accepted for the project. This includes sending code changes via other means than "pull requests". Plainly put, code you send will not be used.

> I don't mean to be ugly. This isn't personal. Heck, I don't know "you",the reader personally. It's not about ego. It's complicated. The result is that it allows me to dedicate my life to this project. It's what's required, for whatever reason, for me to do this. That's the best explanation I have. I love and respect the users of this work.

It's obvious in hindsight that those reasons were a bald-faced lie, and the real reason was exactly that he could legally do this rug pull.

From https://github.com/PySimpleGUI/PySimpleGUI/issues/142

> 2023 is going to be the "Make or Break" year. I ultimately need to determine if the project is going to continue. To date, it's nowhere near sustainable. The income doesn't cover the cost of the project, meaning that it's not only unable to allow me to pay for my cost of living, but I continue to rack up debt, borrowing money, to keep the project functional.

> This isn't new information if you've followed the over 1,200 announcements I've made since Sept 2018. The data is available should you wish to look at the GitHub Sponsorships and do the simple math required to calculate income from Udemy. It would be great for the project to keep going. I'm hopeful, but more than hope's required to keep the project going.

So if you like this project and want to see it around in the future, please support it.

Github sponsors is probably the best place: https://github.com/sponsors/PySimpleGUI

The psutil package makes getting a list of running programs not very difficult. There's an example demo program that polls once a second and displays the top process using CPU time. You could use it as a starting point perhaps.

How does it compare with remi? https://github.com/rawpython/remi

Looking at the examples, for quick UIs, REMI seems simpler. And PySimpleGUI (https://github.com/PySimpleGUI/PySimpleGUI) offers REMI as a backend to deploy on web too (PySimpleGUI is pretty simple to learn).

Random Password Generator (what an orginal name!) or RPG for short is a simple password generator that uses PySimpleGUI GUI framework, in order to have a user-friendly interface and also because i wanted to have fun.

Another approach when the data is easy to graph is to use the Graph Element to create a graph. A Demo Program shows how to make something like this.

Hi, dear Tauri! Long time no see. I published my first post, Developing a Desktop Application via Rust and NextJS. The Tauri Way almost a year ago. Since then, Tauri has become stronger. I'm happy about that! And now, I am very pleased to make a useful contribution to the Tauri community. As a full-stack developer, I frequently face situations where I need to start a DB-based UI project as fast as possible. It's stressful if I need to start the project from 100% scratch. I prefer to keep some boilerplates on hand, which will save me time and nerves and will be the subject of this article.

Hey Thanks!

Just electron & vite. I might actually migrate off electron, Tauri (https://tauri.app/) seems to be getting more stable and it's gotten great reviews.

I think this is the boilerplate I used though https://github.com/cawa-93/vite-electron-builder.

Well the great thing about WebAssembly is that you can port QT or anything else to be at a layer below -- thanks to WebAssembly Interface Types[0] and the Component Model specification that works underneath that.

To over-simplify, the Component Model manages language interop, and WIT constrains the boundaries with interfaces.

IMO the problem here is defining a 90% solution for most window, tab, button, etc management, then building embeddings in QT, Flutter/Skia, and other lower level engines. Getting a good cross-platform way of doing data passing, triggering re-renders, serializing window state is probably the meat of the interesting work.

On top of that, you really need great UX. This is normally where projects fall short -- why should I use this solution instead of something like Tauri[2] which is excellent or Electron?

[0]: https://github.com/WebAssembly/component-model/blob/main/des...

[1]: https://github.com/WebAssembly/component-model/blob/main/des...

[2]: https://tauri.app/

Welcome to the 2nd episode of our series “Building with Tauri”, where we chat with developers who build amazing projects and products using Tauri.

Tauri seemed like the "thing" I should switch to because everybody loves Rust (heh), and because it ships significantly smaller apps.

First of all, I will be using npm as my package manager but feel free to use whatever you prefer. Find more info here.

Today I'm talking about Tauri! Do you know all the various tools that allow you to develop native applications starting from web languages? They often need an intermediate compilation, in the middle of which you end up encountering various problems not always transparent and directly solvable with a language mostly detached from native development. On the other hand, there's still the ease of developing attractive and easily usable interfaces, which are more difficult to develop with low level languages.