I've seem them once or twice before. There are two reasons to have a progress-bar. One is to know the "rate of progress", and another the, amount of work done so far.
When a progressbar freezes, it could also be because some background process just died, or someone forgot to catch an exception in time, or an async call that doesn't handle a timeout or has a long timeout. Most technical users just use -v or --verbose options to see what's happening, rather than how much has happened as an unquantified bar.
Maybe the solution is to have a sort of speed-dial like that on cars. Backend processes can ping the log-collector or some other globally accessible entity everytime they "do" something useful. That would allow the speed-dial to show the frequency of operations, giving a good idea of whether or not something is happening or not.
There certainly are many file/folder sync software out there - some open, some free, some "commercial" (meaning proprietary), some commercial (you get GPL'd code when you buy them).
Mesh Folders, however, are just one feature on top of Mesh. Mesh is about sync'ing all kinds of data and being able to write apps on top of it with very simple programming interfaces.
Moreover, secure transfers are a part of Mesh - everything is unconditionally HTTPS outright.:-)
I presume nobody can read Atom, RSS, Json, etc. anymore.:-)
I forgot to mention in my last post, the XML is in multiple formats which are widely prevalent and the content - you get to choose your blobs. It's a transparent XML blob for the Mesh storage.
So long as you store it in a format to your liking....
All these lockin arguments are highly irrelevant to the Mesh.
The Mesh storage is all XML feeds over HTTP. Unless "GET http:///" is impossible on anything except Windows, I don't understand why everyone keeps harping on the lockin.
Slashdot Mirror
I've seem them once or twice before. There are two reasons to have a progress-bar. One is to know the "rate of progress", and another the, amount of work done so far. When a progressbar freezes, it could also be because some background process just died, or someone forgot to catch an exception in time, or an async call that doesn't handle a timeout or has a long timeout. Most technical users just use -v or --verbose options to see what's happening, rather than how much has happened as an unquantified bar. Maybe the solution is to have a sort of speed-dial like that on cars. Backend processes can ping the log-collector or some other globally accessible entity everytime they "do" something useful. That would allow the speed-dial to show the frequency of operations, giving a good idea of whether or not something is happening or not.
Saw Nokia's standard and added a meter, and are calling it new! Classic Apple! I'm sure the fanbiOS will fall for this one-meter revolution!
That's what I was thinking too. Employees do do epic shit - this is just belittling (feel free to correct my spelling) their own employees.
There certainly are many file/folder sync software out there - some open, some free, some "commercial" (meaning proprietary), some commercial (you get GPL'd code when you buy them). Mesh Folders, however, are just one feature on top of Mesh. Mesh is about sync'ing all kinds of data and being able to write apps on top of it with very simple programming interfaces. Moreover, secure transfers are a part of Mesh - everything is unconditionally HTTPS outright. :-)
I presume nobody can read Atom, RSS, Json, etc. anymore. :-)
I forgot to mention in my last post, the XML is in multiple formats which are widely prevalent and the content - you get to choose your blobs. It's a transparent XML blob for the Mesh storage.
So long as you store it in a format to your liking....
All these lockin arguments are highly irrelevant to the Mesh. The Mesh storage is all XML feeds over HTTP. Unless "GET http:///" is impossible on anything except Windows, I don't understand why everyone keeps harping on the lockin.