829 karma · joined May 10, 2013
The Rust port doesn't change performance much according to the pull request description.
See: - https://www.adyen.com/knowledge-hub/guides/global-payment-me... - https://stripe.com/en-us/payments/payment-methods-guide#paym...
I was in the market for a new washing machine and noticed the Miele W1 machines now have something similar called "TwinDos". You can still add detergent the old-fashioned way but it had me wondering if this is a lead-up to the same business practices we see with Nespresso and inkjet cartridges.
The article has a couple of other weird faults, too:
1. I'm not sure why the author is complaining about FIDO2 having backwards compatibility with U2F/CTAP1. The article even incorrectly claims FIDO2 is "a 3rd incompatible standard" only to counter-argue the point a few paragraphs below explaining CTAP? People not having to throw away their perfectly fine old devices is a good thing in my book.
2. "All FIDO standards are web-centric and aren’t designed with any other client software in mind" the first part is true, the second part not so much. For example FIDO2 supports silent authentication (no user interaction) while WebAuthn explicitly does not[0]. It also supports the hmac-secret extension[1] which is used for offline authentication with Azure Active Directory[2] and IIRC no WebAuthn browser implementation exposes this extension to web apps.
[0]: see e.g. discussion on https://github.com/w3c/webauthn/issues/199
[1]: https://fidoalliance.org/specs/fido-v2.1-rd-20210309/#sctn-h...
[2]: https://docs.microsoft.com/en-us/azure/active-directory/auth...
This is fine as long as everybody follows ISO4217. In my experience many 3rd party systems _mostly_ do it and of course you get bitten by the edge cases.
For example, Stripe decided HUF doesn't have 2 decimals (I know that's how it's used in practice today but we're talking standards and system interoperability here), or that ISK subdivides into hundreds ("cents") in contrast to the ISO tables. Compare https://stripe.com/docs/currencies with http://currency-iso.org/en/home/tables/table-a1.html. As Stripe notes for UGX, backing out of this is nearly impossible because of the subtle break in backwards compatibility. And who knows how other payment providers deviate in their own way.
For my own sanity and that of my coworkers (e.g. easier analysis for extracted tables in the data warehouse) I strongly prefer avoiding this headache and use decimal instead. You can do the appropriate rounding for a currency in your money object as for example https://www.martinfowler.com/eaaCatalog/money.html does.
CCS type 1 (J1772) and type 2 (aka "Mennekes" used in Europe) are not compatible? Both are described in IEC 62196-2 so I am not sure which other connectors could be compatible here.
> And yes, Elon could easily say "Tesla is moving all production to CCS2, all future Teslas manufactured after today will be CCS2, all Supercharger stations will be retrofitted with CCS2 cables"
This already happened in the European Union FWIW.
While digging in to how their network is built, I found out it seem their infrastructure is from AddEnergie, a Quebec company that's also the provider for the eCharge (New Brunswick) and the BC Hydro EV. They have their own consumer brand for home chargers and public charging network across Canada called FLO. They seem to be growing fast (closed their series C last year), their product seems to be pretty good, so it doesn't have to be all terrible.
Either way, 10 pages isn't so bad but tens of thousands can become troublesome as explained on https://shopify.engineering/pagination-relative-cursors
I've been looking at BMWs this year and IIRC they backed out of this after the backlash: https://www.autocar.co.uk/car-news/technology/bmw-u-turns-ap... - agree with your other points though.
See more at https://webauthn.guide/