3 ms·
It's unlikely that AVOS had a choice. Several months ago, the former product manager of Delicious wrote about a few options for its future (http://uniquehazards
by britta 15y ago
It's unlikely that AVOS had a choice. Several months ago, the former product manager of Delicious wrote about a few options for its future (http://uniquehazards.tumblr.com/post/2377362882/we-can-save-delicious-but-probably-not-in-the-way-you http://uniquehazards.tumblr.com/post/2377362882/we-can-save-...), and he included:
> But ultimately the real challenge here will be the technology. During my time at Delicious we rebuilt the entire infrastructure to deeply leverage a number of internal Yahoo technologies. It’s all great stuff but not exactly easy to remove or replace.
- tbrooks 15y agoThat's fair. I guess my larger concern rewriting the codebase, is they lose a lot of learned assumptions from users. For example, under the new delicious, if I click a tag in my tag cloud. And say it takes me to '/photos' and then I click another tag, 'house'. It doesn't take me to '/house', but '/photos/house' and the page isn't found. I've probably done this 20x today and the behavior is so ingrained in me that I can't function with their new UX. There are other nuances like this that make the new delicious extremely frustrating.