> WhatsApp for Windows was originally an Electron app, and it was eventually replaced with UWP after years of investment. Four years later, WhatsApp is going back to WebView2, abandoning the original WinUI/UWP native idea.
> My understanding is that the recent layoffs at Mark Zuckerberg-headed Meta likely disbanded the entire team behind the native WhatsApp. I don’t see any other reason why Meta would abandon its native app for Windows. Meta will save costs by maintaining the web app codebase on Windows, but you’re going to hate the experience.
Giving them more time won't change much if they have resigned from devs in order to save some money.
In the article [0] (also posted on HackerNews [1]) they share a link to page, which is a guide how to run new Affinity (v3) using Wine/Bottles combo [2].
> The bundled Pop!Shop app store is the notable turd in the pool, but it's optional.
I agree. It’s the second most irritating thing. I am glad that I have written my tiny `update` bash script, which takes care of installing all updates (apt, flatpack, brew, etc.) without touching "app store".
I believe the bundled Pop!_Shop originates from Elementary OS and suffers from issues with proper background job processing. I find all those “store” apps for GNOME to be poorly written, often displaying incorrect numbers of updates, and generally slow.
I have been using Pop!_OS on my old Intel-based Dell laptop for over 5 years. Now, I'm alternating between my M1-powered Mac and Pop!_OS as my daily driver. Before, I used Ubuntu for over 10 years and tested various distributions.
Pop!_OS is probably the best Ubuntu/Debian derivative I've used. It's buttery smooth for everything I need it to be. I haven’t encountered any bugs or major problems that are strictly related to Pop!_OS. It feels like Ubuntu, without slow Snaps (Pop!_OS is Flatpak-centered), Canonical ads (Ubuntu Pro, MicroK8s...), and with a slightly modified GNOME desktop environment.
If I had to find the worst thing about Pop!_OS, it's a negligible issue stemming from muscle memory after using macOS. The Super+Left/Right Arrow keys on Pop!_OS are used to switch between applications, while on macOS they are meant to move the text cursor to the start or end of a word. I haven't found the option to disable it yet.
> In Python’s uv, the pyproject.toml has separate sections for dev and prod dependencies.
If you want, you can have multiple ".mod" files and set "-modifle=dev-env.mod" every time you run "go" binary with "run" or "build" command. For example, you can take what @mseepgood mentioned:
> go tool -modfile=tools.mod mytool
Plus, in last versions of the Go we have workspaces [0][1]. It is yet another way to easily switch between various environments or having isolated modules in the monorepo.
This Vimcast (http://vimcasts.org/episodes/converting-markdown-to-structur...) recording is an example of a quite complex macro for converting (a specific file's) markdown to HTML. At the beginning of the video you see that they save the macro to the "a" register. You can record macros of similar complexity to each of the other letters of the alphabet, to get some idea of the maximum complexity (though I tend to stick to about 3 or less in a single session).
Being the Debian-based distro that's willing to bundle proprietary drivers. For someone like me who doesn't want to deal with driver issues, Ubuntu generally* just works out of the box.
Probably, but that's exactly the kind of research and juggling that I'm trying to avoid. The Ubuntu installer has just has a checkbox that says "please give me proprietary drivers".
Also, to be clear, my asterisk is that Nvidia drivers seem to be no easier on Ubuntu than on Debian (you have to seek them out), and for me they've often caused problems once installed.
The most stable solution to Nvidia drivers on Linux has always been "download the deb when you set it up, hope it was a "good" release, and forget about it for a year until something requires a newer driver.
It always felt like going through the distro's included stuff was a waste of time.
I like GNOME because of its design choices in 3.x+. I really appreciate the aforementioned large controls, title bars (often integrated as toolbar menus) and resignation of menus in favour of dedicated pop-overs. IMHO it is a step forward in providing simpler UI, but yes - it has some drawbacks too.
Ironically, I see the designers of macOS built-in applications (e.g. Finder.app or System Settings.app) are following their GNOME counterparts rather than the other way around. Since Maverick, Apple has lagged behind in terms of UI innovation and it is the GNOME designers, who are pushing forward with new ideas. The addition of a header bar in Finder.app and Nautilus made them much more usable for me [0] [1]. The same can be said for System Settings.app [2], which now follows the design and layout of the GNOME Control Center. GNOME has been a copycat for many years, its UI was inspired by macOS/iOS, but now the roles are reversed.
The missing piece of the puzzle is searchability, which GNOME 3.x+ lacks and which GNOME excelled at in the days of Unity DE. Hopefully GNOME 40+ will bring some improvements in this area.
> I really appreciate the aforementioned large controls, title bars (often integrated as toolbar menus) and resignation of menus in favour of dedicated pop-overs.
Heh, those are all on my list of things I hate about Gnome. Funny how different people can be.
> WhatsApp for Windows was originally an Electron app, and it was eventually replaced with UWP after years of investment. Four years later, WhatsApp is going back to WebView2, abandoning the original WinUI/UWP native idea.
> My understanding is that the recent layoffs at Mark Zuckerberg-headed Meta likely disbanded the entire team behind the native WhatsApp. I don’t see any other reason why Meta would abandon its native app for Windows. Meta will save costs by maintaining the web app codebase on Windows, but you’re going to hate the experience.
Giving them more time won't change much if they have resigned from devs in order to save some money.