No, they impose restrictions on your redistribution of the program. (And derivative works)

Which is why it's always been silly to present something like the GPL as an EULA in installers, for example.

Maybe also limit the size/scope of external contributions (only small bug fixes allowed for your first few PRs)

You'd be just looking at both files, side by side, to make sure nothing was lost in translation or newly introduced.

10 engineers each reviewing 5,000 LoC a day for 20 days can do it.

And that is being highly conservative with the estimate. A good chunk of the the code is probably highly trivial boilerplate one can easily skim over in minutes.

Widevine is legitimately a “gate”, but realistically it only stops 4K playback on Netflix, Disney and a few other streaming sites. And it's not super relevant considering that Zen has gathered 10M users without it.

I thought you were owned by Mozilla? A corporation that has over half a billion dollars in yearly revenue? If they decided to allocate zero funding to you, wouldn't it be vastly more effective to start some sort of campaign/movement (either internal or external) to get that funding back, or to entirely fork and leave Mozilla to be your own independent project, than to ask for random donations?

A minor piece of feedback, though: might be just me, not sure if anyone else has this pavlovian conditioning, but seeing the black banner/bar on top with the YC logo/color below and HN background color immediately makes me think someone passed away.

- Arguably the dock, though it's probably contentious - Ubiquitous instant search (e.g. Spotlight) - Gesture-based automatic tiling of windows to left/right side of the screen, tiling presets - Smooth scrolling, either via scroll wheel or trackpad - Gesture-based multi tasking, etc - Virtual desktops/multiple workspaces - Autosave - Folder stacks, grouping of items in file lists - Tabbed windows - Full-screen mode - Separate system-wide light and dark modes - Enhanced IME input for non-latin languages - App stores, automatic updating - Automatic backup, file versioning - Compositing Window Managers (Quartz, Compiz, DWM, modern Wayland compositors...) - The "sources bar" UI pattern - Centralized notification centers - Stack view controlelr style navigation for settings (back/forward buttons) - Multi device clipboard synchronization - Other handoff features - Many accessibility features - The many iteration of Widgets - Installable web apps - Virtual printers ("print to PDF") - Autocomplete/autocorrect - PIP video playback - Tags/Labels - File proxies/"representations" - Built-in clipboard management - Wiggle the mouse to find the pointer

None of these can be said to be at their final/"perfect" form today, and there are hundreds if not thousand of papercuts and refinements that can be made.

The real issue is probably due to management misunderstanding designer's jobs, and allocating them incorrectly. The focus should be more on the interactions and behaviors than necessarily on the visuals.

I think they realized that shipping the features out of sync meant nobody could use them until all browsers adopted them, which took years, so now they coordinate