6 ms·

Software going out of fashion shouldn't be an issue if you take care to use applications that have open data formats, or can at least export their data to somet

by wvh 10y ago

Software going out of fashion shouldn't be an issue if you take care to use applications that have open data formats, or can at least export their data to something usable by other software. Hardware became a commodity; software is on its way there too thanks to its face-paced nature and devaluation from "applications" to trendy, cheap "apps". But your data will likely always be valuable, so whatever you choose to use, make sure to have continuation plans. There is no vendor lock-in if your data stays yours. Some inconvenience perhaps; the sort of inconvenience that comes with freedom.

TeMPOraL 10y ago
And that is the reason I avoid most cloud-based solutions. I want my data to be in files on my drive, and not just in some database rows on a third-party server. Personally, I store all my notes in plaintext org-mode files in a Dropbox-synced folder.
rrdharan 10y ago
I think it's potentially underestimating the nature of the problem and OP's complaint to simply write off potential switching costs as "inconvenient". For example if I've developed a whole workflow around keyboard shortcuts, APIs, whatever, for manipulating a set of data using an app, and then that app disappears, even if I have the underlying dataset it might take me quite a while to get up to speed with a suitable replacement. All of that might argue against investing heavily in developing expertise with a closed, indie, proprietary, or even an OSS app[1]. Ultimately whenever you invest your time in developing a skillset or workflow you are inherently also obligated to evaluate the future risks involved. [1] Despite it being OSS, if it becomes unsupported and stops working on newer OSes/platforms and no one steps up to do the non-trivial work, or host the servers or whatever, you're still in the same boat.

6 ms·

Software going out of fashion shouldn't be an issue if you take care to use applications that have open data formats, or can at least export their data to somet

by wvh 10y ago

TeMPOraL 10y ago
And that is the reason I avoid most cloud-based solutions. I want my data to be in files on my drive, and not just in some database rows on a third-party server. Personally, I store all my notes in plaintext org-mode files in a Dropbox-synced folder.
rrdharan 10y ago
I think it's potentially underestimating the nature of the problem and OP's complaint to simply write off potential switching costs as "inconvenient". For example if I've developed a whole workflow around keyboard shortcuts, APIs, whatever, for manipulating a set of data using an app, and then that app disappears, even if I have the underlying dataset it might take me quite a while to get up to speed with a suitable replacement. All of that might argue against investing heavily in developing expertise with a closed, indie, proprietary, or even an OSS app[1]. Ultimately whenever you invest your time in developing a skillset or workflow you are inherently also obligated to evaluate the future risks involved. [1] Despite it being OSS, if it becomes unsupported and stops working on newer OSes/platforms and no one steps up to do the non-trivial work, or host the servers or whatever, you're still in the same boat.