Expecting Facebook or Google to pay publishers is like going back in time to 1970 and saying that a newsstand should be paying newspaper publishers for the privilege of selling their papers.
WiFi SSID, along with the signal strength is used to precisely locate a person down to ~ a meter. Commercial GPS capabilities don't have that level of precision, but when you combined with WiFi information, you can.
There's always a push and pull between old and new tech and I agree some of the hot new tech is regurgitated old tech, but most of your examples aren't really comparable.
I would say that my examples are rhymes, different developments of the sane theme. They are not literal repetitions, of course; comparable, not identical.
Because a security vulnerability in the common library will have a much larger impact. It also increases the potential attack surface by adding more components. Companies value the secrets they keep and want to make sure they have 100% vertical control, where they can audit everything.
Also, at any project with a sane architecture, you're using 1 vault and maybe 1-2 ambient strategies to pass the data. You won't use all the vaults at the same time anyway
> Also, at any project with a sane architecture, you're using 1 vault and maybe 1-2 ambient strategies to pass the data. You won't use all the vaults at the same time anyway
You're assuming the secrets here are managed by infra+glue added by a DevOps team when deploying an app.
I'm talking about use-cases where the secret-handling is designed into e.g. a cluster-scale deployable virtual appliance, where you configure the app through its UI or deployment-time config files to access your "secrets provider" of choice. (Think "deployable PaaS.")
All service interchanges take a lot of space. Europe has a lot of system and service interchanges too. DD doesn't take a lot more space than a regular cloverleaf, which is commonly found all over Europe. It is however, less flexible, as the loops in cloverleaf can be shaped to fit the area.
It is capable flowing quite a large amount of traffic, so it's not suitable for building anywhere.
It always seemed so needlessly complex, relative to well-established RFID tech -- Uniqlo can count the number and type of garments in a pile in a big bucket, and compute an invoice from that.
Even if you couldn't do this at the exit, seems like it would have been a far easier lift to incorporate the same idea into shopping carts or baskets all along.
The cost-per-unit on RFID product tags (EPCs) has tended to limit them to products with a relatively high margin and a relatively high theft potential---clothing being the most obvious example and the most common application of EPCs, with retailers all the way down to WalMart using them for apparel.
You'll note that WalMart doesn't even use the EPCs at POS, which is telling: for most retailers, the main advantage of EPCs is far more actionable alarms at the exit. So they're limited to items where loss rates make the added cost worth it.
The problem is that the grocery industry has notoriously low margins, and the unit price of EPC tags can be the entire margin on a lot of products. On the one hand, Amazon may have been trying to work around the need for higher-cost tags to roll out this kind of automation. On the other hand, I have heard anecdotally that Amazon Fresh pricing was relatively high, so maybe EPCs would have been a wiser use of their extra revenue.
Amazon Fresh was definitely not the cheapest option. It was on par with Whole Foods for groceries, IME.
But that said, interesting point. Didn't know the cost of an RFID tag was that high -- after all, Uniqlo is putting them on some pretty cheap clothing items!
Rfid tags are really cheap, some sellers advertise prices as low as 3c per tag but realistically 10c is probably the cost of a finished product (print, glue, maybe extra protection of the plastic)
That's the problem though - $0.05 is a LOT to a grocer, that's all they keep on a lot of products. Barcodes are free since they mostly go on labels that are being printed anyway. They could push for source tagging, but the vendor would pass on the cost, and grocery is a very price sensitive industry.
For apparel, on the other hand, source tagging is common - even before EPC on higher end goods, Calvin Klein used to sew magnetostriction tags into clothing. Apparel just has so much more price elasticity and loss prevention is a huge part of that industry. Tools are another industry where EPC and source tagging are common, once again, high dollar items with a lot of theft.
