Hacker Newsnew | past | comments | ask | show | jobs | submit | Martindm's commentslogin

Nobody else mentioned it which really surprises me but I use Google Keep.

Allows you to organise cards, colour code then, pin them and share them across devices.

Anyone else use this? I find it's simple and restricted UI reduces distraction; just you and the idea.

Also good for check lists, links and reminders.


Google has a history of abandoning its projects (https://gcemetery.co/). What formats does Keep export to?


Very true. The way they abandoned Picasa desktop was rotten. A family relative of mine, not tech savvy, loved Picasa. When Google killed it, and tried to replace it with "Google Photos" where everything must be put online, this was confirmation that Google wasn't fit for the task of offering dependable reliable software.


I use Keep for everything. I just wish it 1) wasn't owned by Google and 2) started up faster.

It lets me create searchable yet unstructured notes, lists, and photos. It's unbeatable in terms of simplicity and functionality.


> It's unbeatable

I highly doubt that. If it's just notes, you could make your own web app that did a similar job, without the bloat and unpredictable "product development cycles" of Google.

I mean, why tie your creative note-taking to "Google Corp"?


You can also share Keep cards with other people's Gmail accounts.


And if "other people" don't have or want gmail accounts then tough luck? Doesn't sound like a valuable feature.


Not sure I'm on board with the premise if the article. Author presents duplication of HTML elements as a commonplace exception to DRY; This is not what DRY is.

Can't agree to overturn a tried and true best practice, in favour of the opposite, as the article suggests. While easy to play around and adhere to the dogma of DRY at all costs; namely making code difficult to reason and taking ages to do it; we just call this premature optimisation - DRY done with no critical thought about priorities.

Tldr; don't optimise for DRY too early or at the cost of what's most important or expedient. Use common sense and adopt DRY only as far as necessary for your team and to help others extend and be efficient working with your code. Not a bad article but maybe just complicating what we already have a name for.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: