I like the idea a lot, any effort to spend more time with loved ones and off the phone is a noble pursuit. I think one thing that could add to this and help to habitualize it - would be ongoing statistics.
Something like..
- 3.8 days dedicated since you began in March
- 4.5 hours dedicated so far this week
- perhaps even being able to set up weekly goals could work
You are already using localstorage, so expanding on that sticks to your no account/analytics ethos.
It really bothers me that people refer to open weight models as being open source. They fundamentally aren't and are more akin to freeware than anything else.
As a (unfortunately) wordpress dev this seems to solve my single biggest painpoint with WP. Which isn't plugin security, but the overall plugin architecture.
WP treats plugins as content, literally in the same top level `wp-content` directory as uploaded images. This makes CI/CD among other things, a nightmare. But EmDash plugins are just TS modules, which has got to make things easier even if plugin configuration does end up in the db somewhere.
Your point of view assumes the best of people, which is naive. It may not force you to skip understanding, however it makes it much easier to than ever before.
People tend to take the path of least resistance, maybe not everyone, maybe not right away, but if you create opportunities to write poor code then people will take them - more than ever it becomes important to have strong CI, review and testing practices.
Edit: okay, maybe I am feeling a little pessimistic this morning :)
IMO not significantly. Prior to AI the bulk were tutorial based to-do apps or simple crud things anyway, its still easy to tell the difference between those and something more complex (where AI is less useful - or at least requires more skill to use successfully).
But I don't think the projects themselves really mattered all that much anyway - its the conversations you can have about them. Understanding the driving factors, whether it was solving a problem they have or just working on something they are passionate about, the challenges they overcame in the development process and the considerations/decisions they made along the way.
I did provide a warning of my nonsense. As you say though 10-30kb per image, in a 350+ page text book is already likely 7mb+ (assuming 1+ images pp). And that is absolute best case if the original images and optimization are working together. I would guess without any optimization for digital publication you could be starting from 100-200mb easily.
Talking out of my ass, but since epubs often target mobile devices (kindle, kobo, etc - with limited storage) - publishers probably find that their books do better if they tend to be smaller in size. And images take up far more diskspace than text does in a digital copy.
Then when a user needs to delete books from a device they will start with the largest files. The longer the book is on the device the more likely they are to engage with it, etc.
1. Art is art because it draws meaning from human existence - AI can't and can never exhibit this. Furthermore, pumping out thousands of "creations" a minute will never compare to a single work from a human.
2. People are dumb and will fawn over just about anything, the origin of a piece of art created today is less relevant than ever.
Something like..
- 3.8 days dedicated since you began in March
- 4.5 hours dedicated so far this week
- perhaps even being able to set up weekly goals could work
You are already using localstorage, so expanding on that sticks to your no account/analytics ethos.