bamboo

LibreOffice is great if you don’t need perfect compatibility with Microsoft office. If you do, the only good option is, well Microsoft Office.

Microsoft office and games with anticheat are two big categories.

WebKit and Blink are extremely far diverged at this point, even though Blink was originally a fork of WebKit. Features like sandboxing and process isolation vary significantly on the backend, and feature support for web pages varies greatly. Ask any web developer if they can rely on new web features in chrome also being present in safari, they can’t.

WebKit and Blink are extremely far diverged at this point, even though Blink was originally a fork of WebKit. Features like sandboxing and process isolation vary significantly on the backend, and feature support for web pages varies greatly. Ask any web developer if they can rely on new web features in chrome also being present in safari, they can’t.

They can already do that. You can make custom clients that pretend to be the real one, it’s just against their terms of service. Spammers generally don’t care about the ToS though, so it’s just legitimate users that are affected.

You could burn it to a dvd or whatever, delete the file, and give the customer the only copy. Whether they choose to keep it or destroy it is their own choice.

My main complaint is that they officially prohibit 3rd party clients including 3rd party builds of their official ones. They also don’t have reproducible builds for their clients. It leaves the door wide open for inserting some telemetry via an update to completely bypass their otherwise good encryption and (lack of) data retention.

Safari is the browser with the second highest usage share and is not in any way based on chrome. It’s limited to Apple platforms though, so other users can’t switch without buying new devices.

The original cast-only chromecasts didn’t have ads as far as I know, but they’ve all been discontinued and replaced by the google tv chromecasts which have ads integrated throughout the interface, mostly just for streaming services, movies, etc.

I agree, and GitHub allows choosing how to merge each PR individually if you need to do something different for a specific PR. Large PRs like that are at most 1% of our total PRs, and we review those more per-commit and use a merge commit instead of a squash. By default we optimize for the other 99%.

I think the idea here is that reviewing individual commits is irrelevant if the plan is just to squash it all down. Each PR corresponds to a single change on the main branch in the end, the fact there was a main commit followed by a half size “fixed typos” and “fixed bug” commits doesn’t actually matter since it will be blown away in the end. The process results in the same clean history with good individual commits on the main branch, just as if the user squashes those commits locally before pushing it up to the code review platform.

Well squash and merge isn’t default or pushed in any way. It’s an option, and we chose to enable it ourselves because that’s what works best for us. It’s what works well for many other projects too, which is why many choose to enable it instead of the default merge commit.