Is there now a generation of users who never worked with files?
blog.hyperknot.com
Is there now a generation of users who never worked with files?
1–10 of 50 posts
Re: Is there now a generation of users who never worked with files?
#2Mightn't it be better to actually just autosave?
Re: Is there now a generation of users who never worked with files?
#3Mightn't it be better to actually just autosave?
Where?
Re: Is there now a generation of users who never worked with files?
#4Re: Is there now a generation of users who never worked with files?
#5I work with files every day, and I'm not sure I would have realised I'd needed to save manually with the original MapHub UI either. A web-based interface that looks like that, I expect it to be transparent. If it'd had three icons (the classic blank page, open folder and floppy disk) in the top left, then I'd assume it would need manual saving. (I'm not saying that's what you need to do, just analysing my own intuitions)
Re: Is there now a generation of users who never worked with files?
#6Mightn't it be better to actually just autosave?
Yes, but the author (probably) implemented their save system where the client sends the entirety of the save data to the backend; meaning a lot of redundant information is sent.
Ideally, the client should only push changes to the backend and thus avoid the issue of sending redundant data entirely. This means re-implementing their saving solution, which is probably not trivial to do as you also have to deal with the issue of migrating existing save data to your new solution (which might mean some significant upfront costs).
The author didn't address this directly, but what they could do is just implement the autosave anyways and just deal with sending redundant data. But... this probably is quite expensive as the cost incurred per user is proportional to the size of the save data multiplied by the frequency of auto save.
Re: Is there now a generation of users who never worked with files?
#7Nothing to do with generations.
I simply expect a webapp to autosave. Period.
Re: Is there now a generation of users who never worked with files?
#8I don't understand why the author believes auto save would be so difficult to implement.
Just automatically click the save button for the user on a one minute timer. Done.
setInterval(() => {
document.getElementById("save-button")?.click();
}, 60000);Re: Is there now a generation of users who never worked with files?
#9I doubt it. Most school software still sends files over e-mail that you have to save as attachments, or upload your own document files. So they still learn that early, regardless of if they use it later in life.
Re: Is there now a generation of users who never worked with files?
#10I don't understand why the author believes auto save would be so difficult to implement. Just automatically click the save button for the user on a one minute timer. Done. setInterval(() => { document.getElementById("save-button")?.click(); }, 60000);
Hi, author here. I think it's not a good idea to auto save just at random intervals. I certainly don't want my any of my apps to auto save without me telling it to do so. Maybe I'm old fashioned in this regards.
Update, answered in detail here: https://news.ycombinator.com/item?id=42016231