Treebard v. 0.0.0 revisited
Feb 15, 2023 1:15:04 GMT -8
Post by Uncle Buddy on Feb 15, 2023 1:15:04 GMT -8
I just posted a new video in the Treebard Philosophy section:
odysee.com/@treebardgenealogysoftware:1/treebard_philosophy_003:3
I played around with the framework Pynecone as I said I'd do in the video. What this app does is to create a web app written in Javascript in the React framework with the backend, a built-in SQLite database, hooked to the HTML/CSS front-end by NodeJS... and all you do is write Python.
Yeah, you don't have to know anything about ReactJS or NodeJS or Javascript...
Unless something doesn't work. Which means unless everything works perfectly all the time, you'll have to learn ReactJS, NodeJS and/or JavaScript to fix it.
Or something. Anyway, I'm over it. It's the same story with all frameworks, in my vastly uneducated opinion: by the time you learn a framework and all its dependencies, you could have gotten a lot of code written in Python, SQLite and Tkinter. Of course this inquiry had nothing to do with Treebard GPS, it's about looking for something other than Electron for writing Treebard v. 1.0.0. There's no reason why a real programmer couldn't use whatever framework they wanted, but I don't have time to learn all these dependencies.
Treebard GPS is built on the no dependencies principle, because it's for novice programmers. It's a demonstration of the fact that a novice programmer can write his own genealogy software. If I can do it, you can do it better. It ain't easy, but it's possible. As soon as you start working on a project that links a whole bunch of dependencies into it, you'd better already be a programmer or forget it.
Also, as mentioned in the video, Python 3.11 is way faster than its predecessors. So what is the problem anyway? Just use Python. If someone wants hundreds of thousands of people in their family tree and wants their app to run fast, well let them write their own app. Treebard GPS is for regular folks who do genealogy and want to have fun doing it.
If someone wants to write an app that works in Dart/Flutter there's a framework called Flet for doing that in Python too so you don't have to learn Dart. So what? These frameworks are for people who know how to solve complex problems with multiple dependencies. Treebard GPS is for regular folks who want to learn just enough programming to do one thing. Regular folks hate dependencies.
I'm glad the experiment with Pynecone failed right out of the gate, because it saved me a lot of time. It could have just as easily worked for a week and then smacked up against a brick wall, and that would have wasted a week. Back to work tomorrow, this sort of thing always renews my love for the simple, out-of-the-box solution that is Python-SQLite-Tkinter.
www.youtube.com/watch?v=VVCUUaYqKW8
www.youtube.com/watch?v=k7n2xnOiWI8
odysee.com/@treebardgenealogysoftware:1/treebard_philosophy_003:3
I played around with the framework Pynecone as I said I'd do in the video. What this app does is to create a web app written in Javascript in the React framework with the backend, a built-in SQLite database, hooked to the HTML/CSS front-end by NodeJS... and all you do is write Python.
Yeah, you don't have to know anything about ReactJS or NodeJS or Javascript...
Unless something doesn't work. Which means unless everything works perfectly all the time, you'll have to learn ReactJS, NodeJS and/or JavaScript to fix it.
Or something. Anyway, I'm over it. It's the same story with all frameworks, in my vastly uneducated opinion: by the time you learn a framework and all its dependencies, you could have gotten a lot of code written in Python, SQLite and Tkinter. Of course this inquiry had nothing to do with Treebard GPS, it's about looking for something other than Electron for writing Treebard v. 1.0.0. There's no reason why a real programmer couldn't use whatever framework they wanted, but I don't have time to learn all these dependencies.
Treebard GPS is built on the no dependencies principle, because it's for novice programmers. It's a demonstration of the fact that a novice programmer can write his own genealogy software. If I can do it, you can do it better. It ain't easy, but it's possible. As soon as you start working on a project that links a whole bunch of dependencies into it, you'd better already be a programmer or forget it.
Also, as mentioned in the video, Python 3.11 is way faster than its predecessors. So what is the problem anyway? Just use Python. If someone wants hundreds of thousands of people in their family tree and wants their app to run fast, well let them write their own app. Treebard GPS is for regular folks who do genealogy and want to have fun doing it.
If someone wants to write an app that works in Dart/Flutter there's a framework called Flet for doing that in Python too so you don't have to learn Dart. So what? These frameworks are for people who know how to solve complex problems with multiple dependencies. Treebard GPS is for regular folks who want to learn just enough programming to do one thing. Regular folks hate dependencies.
I'm glad the experiment with Pynecone failed right out of the gate, because it saved me a lot of time. It could have just as easily worked for a week and then smacked up against a brick wall, and that would have wasted a week. Back to work tomorrow, this sort of thing always renews my love for the simple, out-of-the-box solution that is Python-SQLite-Tkinter.
www.youtube.com/watch?v=VVCUUaYqKW8
www.youtube.com/watch?v=k7n2xnOiWI8