Author here. The article is making a case that Google has in fact captured the Web, and secondarily that there are some clear reasons for it. I had no intention of writing a dissertation on the history of the Internet. Also, filling in the missing technical gaps would be several RFCs.
As for what would native payments look like:
1. I put the element <pay-me>$1.00</pay-me> in my HTML
2. User clicks on Pay Me button in any browser and I get $1.00
Something like that. Anything more complicated and for most people it might as well not exist. Grandma isn't loading up a Bitcoin wallet.
> 1. I put the element <pay-me>$1.00</pay-me> in my HTML 2. User clicks on Pay Me button in any browser and I get $1.00
And then what? If all that is needed is a tag support then why is the problem not yet solved? I mean if it is so simple to add support in HTML, why not just add it outside HTML?
I'm not asking for the actual final RFCs, but just some idea of what everyone except you is missing which makes this an easy problem to solve for you. Just broad strokes will be awesome. At the moment all you are saying is that the architects did not know what they were doing, but can't explain what they missed.
Having an html tag, and even a browser that interprets it and connects to grandma's saved credit card is not the problem. But where does the money go to? It has to be a central body that holds all accounts and the page can specify their wallet id in another tag. How do you create that in the spirit of the open web?
As for what would native payments look like:
1. I put the element <pay-me>$1.00</pay-me> in my HTML 2. User clicks on Pay Me button in any browser and I get $1.00
Something like that. Anything more complicated and for most people it might as well not exist. Grandma isn't loading up a Bitcoin wallet.