If you've ever done an international wire, you know there's the form question "What intermediate bank to use". So at least the same if not less middlemen apply.
Everyone saying "muh GDPR" has no clue none of it applies to financial transactions.
To get a PSD2 "Open Banking" license one needs to KYC every user and keep every transaction that passes through the system, for 5 years, including the KYC data.
Being PSD2 licensed doesn't even make you a bank. Just imagine what an actual bank has to keep around...
Also every business has to keep invoices and transaction data around for tax audits, usually 7 years. So you can GDPR delete request all you want, but the shop where you bought that thing still has to legally know you've bought it.
If I'm a guest, visting NYC and looking for the next place to stay, I would be logged in and Airbnb would know very well I'm from out of town (payment details etc.)
Dutch people and government are obsessed with (limiting) speed, instead of focussing on keeping distance.
A nice effect of distance is less braking, which means less energy converted into useless heat and less ghost traffic jams.
It always amuses me to hear local radio news about yet another multi-vehicle collision.
In Germany, the country known for it's wonderful Autobahn, you can temporarily loose your license for tailgating.
The msgpack serializer was probably used in a suboptimal way. The integer 3 can be encoded by msgpack in one byte as well. I never use doubles which is probably why I didn't think of this case.
Integers are actually always <= bytes in msgpack than the JSON ascii representation.
Ever since I've started programming in haXe, it became clear that the language you code in should never be completely tied to a single platform. This article hints at Flex dying and tech needing replacement, yet many parts of an application (lets call it domain model and business logic) should be unique and not rely on a specific platform or data exchange format.
When you write your data model in a language that works on client and server platforms, you save lots of duplication of effort and gain flexibility.
The best example of experiencing the opposite I have is a fairly large application I worked on, where the backend developers designed a totally different set of classes around a (pretty much undocumented) XML structure than the frontend guys. Basically all communication happened through XML. Sure "it's an open format!", "it's human readable! (in a sense)", but taking over this project figuring out semantics and what was considered valid became a painful effort.
Your frontend should always use the same domain model as the backend. Designing the fundamental parts of your application without relying on an ORM, XPath, JSON, .NET, Scala case classes, Flash, Javascript, HTML5, Swing, whatever... makes you platform agnostic and shrug at the next internet technology death.
Am I happy Flash is considered dead? No, currently HTML5 lacks many features I rely on today and sanity (isn't it kind of bizar we consider cross-browser issues as normal?). Will my skills and all of my codebase die with it? Absolutely not.
Isn't it quite easy to block USB storage devices at the OS level? I mean hiding the stick is clever, but it shouldn't really matter. If you only allow HID devices, the mouse still works without getting access to the data on the stick.