I should add that using unsafe.Pointer I'm able to get a significant boost on little endian platforms, with no loss of safety (pointers are still bounds checked).
With this change, my ported driver would beat wazero on most benchmarks. I do need two 20 MiB blobs of slow to compile, unreadable, Go code in my repo, though.
I tend to use numFoos (short for “number of foos”), and only use fooCount when the variable is used for actual counting (like an errorCount variable that is incremented for each error).
Countof is strange, because one doesn’t talk about the “count of something” in English, other than uses like “on the count of three” (or the “count of Monte Cristo” ;)).
The other day I asked AI to one-shot an implementation of hyperbolic trig functions for double-double floats.
I provided a repo (mine) that already implemented double-double arithmetic, trigonometry, and logarithms/exponentials, with plenty of tests.
It produced something that looked this good. It had tests, it followed the style of the existing code base, etc. But it was full of shit and outright lies.
After I reviewed it to fix deficiencies, I don't think there was anything left of the original.
I had much more success the previous week using an AI to rubber duck the algorithms to implement trig.
I am incredibly sceptical that just adding more loops — and less critical thinking/review — to brute force through a solution, is a good idea.
If you’ve worked on a code base built by more than you, you don’t understand and you don’t have control. Part of being an experienced engineer is understanding how to deal with that effectively at scale.
It's an app that uses NFC or, if needed, reads a QR code and does a web request (i.e. needs internet).
Neither Google nor Apple will block that, or take a cut; and it's already available in multiple markets.
This is about taking stuff that already works in one or two countries, design a similar system that works across countries, and mandate that all banks under ECB supervision implement it.
Digital Markets Act, also Apple nearly lost their payment monopoly in Germany as powerful banks lobbied for a law forcing them to open up. It was passed, but then they didn't want to use it. If I would guess, Apple offered them preferential conditions to not have a precedent.
Lack of negotiation power. Less control over Android than Apple has over iOS.
Google keeps self-sabotaging Android Pay. They lacked market power so cellular carriers blocked it hoping to advance their own payment ecosystem (ISIS). Google changes the payment brand every few years, and fragments it into two separate apps or combines them. It's rather like their messaging strategy.
With this change, my ported driver would beat wazero on most benchmarks. I do need two 20 MiB blobs of slow to compile, unreadable, Go code in my repo, though.
reply