If you have a basic site that doesn't work you can open an issue on the repo. If you have some relatively simple site, its useful for the team to know what features that people are using are broken.
Only a few components of Servo that got split out are used in Firefox. A number of them are shared between the 2 (and servo having the smaller team usually follows the Mozilla upstream)
Speaking only for myself, I think a big part of this is that to be comfortable recommending any browser to be used as a typical browser would require a pretty substantial base set of security features/layers. Servo has a few pieces in place but some of those features are only available on some platforms.
It is much easier to recommend it to be used as an embedding solution where the embedder is usually choosing to only render specific pages as an app.
It is pretty exciting, there's lots of big projects constantly being undertaken in the codebase. In terms of being "greenfield" I will say that the layout engine got rewritten starting in 2020, became the default in 2023, and the legacy one got fully removed in early 2025. There's a lot of reorganization and re-architecting going on in the net and storage components as we speak. There's opportunities to redesign systems to align with newer versions of the various RFCs/WHATWG specs. Basically lots of work to do to stay modern.
The location they have that's "well into construction" is SPARC, which is not intended to be a net power production facility. It will host their net gain demonstrator that they intend to have first plasma in next year and target a net gain demonstration in 2027.
ARC which they announced siting for and is intended to be their first grid-attached net power provider only just had the location selected so I don't believe its got much construction going on yet. The goal for that plant to be producing power is "early 2030s".
Ah, maybe not well into construction. But a friend of mine works with exotic materials and they are purchasing lots of things for ARC. Though I imagine these materials have a long lead time.
According to the IEA "Heat accounted for almost half of total final energy consumption and 38% of energy-related CO2 emissions in 2022" so finding ways to create process heat that can reach hot enough temperatures efficiently from electricity is a big deal for industry.
but this approach stalled because it doesn’t implement validation of TypeScript: the TypeScript annotations are simply ignored. I felt this defeats the point of using TypeScript. We probably need to use tsc instead of esbuild to get type checking. Hints welcome!
Okay, thanks! Now next question which comes into my mind: is there info about the regex engine they are using? I would expect there is some (proprietary?) C++ library also used in other MS products or are they even using a FOSS licensed one?
Seems likely that if they explicitly say they're supporting the PCRE2 syntax it is because they are using the BSD licensed libpcre.
Reinventing a regular expression system is very far down on the list of things I'd ever want to do. Those things are filled with dragons and require years of refinement to get the bugs out.
