3 ms·
Yes, you could add support for it. To what end? Do you think the usage will be high enough to justify the effort to implement and maintain it? Even imagining t
by D13Fd 5y ago
Yes, you could add support for it. To what end? Do you think the usage will be high enough to justify the effort to implement and maintain it?
Even imagining the ideal world where every to-do app implements this, portability of to-do items between apps just isn't that big of a problem. There isn't a big need to move long lists of to-do items between apps.
And in the real world, this won't be implemented perfectly. You'll have the App A implementation, the App B implementation, and so on. Look at Markdown. You'll have headaches migrating your to-do items automatically and in the end, most likely, you'll just end up copy and pasting them. It's not that hard and old to-do items aren't that important to the vast majority of people.
- vhanda 5y agoThis sounds a bit defeatist. Yes, it won't be perfect at first, but there is always a chance of reducing the barrier to entry. The lower it is, the more % of users / developers / apps are going to use it.
- D13Fd 5y agoIt's not defeatist. As I said, I just don't think, even in the optimal scenario, that it is a goal worth achieving. Personally I'd rather software developers focus their time on more worthwhile features.
- paulryanrogers 5y agoWhat is worthwhile can vary widely. Like the quote that people use only a slice of Word, yet often different slices.
- vinodkd 5y agoNot sure I agree. I didnt know about gitjournal until vHanda's post, but immediately saw how it could be a replacement for my use of Google Keep (which I use when I'm on the go vs at my laptop). And there was already an exporter for Google Keep. I'm guessing that exporter benefited from a spec being available. Your point about "if you're the only one using it, just use it" does apply, but sometimes we do find ourselves being more successful than we originally expected and defining things via a spec is not a bad thing.