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

- 2 USB3-A on the front

- 2 USB2-A on the back

- 1 USB-C on the back

If you want to plug an external USB hard drive or SSD at full speed, you'll need to plug it at the front? Or use up the only USB-C port...

I suspect most joysticks sold today come with a USB-C to USB-C cable, so if you want to charge your controller you either need to plug on the back, use an adapter, or get a USB-A to USB-C cable?

Also the single USB-C port isn't Thunderbolt/USB4, and they're only including gigabit ethernet, which is disappointing but perhaps understandable if they're trying to keep it at a low price.

Anyway, these are pretty cool/unique looking! I hadn't seen curved origami like this before.

There needed to be someone willing to try going big at an organization with sufficient idle compute/data just sitting there, not a surprise it first happened at Google.

https://support.apple.com/en-gb/guide/mac-help/mchlp1008/mac

I agree that discoverability could be better, but macOS has pretty consistently had hidden power user shortcuts and modifiers, to keep the basic workflow streamlined/simple for those who don't need it.

My understanding is that Microsoft chose Go precisely to avoid having to do a full rewrite. Of all the “modern” native/AoT compiled languages (Rust, Swift, Go, Zig) Go has the most straightforward 1:1 mapping in semantics with the original TypeScript/JavaScript, so that a tool-assisted translation of the whole codebase is feasible with bug-for-bug compatibility, and minimal support/utility code.

It would be of course _possible_ to port/translate it to any language (Including Rust) but you would essentially end up implementing a small JavaScript runtime and GC, with none or very little of the safety guarantees provided by Rust. (Rust's ownership model generally favors drastically different architectures.)

If the packages are already available locally, cargo works offline.

UNIX also has a playful name (from Multics)