Unfortunately, as much as I hate to admit it as someone who has left Chromium behind personally, Chromium is kind of the only choice. I think people outside the browser implementation world underestimate the sheer scale and complexity of the modern browser stack and what goes into maintaining compatibility with web standards, much less advancing them.
We've reached the point where Chromium is essentially the de-facto web standard because Chromium engineers do the lions' share of feature testing and development, because Chromium receives the lions' share of funding.
Igalia, an OSS consultancy that does a lot of fairly-funded independent browser development, has lots of material about this. For example, the recent chat between Igalia members and someone from Open Web Advocacy about what to do if the anitrust ruling against Google jeopardize's Chromium's funding, and the options are pretty dire.
Edit: After reading the article, I think this is a really good sign. Bringing together the immediate stakeholders in Chromium's development and funding bodes well for the possibility of stewarding Chromium in a less Google-dependent, profit-motivated, ad-centric direction. There's unfortunately a lot of uncertainty about how this will all shake out, but it's possible that Chromium could become a truly independent project and move back in the direction of user value instead of user-hostile shareholder value.
Microsoft produces a plethora of good learning materials if you're struggling with the basics or specific concepts. I recommend their C# for Beginners course to get a good overview of real C#.
Once you have a good handle on the basics, I would echo others' advice that having some kind of project or goal to work towards is the surest path to learning, because you have external motivation to use what you're learning and look up things as you need them. Is there some reason you chose C# specifically as your next language, maybe for game dev, web dev, or Windows apps?
YAML is truly an untenable format. I'm personally excited for KDL to stabilize and hopefully see wider adoption, but in the meantime I'm fine sticking with JSON most of the time.
Thankfully, development of Servo has been revived, and it's now fully independent of Mozilla. I believe it's now being stewarded by the Linux Foundation of Europe, with a lot of contributions from Igalia.
The fact that there's no option to express my anger over the environmental cost of AI is infuriating. There is no responsible or positive use of AI when it's accelerating the destruction of our climate.
I have stopped giving Apple my money, for this among other reasons. I have to say, though, that Asahi Linux makes a compelling case for repurposing their hardware for better use.
I mean, the simple proof is that Rust has been growing by leaps and bounds in the embedded world, which is the closest to bare metal you get. It’s also being used in the Linux kernel and Windows, and there are several projects building new kernels in pure Rust. So yeah, it’s safe to say that it’s as close to the metal as C.
Also, the comparison to Java is understandable if you’ve only been exposed to Rust by the memes, but it doesn’t hold up in practice. Rust has a lot more syntax than C (although that’s not saying much), but it’s one of the most expressive languages on the market today.
It’s satire, pointing the cognitive dissonance that allows people to recognize that fumes are deadly but never question the fact that our entire “modern” concept of city planning is built around constantly being in and around the machines that produce these fumes 24/7.
My preferred variation of this is to make it an open question that leaves them in the position of authority, and assumes that they made a deliberate decision.
For example, instead of "Why aren't you using StandardLib that does 90% of this?", I would try "Could this be achieved with StandardLib? Seems like it would cover 90% of this".
As with all things, there’s a trade off: how much do you value the [convenience/ecosystem/insert other thing that proprietary system offers you] compared to the ongoing cost - monetarily but also in terms of privacy, market manipulation, environmental impact, etc. of supporting and relying on the proprietary system.
You can’t do your work without connecting to Exchange because Microsoft has leveraged decades of monopolistic gains to make Outlook the default option for any “serious” business, and has invested even further in making inconvenient (or soon impossible) to connect to Exchange from outside their sanctioned walled gardens. Demanding that Linux solve that for you is akin to demanding that the person commuting on bike undo a century of automotive-centric urban expansion in the US so that they don’t interrupt your commute. It’s not their fault they can’t solve the problem and it doesn’t help anyone to get mad at them for doing their best to behave rationally in a system stacked to only serve the 1%’s corporate interests.
The most obvious cost of detached homes is the completely unsustainable amounts of infrastructure required to maintain them. Roads, sewage, electric, etc.
It’s a well documented fact that suburbs of sprawling suburban homes are bankrupting towns/cities all across America and only the densely built downtown cores are keeping these cities afloat because the tax revenue of dense mixed-use areas is substantially higher than the cost of maintaining the infrastructure for these places. Check out Strong Towns if you’d like to know more and see the studies showing all this.
I switched from Zsh to Nushell almost two years ago and I have never looked back. If you need POSIX compliance, Nushell is a no go. But it sounds like your real problem was just that Zsh was familiar whereas fish was not. Nushell strikes the perfect balance of offering the commands you’re used to but letting everything just make intuitive sense. Plus, its help command is so far above and beyond other shells. I rarely need to open the Nushell docs (even though they’re really good), and I never have to go the community (even though it’s awesome), because I can figure pretty much everything out just from interacting help within the terminal.
For anyone interested in learning more about bloom filters, this is a technical but extremely accessible and easy to follow introduction to them, including some excellent interactive visualizations: https://samwho.dev/bloom-filters/
More specifically, he argued (and the recent and upcoming releases of most major frameworks agree) that rendering most content on the server with islands of client-side interactivity is the future.
That’s not necessarily a huge revelation, but the big difference from what people have been doing with PHP for decades is the level of integration and simplicity in mixing server-side and client-side code seamlessly so that a dev can choose the appropriate thing in each context and not have to go through a lot of effort when requirements change or scaling becomes an issue. I would say that this represents a new level of maturity in the “modern” web frameworks where devs can choose the right technology for every problem to serve their users best.
Unfortunately, as much as I hate to admit it as someone who has left Chromium behind personally, Chromium is kind of the only choice. I think people outside the browser implementation world underestimate the sheer scale and complexity of the modern browser stack and what goes into maintaining compatibility with web standards, much less advancing them.
We've reached the point where Chromium is essentially the de-facto web standard because Chromium engineers do the lions' share of feature testing and development, because Chromium receives the lions' share of funding.
Igalia, an OSS consultancy that does a lot of fairly-funded independent browser development, has lots of material about this. For example, the recent chat between Igalia members and someone from Open Web Advocacy about what to do if the anitrust ruling against Google jeopardize's Chromium's funding, and the options are pretty dire.
Edit: After reading the article, I think this is a really good sign. Bringing together the immediate stakeholders in Chromium's development and funding bodes well for the possibility of stewarding Chromium in a less Google-dependent, profit-motivated, ad-centric direction. There's unfortunately a lot of uncertainty about how this will all shake out, but it's possible that Chromium could become a truly independent project and move back in the direction of user value instead of user-hostile shareholder value.