Why is that a problem? You get a commercial license for PyQt and are good to go(?)
> I love Python, but it has stagnated hard in the last few years. The 2 to 3 transition really hurt the Python ecosystem [...]
I disagree. I think the ecosystem is more vibrant than ever.
> Furthermore, packaging for different platforms is still a problem in 2018.
That is exactly what this project is trying to help with.
Beside the ML/AI sub-community, I am having a hard time finding GUI innovation in the Python ecosystem. Perhaps, you could show me an option that doesn't suck? I've tried Kivy, PyQt, PySide, Eel, gooey, etc... I am not a JS dev and had an electron/react app up and running that I easily ported to my Android phone in under an hour.
[1]: https://fman.io
On one hand you have the complex licensing thing (PyQt) where you are limited to desktop of Mac, Win, Linux. On the other you have a skill (JS dev) that is good for literally any screen, on any platform with almost zero complications for commercial apps. It is a no brainer.
If it isn't obvious, I have begun the transition to embrace JS for what it is... I am learning it and it hasn't been too bad. Python will be relegated to ML/AI and glue...
Regarding licensing, you can simply buy the commercial license only when you go public / begin making money. It's not that difficult I think.
But as I said, you are correct in that Electron is easier to use for many people. I'm also the last person to say you should always use PyQt. Just today I recommended someone to use Electron over PyQt. It really depends on the project.
if nuklear.button_label(title="Button"):
print("Button pressed!")