This has been fixed. It was a bug, see this merge request: https://github.com/microsoft/vscode/pull/313931
There a quite a lot of toxic comments there already, please dont add to the pile.
überlegener Teekomsum
Inside the PIC64-HPSC: the SiFive powered RISC-V SoC that NASA intends to fly on every future mission | BonTech Labs
Telegram-Sperre: Russland im Kommunikationsdilemma
Package managers keep using git as a database, it never works out
Package managers keep using git as a database, it never works out
The OpenHW Foundation unveils the first industry-ready RISC-V ecosystem to advance European digital sovereignty
Schenker Element 16 is a "semi-modular" laptop with a repairable, customizable design - Liliputing
Mandy: ActivityPub on Goblins — Spritely Institute
rule theory
New Box64 v0.4.0 released (x86 to RiSC-V emulator)
Stromausfall in Berlin - kyrillische Fehler im Text? - Berlin Story News
nom rule
mimi rule
toilet rule
mimi rule
Newer RISC-V CPUs Vulnerable To Spectre V1 - Linux Mitigation Patches Posted
SiFive introduces 2nd Gen Intelligence RISC-V AI CPUs: X160, X180, X280 Gen 2, X390 Gen 2, and XM Gen 2
Christoph Hellwig Steps Down From One Of His Kernel Roles Following Rust Drama
attract rule in your area
Rule: the rule
bridge rule
There is a difference between the justified public backlash that happened and the piling on the developer who merged the request after it was fixed.