But, as good as that opportunity is, I'm afraid the 3 years this administration has left wouldn't be enough to fully disassemble the US advantage. :)
But, as good as that opportunity is, I'm afraid the 3 years this administration has left wouldn't be enough to fully disassemble the US advantage. :)
It is not easy to get verified in vscode marketplace, even major publishers like Qt organization are not verified much less so a solo open source developer like myself.
Qt organization (because you mentioned it) also has verification. It displays a different message (because I haven't installed anything from them):
> The extension Qt Core is published by Qt Group. This is the first extension you're installing from this publisher.
> Qt Group has verified ownership of qt.io.
> Visual Studio Code has no control over the behavior of third-party extensions, including how they manage your personal data. Proceed only if you trust the publisher.
EDIT: I'm sure there are other extensions that are also by unverified publishers. It was the first time I was hit with that message though.
10 FORL=54272T054295:POKEL,0:NEXT
15 POKE54296,15:TI$="000000"
20 POKE54277,255:POKE54278,255
25 POKE54284,255:POKE54285,255
30 POKE54276,17:POKE54283,17
40 FORA=8TO1STEP-1:FORB=ATO1STEP-1
45 T=TI+2952/B
50 POKE54273,3: POKE54272,A
55 POKE54288,3:POKE54279,A+B
60 PRINTA,A+B
70 IFTI<TTHEN70
80 NEXT:NEXT
90 POKE54276,16:POKE54283,16
Also, what's the source for this program? I tried it on VICE and failed miserably. Maybe something (else) was copied wrong? Or is it supposed to fail on emulators?
> Do you trust the publisher "Ali Mostafavi"?
> The extension voil is published by Ali Mostafavi. This is the first extension > you're installing from this publisher.
> Ali Mostafavi is not verified.
> Visual Studio Code has no control over the behavior of third-party extensions, including how they manage your personal data. Proceed only if you trust the publisher.
Lol. That's _so_ in character
I think their docs could use a little bit of work, especially there should be a defined path to switch from a requirements.txt based workflow to uv. Also I felt like it's a little confusing how to define a python version for a specific project (it's defined in both .python-version and pyproject.toml)
Try `uvx migrate-to-uv` (see https://pypi.org/project/migrate-to-uv/)
I'm sure someone could whip up some merch super quickly as souvenirs/protest
The King. Sorry to spoil The Crown for you, but Queen Elisabeth II has been dead for a few years.