The vast majority of my time on Reddit was on smaller communities where that wasn’t true. The experience on Reddit of the defaults compared to more niche communities was like night and day.

I don’t even think that’s remotely true.

I’ve seen two cases that actually directly impacted my ability to use Firefox. I can only presume there are many more. Those being supporting the column-span CSS property (available since 2010 in other browsers with vendor prefix, and early 2016 without, while being late 2019 for FF) and supporting iPad OS’s multi-window functionality (introduced mid 2019, Firefox has had it for just a handful of months now). I have first hand experience telling me very directly that this is true.

There’s also been a lot of talk about Firefox’s lack of support for PWAs. I’ve not experienced that myself to be able to comment more than to say I’ve noted others have complaints.

The point is that with open source you can effectively leech off of Google for now, while still retaining the flexibility to nope out and do your own thing at any point you decide.

Considering just how severely behind they are already (as I mentioned in my other comment, they’re often 3–5 years behind other browsers in implementing new web standards or operating system features), I see anything they can do to reduce how much they need to maintain independently as a good thing. In an ideal world where they had all the funding and development power they could want I might say sticking with the completely independent Firefox would be great. But that just isn’t where they’re at today.

They wouldn’t be at the mercy of anything. That’s…how open source works. If it changes in a way that breaks things for you, don’t pull that change. At that point, if the change is drastic enough to require it, you can turn that soft fork into a hard fork and hope that Edge, Brave, Vivaldi, Opera, etc. join you; something that would significantly hamper Google’s ability to maintain their dominance of the browser engine market. That’s a choice that they simply don’t have today when being based on Firefox and Gecko means using an inferior browser platform.

Honestly I’ve been saying for some time that Mozilla’s resources would be much better spent making Firefox a soft fork of Chromium. Primarily: use the Blink browser engine and V8 JS engine, with only the changes to those that they deem absolutely necessary, and maintain a privacy-forward Chromium-based browser. Maybe try and enlist the help of Brave, Vivaldi, and other browsers that are currently Chromium but which prefer more privacy than Google offers.

It’s not zero effort, and especially as Google continues to develop Chromium with assumptions like the removal of Manifest V2 it might take some effort to maintain, but it cannot possibly be as much effort as maintaining an entire browser.

Looking at it now, the LW version of that community would be great, were it not for LW’s severe federation problems.

High school is considered primary education here. (at least by me

Ah, right. So, this terminology is actually pretty standardised and high school is secondary education, with primary school naturally being…primary education. Though there is a little ambiguity around the edges, for example:

United States: High school (usually grades 9–12 but sometimes 10–12…) is always considered secondary education; junior high school or intermediate school or middle school (6–8…or other variations) are sometimes considered secondary education.

It’s of particular note because the phrase “tertiary education” universally refers to post-school education like university or technical colleges, and it wouldn’t make sense to have tertiary education if there was no secondary.

primary education only though

Wait, yous don’t even have free secondary school? I know America has an infamously terrible tertiary education sector, but I thought high schools were publicly funded at least.

Culturally appropriate other countries’ cuisine.

How I feel is the CIA overthrew a left-leaning democratic government in my country because it threatened to close down a CIA base. That’s not tanky.

Idgi

At this point, “crypto” is its own word short for “cryptocurrency”, and not for “cryptography” in the broader sense. It’s unfortunate, but that’s how people use it.

Yeah I’m not really sure either. I get the sense that either it got better over its lifetime or over time people came around to it à la the Star Wars prequels. But I don’t really remember it. I played it a little early in its life but don’t remember anything about it.

Using anything about America to justify Russia’s war of aggression in Ukraine is an obvious attempt to rationalise their support for something indefensible. The only involvement America has in this particular war is helping the victim of an invasion defend themselves.

I agree in general, but

Maybe I’m over simplifying it though, I don’t know how their org operates.

This is exactly why just sticking to the 90 day standard is better. For the supposed security researcher it’s a CYA move at worst.

90 days is just the standard timeframe for responsible disclosure. And normally that’s just a baseline with additional time being given if there’s genuine communication going on and signs they’re addressing the problem.

Hexbear doesn’t care about the answer to that question. They support modern-day Russia which doesn’t have any pretense of socialism. Their stance is first and foremost anti-American. Anything else is window dressing.

I had a read over the rest of that review. Damn it was a good read. And sadly very, painfully accurate to my experience.

Yup absolutely. I mentioned web APIs because that’s what I’ve got the most experience with, but .h files, class library public interfaces, and any other time users who are not the implementor of the functionality might want to call it, the code they’ll be interacting with should be tailored to be good to interact with.

If the doco we’re talking about is specifically an API reference, then the documentation should be written first. Generate code stubs (can be as little as an interface, or include some basic actual code such as validating required properties are included, if you can get that code working purely with a generated template). Then write your actual functional implementation implementing those stubs.

That way you can regenerate when you change the doco without overriding your implementation, but you are still forced to think about the user (as in the programmer implementing your API) experience first and foremost, rather than the often more haphazard result you can get if you write code first.

For example, if writing a web API, write documentation in something like OpenAPI and generate stubs using Swagger.