Wait, 4 attempts? I think I only heard about 1.

What if the new elected upper house worked similarly to the Australian Senate? Our House of Representatives is the same as your House of Commons (except that it uses IRV instead of the undemocratic FPTP) with single-winner districts. But the Senate uses a proportional system (STV) electing 6 Senators per state for twice the amount of time an MP is elected for. So they’re relatively less concerned about the day-to-day shifting polls than MPs are, and you get a result that’s much more representative of what the people actually want.

In the UK context, it might be easier to sell PR in an entirely new house than it would be to update how the Commons is elected.

And currently the house of Lords is a bunch of old geezers that don’t know anything about anything

Look, I’m not British and frankly do think the Lords is silly. But I can name three members of the House of Lords, and 2 of them at least demonstrably deserve to be there on political merit, whether or not you agree with how they vote. I have no idea what the ratio is across the whole of the Lords, but at least not all of them “don’t know anything about anything”.

Don’t get me wrong, I prefer the Australian model where Senators are elected with a proportional system and serve for terms twice as long as lower house MPs. And the Canadian model of “lifetime” (subject to retirement age) appointments also has merit. It’s just that not ever single Lord is completely undeserving.

The three Lords that I’m familiar with, fwiw, are David Cameron, David Willetts, and Andrew Lloyd Webber.

Not really. Wikipedia is not a democracy. It would only take a handful of dedicated zionists to kick up a fuss to create the debate. The fact that it arrived at the right conclusion is a testament to Wikipedia’s editorial policies.

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.

Okay but they often don’t give users what they want

You should see the state of Firefox on iPad OS. I started using it earlier this year after they finally rolled out support for multiple windows—a feature Safari added in 2019 and Chrome had only a few months later.

Nice that they finally have this feature, but the browser itself is nearly unusable. It stutters constantly and freezes, locks up, or force reloads with some regularity. In a way that Chrome and Edge (and I assume Safari, though I have never really used that) never do.

Or on desktop OSes, a website I frequented around 2016–2018 used the column-span CSS property, which Firefox didn’t get around to implementing until December 2019.

It’s been very clear for some time that, whether it’s because they stretch themselves too thin or some other reason, Mozilla has been failing to continue to deliver an excellent product for their users.

Olive oil is a deeply important cultural touchstone for Palestinians, according to a post I saw a day or two ago.

As for all those links. Absolutely irrelevant to the conversation at hand, which is about you violating instance-wide rules about respect.

You’ll note I did not report comments I merely disagreed with. I reported the ones where you were clearly violating your own instance’s rules by failing to be respectful with your interlocutor.

Maccas HQ should take the guy’s franchise off of him, then. They did it near me to a guy whose only crime was supporting the local community more than extracting maximum profit, surely making a political endorsement that HQ doesn’t agree with should be grounds for the same. Right‽

Yup. Clear violation of the rules.

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.

It means slightly better than—but just slightly—America’s Democrats.

Though fyi in Australia we spell it Labor. It’s labour in any other context, but our political party is Labor.

Do you guys here ticking?

Ron, Ron, Ron Weasley

The only country whose opinion should matter here is Taiwan. If and when they decide they want to be recognised officially, they should be. Not before, and not after.

I thought it was a rather simple analogue, but I guess it was too complicated for some?

I said nothing about JavaScript or Python or any other language with my 1/3 example. I wasn’t even talking about binary. It was an example of something that might be problematic if you added numbers in an imprecise way in decimal, the same way binary floating point fails to accurately represent 1/10 + 1/5 from the OP.