https://bugs.kde.org/show_bug.cgi?id=75324
--- Comment #43 from Ville Ranki <ville.ra...@iki.fi> --- (In reply to Nate Graham from comment #39) > What can we do to make this happen and still provide an adequately > performant and responsive experience? We must make it clear for app developers that they can't assume file i/o is quick and always successful. Any loading and saving should be done it's own thread and the UI must be able to handle it being slow or fail. File i/o must be handled much like network operations. An asynchronous helper library could be implemented to help developers if needed. Maybe also testing tools to simulate congested or unreliable network share. -- You are receiving this mail because: You are watching all bug changes.
