johnasmith

Compose Multiplatform is an interesting framework that can render to a web canvas, including full accessibility support.

Canonical Serviços De Software Ltda.;

I'm curious, what does having control over the update process give you? Isn't it replacing one unauditable black box system for another? Are you concerned about a regression and don't want to be in the vanguard cohort?

Google has two billion lines of proprietary code, conformant to their style guides and proprietary requirements. I can't imagine they'd poison their model with non-conformant third party source.

The English translation of the (Dutch) "strandbeest" is "beach animal".

Not all John Smiths are bad, promise.

The article suggest that it was neither. That rather it was an engineering decision: the product did not have staffing to be properly maintained, and rather than staff it up, it was easier to turn it down.

Google is no such place. I've worked in several product areas, and while there is no formal one-size-fits-all process, generally engineers build products specified by PM written PRDs, often informed by UXR, designed by UX. At least for the last 12 years, it's not been a wild west of rogue engineers.

For Firefox to succeed, it has to differentiate. There are two meaningful ways it does, or will do, in the near future:

1. Mobile extensions: that's a unique value prop

2. Fight for the user: manifest v3, web environment integrity, and whatever comes next are degradations in user experience, and following a different path puts FF apart

There are build systems where this guidance isn't terribly valuable.

With Bazel for example, you typically have build files in each directory, and a test target for each test class in that build. But bazel allows you to select and run targets in a collection of directories, select targets recursively, or by a variety of other criteria. Your CI systems runs targets selected implicitly, while each build expresses the test targets explicitly.

One of the newer things I've appreciated from guava is ListenableFuture to Kotlin suspend functions interop.

That's a fine argument to make, but the article didn't.

The article conflated ad selection and search query results.

Mozilla's office in SF, pictured in the article's first photo, is literally neighbor to Google's SF office, making that a particularly apt photo and headline pair.