I had heavily used PySimpleGUI in various work projects, and one day, when I had to run some older piece of code I had not run in a while, I get a notice that PySimpleGUI won't work, because was free, but nobody paid, and so, good luck! So I was piping mad, paid the 3-year or whatever the max license fee was, received a code, and THEN I was able to get my stuff to work, like it used to. LESSON: N E V E R Use code tha…
Given it was older code, were you not able to use an older version of pysimplegui that was freely available?
PySimpleGUI 6
51–60 of 64 posts
Re: PySimpleGUI 6
#52I understand that people have had bad experiences and in general I don't want to pay for software components either. But it's weird how much hate there is against developers sometimes just for even trying to make money from their libraries.
Re: PySimpleGUI 6
#53Today I wanted to build a simple ui that maps time across 3 time zones. After spending some time thinking about using it across my Mac and Linux machines, I just had Claude write an html file. Nice, simple runs everywhere.
Local HTML files with embedded JavaScript are fantastic for mini portable apps. You can even load/save files with some finesse.
Re: PySimpleGUI 6
#54NiceGUI is MIT licensed. Not perfect , but no bizarre shenanigans when it comes to releasing commercial software.
Re: PySimpleGUI 6
#55LOL, I remember this one being a famous traitor to FOSS by starting out as a community project and then closing doors to make money from it. Guess they weren't able to make any money after all. Karma in action.
Or it's just another example of why FOSS fails - people (like you) expect free labor and never want to pay for it. They tried to make it a sustainable project, and it would probably have died even earlier if they didn't. > For the last 5 years, PySimpleGUI offered free software with the hope of sustaining the project with donations. We appreciate the support we received, but the amount has been too small to support t…
> with the hope of sustaining the project with donations.. the amount has been too small to support the project
So shut it down, lock the repo, invite new maintainers indefinitely. It's only non-sustainable for the price the author is asking. It'll still be FOSS even if no longer maintainer by the original author, whether a new maintainer steps in or not.
And if they want to fork it an create a commercial alt, no problem - anyone can!
The problem arises, IMHO, when they develop (accept contributions) or propagate (lock-in) a FOSS project in good-will, then somehow leverage their position as a FOSS maintainer transform it to non-FOSS.
Re: PySimpleGUI 6
#56NiceGUI is MIT licensed. Not perfect , but no bizarre shenanigans when it comes to releasing commercial software.
How has your experience with NiceGUI been like? I was thinking about giving it a try some day but didn't get the chance to do so.
Re: PySimpleGUI 6
#57I had heavily used PySimpleGUI in various work projects, and one day, when I had to run some older piece of code I had not run in a while, I get a notice that PySimpleGUI won't work, because was free, but nobody paid, and so, good luck! So I was piping mad, paid the 3-year or whatever the max license fee was, received a code, and THEN I was able to get my stuff to work, like it used to. LESSON: N E V E R Use code tha…
Re: PySimpleGUI 6
#58Re: PySimpleGUI 6
#59Earlier quoted context omitted.
Is this a new form of gatekeeping? I.e., "too human-friendly to survive in the presence of The Great AI™". If so, where does that lead us?
These libraries are not more human friendly. Humans can write GTK or win32 or QT or Cocoa code just fine. GUI frameworks are very complex and often have very in depth setup code that is required. It requires a huge investment to get an app up and running with a GUI framework, and AI makes setting that up approachable when it was a real challenge before. Have you ever written GUI code using one of the big GUI framewor…
I tried a bunch of Frameworks and some were easier (PSG, Kivi) and others much harder.
Re: PySimpleGUI 6
#60Earlier quoted context omitted.
What do you prefer for lockfiles in the Java world? I’ve been trying to drag a couple of Maven teams into the 2010s after finding that they weren’t.
You don't need them. Maven has deterministic dependency resolution (unless you use version ranges, but don't do that), so you just write your dependencies. (The flipside is you may want to get in the habit of doing something like versions:use-latest-releases as a regular housekeeping task so that you pick up any security updates, but that tends to be less of an issue in Java-land for other reasons)
Even if that worked, I’d also want hashes to avoid file modification, although that’s less of a concern for anything on Maven Central where the releases are immutable.