That's exactly why I stopped using Svelte. Claude is much more sensible when generating React. Looks like a bleak future where only the most popular library survives.
That's not a typical leetcode problem though. Most companies ask things like "solve this slightly modified knapsack problem" which takes 5 minutes if you know the solution and 50 minutes if you don't.
I found VSCode's remote plugins to be a really good option when the code lives on a shared remote machine over a slow connection. vim+scp is an extra step on each change, vim over ssh is just awkward, and sshfs isn't the most reliable piece of software.
This kind of stuff requires access to the complete architectural parameters of the device, so adding support for even a single device family is a huge reverse-engineering^W documentation effort.
See f4pga.readthedocs.io which consolidates pretty much everyone's efforts into a distribution, but supports only 4 device families: iCE40 and ECP5 from Lattice, some 7-series devices from Xilinx and EOS-S3 from QuickLogic.
For internal testing, VPR has "Stratix IV-like" and most recently "Stratix 10-like" architecture files but these don't try to "document" the whole thing, they just want a close enough approximation to a modern device to evaluate the tool better.
Most sane right-to-repair advocates don't oppose microscopic parts or glued batteries. They oppose deliberate measures against repair, such as:
- Parts which are produced by a third party who signed a contract with the manufacturer to not sell the part to other people. So you cannot find whatever $2 power management unit in your phone's main board even if you are willing to use complex equipment to replace it.
- Parts which "marry" their devices and refuse to work when you plug them into another device.
This kind of behavior actively fights against you repairing the device. I find it unacceptable.
If this future happens, people might "fall back" to their native languages for internet writing. I'm already thinking about this: if I wrote something which could potentially get me in legal trouble, like a reverse engineering post, I would probably write it in my native language. Kind of similar to torrent trackers in Russian or obscure phone mod forums in Portuguese.
"Building" for the latest process and large volumes is another story, but as far as I can see, large scale logic design is something not _that_ far away from software. Large scale, open source, and performant software designs exist in the wild. (see Linux, llvm, ...)
Why wouldn't we get a logic netlist which could perform reasonably well when placed on silicon by people who know what they are doing? (Yeah, lots of handwave.) I'm asking this out of curiosity. Not an expert in the field by any means.
Another effect is that the sound variety in the language was reduced. The new alphabet has "n" for both "ŋ" and "n" sounds. Now, in year 2020, no one spells out ŋ. See "taŋrı", "seniŋ", etc.