Most active commenters
  • xandrius(4)

←back to thread

Nullboard: Kanban board in a single HTML file

(github.com)
578 points smusamashah | 12 comments | 19 Dec 24 14:29 UTC | HN request time: 0.858s | source | bottom
Show context
egeozcan ◴[19 Dec 24 17:12 UTC] No.42463511[source]▶
This is very cool. BTW, when developing single HTML file apps, instead of localStorage, one can use the HTML as the source of truth, so the user can just save/save-as to persist. I had mentioned my quick and dirty attempt at an image gallery that is a self-contained html file and some really liked the concept, if not the "app" itself: https://news.ycombinator.com/item?id=41877482
replies(6): >>42463631 #>>42464347 #>>42467577 #>>42471918 #>>42476577 #>>42477123 #
xandrius ◴[19 Dec 24 17:23 UTC] No.42463631[source]▶
Wait, so every time I make a change I need to remember to save or it's all lost? Or am I missing something?
replies(7): >>42463754 #>>42463869 #>>42464221 #>>42464493 #>>42464749 #>>42465571 #>>42469902 #
1. breakfastduck ◴[19 Dec 24 18:16 UTC] No.42464221[source]▶
My god this comment made me feel old.

God forbid you have to remember to save your work!

replies(4): >>42464339 #>>42464506 #>>42466436 #>>42474915 #
2. billiam ◴[19 Dec 24 18:28 UTC] No.42464339[source]▶
The mental model my kids have for work is that typing or even thinking is itself a finished product. For my generation that idea of a conscious action of saving your work on a computer made me think more about what I was doing and how I was doing it. But I am an old.
replies(2): >>42464773 #>>42481399 #
3. mock-possum ◴[19 Dec 24 18:46 UTC] No.42464506[source]▶
I mean - yeah, honestly, god forbid. Requiring manual saves with limited change history (or none at all) was the bad old days. That was bad UI/UX, literally everybody had a “oops I forgot to save” and a “oops I saved and I didn’t mean to” horror story. Things are better now.
replies(1): >>42464784 #
4. endofreach ◴[19 Dec 24 19:17 UTC] No.42464773[source]▶
I understand the overall contrast you're sketching here. But can you elaborate on

> typing or even thinking is itself a finished product

Any specific examples where you notice the difference?

5. jjeaff ◴[19 Dec 24 19:18 UTC] No.42464784[source]▶
I wouldn't say it was totally awful. At least, prior to having an Undo option or perhaps an undo but that can only go back 3 steps, saving as before making any large changes was a pretty common workflow. I might end up with 50 versions of a document numbered incrementally by the time I was finished. that is still a necessary workflow for certain types of documents. I don't necessarily want everything saved automatically all the time.
replies(1): >>42466448 #
6. xandrius ◴[19 Dec 24 22:33 UTC] No.42466436[source]▶
Do you really long for that?

It's been over 20 year with auto-save being pretty common, one has to adapt to the modern times, especially when it makes things better.

I don't have to "remember to save my work" when I write on my notepad, why should it be different on a computer?

replies(1): >>42469994 #
7. xandrius ◴[19 Dec 24 22:34 UTC] No.42466448{3}[source]▶
I love my paper notebook to save everything automatically, I don't long for it to all disappear if I forget to press a button and give it a name.
8. account42 ◴[20 Dec 24 10:50 UTC] No.42469994[source]▶
> Do you really long for that?

Yes, absoultely. Saving data you don't want saved and overwriting data you want to retain are just as bad as not saving data you want to keep.

Keeping a scratch file to restore from unexpected applications exits (crash, power loss, etc.) is fine but beyond that I expect to be in control of when and where things are saved.

> one has to adapt to the modern times

I expect my computers to adapt to my requirements, not the other way around.

> especially when it makes things better.

Modern rarely equals better.

replies(2): >>42470961 #>>42481327 #
9. xandrius ◴[20 Dec 24 13:39 UTC] No.42470961{3}[source]▶
Wait until you discover pen and paper.
10. HeyLaughingBoy ◴[20 Dec 24 20:53 UTC] No.42474915[source]▶
At my first job, one of my responsibilities was to write the product manuals. My boss would set a timer next to me and instruct me to ctrl-S every time it went off.

Corrective action from having lost work too many times :-)

11. nuancebydefault ◴[21 Dec 24 18:39 UTC] No.42481327{3}[source]▶
Neither save strategy is 'the better one'. Next step would be that git auto-commits...
12. nuancebydefault ◴[21 Dec 24 18:48 UTC] No.42481399[source]▶
If you go back in time, there were editors that by default would save the previous version of a file to .bak, each time you saved the current status. The fear of accidental saving or editing and hence overwriting old good stuff was higher than accidentally loosing new good stuff. There was less protection of system files, config files etc, so chances were you would brick apps or even the OS. Things got more forgiving since.