|
|
|
|
|
by politelemon
303 days ago
|
|
Given that the aim is to still visit the URL, this appears to be browser bookmarks with extra steps. I am not seeing an advantage to the external storage mechanism and the overhead it brings. Browsers have been doing an excellent job of managing bookmarks, you can tag and search for them from the address bar itself which is very convenient. |
|
If you organise them you can even reference them from the codebase, or the documentation to avoid clutter. The format is simple and dumb enough so that a simple bookmark.txt can be converted into a dictionary, array that can be used in the program if some URLs are supposed to be used there.
It's not revolutionary by any means, but I have to confess that it didn't occur to me that's a great per repo documentation reference tool or per folder.