Self checkout works fine for large amounts of items. You grab a portable scanner at the entrance and scan items as you put them in your cart. When you arrive at checkout you already scanned all your items and all you have to do is pay.
Self checkout customers cannot verify their own age for age-restricted items.
Age verification happens asynchronously and causes zero delay for anyone who doesn’t look like a teenager. The employee overseeing the self-checkout gets an alert on their tablet-thingie, they take one look at me and press approve. You can just keep scanning items while this happens. Usually the ‘your age may be checked’ alert disappears within seconds.
Self checkout customers cannot scan something and report the number of duplicates (e.g., scan a can and punch in that you're buying 8 of them).
They can where I live.
In most stores, self checkout customers are policed by the system to make sure that each item is placed onto a scale that weighs everything, and stops the process if weights don't match up.
I’ve never seen that, and I’m not aware of any supermarket chain in my country that does this.
The ergonomics and flow of self checkout doesn't allow for a conveyor belt style rapid scanning, because a self checkout station is a tighter space and tends to require bagging as you scan, instead of scanning and bagging separately and independently.
The conveyor belt slows things down. You take an item out of your basket, scan it and put it in your bag in one go instead of it being two separate actions. You’re only handling each item once instead of twice. Besides, if you’re planning to get a lot of items you scan while shopping, not at checkout. You get a portable scanner, put it slot on your cart and just scan each item as you put it in your cart.
As a result, self checkout tends to be slower for customers who have more than 20 items.
If you scan while you add items to your cart it takes less than 10 seconds to check out, regardless of how many items you have
That might be offset if there's a longer line for regular cashier, but if there's no line the employee cashier is much faster.
My local supermarket has a grand total of 1 regular cashier, versus 16 self checkouts. If you go during a busy time you have to stand in line. Since the regular cashier is basically only used by people who don’t want to or can’t use self-checkout for some reason (that is: usually elderly people) this line doesn’t move very fast.
When it’s a quiet time of day there often isn’t a regular cashier at all and you have to ask the person overseeing the self-checkout who then has to call someone to help you out as they cannot leave the self-checkout isle unattended so you end up waiting for a cashier to arrive.
Self checkout is always faster, by an order of magnitude.
Why would you be pro self checkout? Besides the extra time and effort for the customer to check out if they have more than a couple items
In what alternate reality does self-checkout take more time and effort?
If you go to a cashier then you have to wait in line. At my local supermarket there is one cashier vs. 16 self-checkout machines. Even if you go at an extremely busy time there is almost always a self-checkout machine available.
With self-checkout you simply scan the items from your basket and put them in your bag. With the cashier you have put all your items on the conveyor belt, wait for them to be scanned, then put them in your bag.
If you have more than a few items you simply grab a hand-scanner or just use the app on your phone and scan the items as you put them in your cart. Then you just go to a self-checkout machine and pay. No unloading the cart at checkout, you just pay and take your cart to your car.
the problems and delays they cause where they have to provide employee assistance anyway ("Unexpected item in bag", etc)
What do you mean unexpected item in bag? The self checkout machine can’t look into my bag.
The article also talked about people getting in trouble for accidentally not getting something scanned.
Never seen that happen. You get random bag checks before you pay (so at that point it’s technically not theft). If you missed something, they simply re-scan all the items and you pay the correct amount, that’s all.
I get why bike racks are used when there are a lot of bikes, as you can pack them closer together. If at all possible I’d rather not store my nice bike in one, too easy to damage the bike. Especially the way this is placed, with bikes blocking much of the sidewalk.
Trump Watches are intended as collectible items for individual enjoyment only, not for investment purposes. The images shown are for illustration purposes only and may not be an exact representation of the product.
And yet, I’ve never run into RAM problems on iPhones, both as a user and as a developer. On iOS an app can use almost all the RAM if needed, as long as your app is running in the foreground. Android by contrast is much stingier with RAM, especially with Java/Kotlin apps. There are some hard limits on how much RAM you can actually use and it’s a small fractIon of the total amount. The actual limit is set by the manufacturer and differs per device, Android itself only guarantees a minimum of 16MB per app.
The reason is probably because Android is much more lenient with letting stuff run in the background so it needs to limit the per-app memory usage.
Those apps also use more RAM than an equivalent iOS app, simply because they run on a garbage-collected runtime. With a GC there is a trade-off between performance and memory usage. A GC always wastes memory, as memory isn’t freed immediately once no longer in use. It’s only freed when the GC runs. If you run it very often you waste little RAM at the cost of performance (all the CPU cycles used by the GC) if you run it at large intervals you waste a lot of RAM (because you let a lot of ‘garbage’ accumulate before cleaning it up). In general, to achieve similar performance to non-GC’d code you need to tune it so it uses about 4 times as much RAM. The actual overhead depends on how Google tuned the GC in ART combined with the behavior of specific apps.
Note that this only applies to apps running in ART, many system components like the web browser are written in C++ and don’t suffer from this inefficiency. But it does mean Android both uses more RAM than iOS while at the same time giving apps less RAM to actually use.
It basically comes down to different architectural choices made by Google and Apple.
Clothing and tech in a supermarket?