Human writes the requirements, contains flaw.
Human or AI translate that to specifications, and eventually code.
It does not matter if the middle man is human or AI, or written in "traditional language" or "formal verification". Bugs will be there as human failed to defined a bullet proof requirements.
2k feels very small considering the number of business sites that embed Google Maps. I guess a lot of those sites use other website building services that handle the Google API keys for them, and/or they're old and untouched enough that no one enabled Gemini on them.
I had the same thought. I guess a lot of those keys may belong to dormant/deleted accounts and only a % of people who have enabled Gemini (presumably it required user action)
I did. Specifically the part about "When you enable the Gemini API". This doesn't take into account that people may have had years old forgotten about other services they use.
Fair enough. It's a reasonable expectation of someone that enabled Google maps 15 years ago that enables Gemini 6 months not to understand the fundamentals of how Google treats their keys. If it wasn't explained on the enabling Gemini screen, what do you expect the user to do.
Totally agreed. But it clearly requires user action. I have some old projects that only use Google Maps for websites and that wouldn't magically be impacted. Google needs to do better though
Fixing the problem requires 2 resources, the knowhow and the money. People need to know how to execute it safely, and people need to have the disposable income to run their PDS.
Even for tech people in HN, not everyone will have the disposable income to self-hosted every digital life lands on. Somehow, somewhere one may need to use free services paid by VC money.
Now, instead-of hand-written vector instructions, look at programs transliterated line-by-line literal style into different programming languages from the same original:
But that's not the javascript, it's how it's used (react or whatever)
You can write terrible non-performant code in assembly and C, and perfectly speedy pages in html and javascript (say the page you're on at the moment).
You wouldn't write a new cutting edge video codec in javascript - not one you wanted to use anyway - but given that we had performant guis running on 286s at 12MHz, Javascript being 1/10th the speed of C isn't the problem.
Good luck telling a FOSS project what to do. At the very least you'd have to pay for the work and it seems to me they could claim whatever price they want.
https://www.youtube.com/watch?v=qB4cdRgIcB8
reply