3 ms·
Don't apologize. It's a pretty common practice. Some e-commerce vendors may not like it, because it disturbs their statistics or marketing shenanigans, but the
by TeMPOraL 6y ago
Don't apologize. It's a pretty common practice. Some e-commerce vendors may not like it, because it disturbs their statistics or marketing shenanigans, but the error here is on their side - they assume that putting something in a cart is an intent to purchase. That assumption is wrong.
It's obvious why this happens. The shopping cart, as an e-commerce pattern, is a bookmarking tool. You put stuff there, it stays there while you browse the store for other stuff. If you step out for an hour and come back, things you added to the cart are still there. If you close the tab and open it later, the things are still there. If the price changes in between, it's updated. If an item goes out of stock, it's reflected on the cart screen. If it quacks and walks like a bookmarking tool, ...
The way for the e-commerce sites to stop it is obvious: put a time limit on the basket. Purge it if the user leaves it be for more than a couple hours. But for some reason, nobody seems to do that :).
As for the browser bookmarks, I also don't use them much (nor does anybody I know). They map badly to actual use cases. For short-term storage, tabs are perfect (especially when the browser saves them between restarts). For mid-to-long-term storage, you want to save your links where you can find them on any device, and often you also want to store them within the service itself (see also: stars on GitHub - they're not an expression of appreciation for the project, they're just bookmarks).
- ryandrake 6y agoI do this too. A good question for OP is: why is this a problem? Just let users do what makes sense to them. Why do you have to get them to stop?
- brigandish 6y ago> stars on GitHub - they're not an expression of appreciation for the project, they're just bookmarks Project maintainers often don’t think so. I think they should be just bookmarks and not a measure of popularity, better to hide the number of stars. It’d hopefully make some maintainers more humble and helpful. Maybe!
- mewpmewp2 6y agoThey are really good to understand whether project is used by enough folks for it to be validated and most likely maintained.
- brigandish 6y agoIsn’t that what the commit dates are for? Or the issue list?
- mewpmewp2 6y agoAmount of issues to infer how much library gets used? That might work, but it feels like amount of issues would depend very much on the complexity of the library itself. It would be great if this number was also on the main page then and it would be possible to sort by that, but it still feels iffy to use that. And maybe in some cases you would like to know amount of issues per amount of stars. With issue count if it's a simpler type of library you would imagine there are quite few issues, but you'd still like to know whether this library is validated by enough folks. If it has plenty of stars and very few issues, this seems to be indicative of a very good option. Ideally you look at all signals, also download counts from packagist/other managers as well. I just don't think it would be a valid idea to remove the star count in an attempt to make some folks more humbler. I doubt it would make maintainers more helpful.
- girzel 6y agoI like how Amazon has a "public list" and "private list" by default, in addition to all the custom lists you can make. Seems like the reasonable thing to do in the above case is to have a default "shopping list", and if someone puts an item into their cart and doesn't buy it within the allotted time, it gets automatically moved to the "shopping list". Make the shopping list highly visible on all the cart-related views. Problem solved?