TSMC is a publicly traded company just like the others. I'm not familiar with their governance but Google tells me the largest owner (a state development fund) has 6%.
They have a special advantage because they don't compete with their customers, which leads to trust, which leads to customers paying for their R&D for them.
Intel on the other hand just kind of sucks at their job. Skill issue basically. (But they aren't /that/ far behind.)
The specs and the test suite are both moving targets. There are regularly new proposals to the specs, and new tests that cover them as they progress towards acceptance. The main engines implement these proposals behind feature flags, and only enable them once the proposal has been fully accepted.
Ladybird does not hide implementations behind feature flags (yet) because there's no need when you don't have users. So its score on test262.fyi includes all proposals it has implemented thus far.
The other engines on that site have an "experimental options" variant to include these proposals, which is a bit more of an honest comparison. As of right now, that shows: Spidermonkey (Firefox) at 98.3%, V8 (Chrome) at 97.9%, LibJS (Ladybird) at 96.9%, and JavaScriptCore (Safari) at 93.2%.
Probably that there are already several generations of TPU hardware - the best ones go to internal use, while the older hardware gets rented out to gcp to amortize the development costs.
- you don't need to understand the whole in order to help
the kind of bugs you can start with are like :
- this icon is a bit weird, it's off centre by 2px - how do I add 2 pixels to this icon? either by moving it or by changing the underlying image asset? if I'm moving it, what is the subroutine that paints it? if I'm changing the image asset itself, where is it stored? (is it in a packed store? or is it just a plain file, etc)
- when I click this button, trace the pathway - it's supposed to add to history and turn blue. is it doing that?
etc.
For large projects, start super small and work your way out from there.
It was rough a few years ago, but nowadays it's pretty nice. TI rebuilt their Code Composer Studio using Theia so it does have some larger users. It has LSP support and the same Monaco editor backend - which is all I need.
It's VSCode-with-an-Eclipse-feel to it - which might or might not be your cup of tea, but it's an alternative.
Agreed not the most well thought landing page, but the explore page gives a good insight of how it’s being used and what it looks like: https://theia-ide.org/theia-platform/
(Scroll down to Selected Tools based on Eclipse Theia)
The feature that keeps me from moving off of vscode is their markdown support. In particular the ability to drag and drop to insert links to files and images *. Surprisingly, no other editor does this even though I use it all the time.
I took the plunge and don't regret it. Despite the condition of the web site the extension is very useful and relatively free of any annoying bugs.
At some point in time, I'd like to take the time to invest building a custom version of the extension to bump dependencies to access more modern support for plantuml/mermaid diagrams.
I belong to the class of people who believe in customising their tools as they please. So I'd have written an Emacs package to do this. But then again, this is Emacs, so someone's probably already done it. Oh, here it is: https://github.com/mooreryan/markdown-dnd-images
Yeah , INSEAD of forking vscode which is not modification friendly they should justuse theia because it is maintained to be modular and allowed to be used like a Library to build IDEs of your choice.
Eclipse (as in ecosystem) is fairly popular in Enterprise, but since it exposes all the knobs, and is a bona fide IDE which has some learning curve, people stay away from it.
Also it used to be kinda heavy, but it became lighter because of Moore's law and good code management practices all over the board.
I'm planning to deploy Theia in its web based form if possible, but still didn't have the time to tinker with that one.
Using Eclipse as "the Java LSP" in VSCode makes more sense now.
Nevertheless, as much as I respect Erich for what he did for Eclipse, I won't be able to follow him to VSCode, since I don't respect Microsoft as much.
So not also using Github, LinkedIn, TypeScript (any FE framework that uses it), any Microsoft owned studios games, no Linux kernel contributions, GHC contributions,....
It is kid of hard to avoid nowadays.
Here a session with him related to VSCode history,
"The Story of Visual Studio Code with Erich Gamma and Kai Maetzel"
This is why I used "(as in ecosystem)" in the first paragraph. It was a bit late when I wrote this comment, and it turned out to be very blurry meaning wise.
What's wrong with that? If they re-implement the whole thing it would amount to the same code size. It's the JDT language SERVER not some sort of "headless" software with UI needlessly bundled.
Java isn't quite what I think of as lightweight. I mean it probably can be, but most Java engineering I know of is all about adding more and more libraries, frameworks, checks, tests, etc.
Think about how Intel, who pioneered the know how, can't build cutting edge nodes in the levels that they need to make it profitable.
IBM had to sell their fabs to cater to the whims of "shareholders".
It's the greed of stockholders that you need to blame.