There is no rule that there has to be a single payment per authorization, if you read for example mastercard API https://in.gateway.mastercard.com/api/documentation/integrat... it says you can partially capture, you can extend authorization. So for all you know when you buy at amazon it just updates the authorization and charges you later but keeps authorization going and amazon might just check if they have auth token for your card and if they do system allows you to continue and to you it seems instant.
It’s a lot more complicated and nuanced than that. The API docs you link too are for an API that covers a tiny fraction of what can be expressed in the actual ISO 8583 messages which are the real “API” of the card networks. The docs for those are hundreds of pages long.
Plus you need to analyse how the different messages types and sequence of messages interact with the transaction processing rules, which are also hundreds of pages long.
Suffice to say, the entire system is insanely complicated, and just about everyone out there implements it all incorrectly, with the whole system on working because partners are only allowed to complain about the insanity if they actually loose money. Until that point they’re expected to just handle everything as best they can.
This is only true if people stick to a version of a language and don't upgrade.
If you upgrade then, for example, you can't run all of your PHP 5 code in PHP 8, most of it you can but you will have to change the parts that are broken, which are the areas that are repaired in PHP 8.
Is that just sloppiness on their part or is it LLM chat bots being used with a prompt "hey give me current versions of these languages" without verifying the result?
I think by crash they mean program stopping execution and being unable to continue, so by that metric Erlang didn't fully crash.
Erlang is designed with a mechanism that makes it easy for external processes to monitor for crashes (or hardware failures), rather than an in-process mechanism like exception handling used in many other programming languages.
Erlang was designed with the aim of improving the development of telephony applications.
The Erlang runtime system provides strict process isolation between Erlang processes (this includes data and garbage collection, separated individually by each Erlang process) and transparent communication between processes on different Erlang nodes (on different hosts).
The "let it crash" philosophy prefers that a process be completely restarted rather than trying to recover from a serious failure. Though it still requires handling of errors, this philosophy results in less code devoted to defensive programming where error-handling code is highly contextual and specific.
It is ongoing project but there doesn't seem to me enough financing, the money that EU allocates only cover about half of the required budget so they are looking for investors.
Correct it is a new rail line not an alteration of existing tracks, but it goes into some existing and new (mostly cargo) stations so some stations will have both gauges of track.
I don't think it is fair to compare Netherlands to other countries like UK or France because Netherlands has a well established culture around bikes and bike lane infrastructure is one of the best in the world, so it will be the last country that will have any issues because of e-bikes.
Well, we (in NL) are used to bikes going mostly the same speed and people in cars and bikes following the rules. With overpowered fat-bikes, it's now much more chaotic than a decade ago.
The established road / bike path system here runs so smoothly that changes like this cause problems. People can't seem to improvise. I've also been to Cairo a lot and had a bit of a traffic culture shock. I believe that the chaotic Cairo traffic seems to cope much better with unexpected situations.
