> 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.
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.
Isn't there `xsel` or `xclip` installed instead [0]? These two commands are commonly used on the Linux boxes and they support pipes too. For example, the xclip is used by the original password-store implementation [1].
On [2] you might find the aliases to pbutil for X11-based Linuxes.
[0]: If not, why not run apt-get command to install one of them, like xclip?
Maybe it is unpopular opinion, but I think the go-compiler in `go build`, `go install`, `go test` commands should check for all unhanded errors and not compile the program if there are any.
It happens in personal projects, small teams and big ones too. The linter errors are too often ignored by developers. Also, it should help embrace in developer the need to explicitly name some error to be ignored.
Uh, that's interesting, but it does not work for me :(
AFAIK, VO+Command+Return can be used to select multiple things, not to click. For example, in the file viewer (Finder.app, similar to Nautilus/explorer.exe), it is similar to pressing Control (win/linux) and the left mouse button when the cursor is over a file to add it to the selection.
Edit: To open a page in a new tab in a Firefox with stock VoiceOver, I need to press VO+Shift+M to open context menu (aka right-click menu), and then select an option from the list (by greping, using arrows etc.).
> Accessibility support is a matter of priorities for a given project.
It is painful that some managers, architects or developers might think this way. Accessibility is not just for disabled people, such as the blind or those who have lost a limb. In the kitchen, for example, it is great to have push to open drawers (e.g. based on IKEA's EXCEPTIONELL [0]). If your hands are dirty, you can still open the kitchen drawer without getting anything else dirty. And this is just one example of accessibility.
Personally, I see screen readers as an additional tool (like Copilot or ChatGPT) to be used on a daily basis by keyboard users.
Screen readers can also help you, even if you are sighted. For example, with a ShortCat.app [1] I have a system-wide ace jump [2] with a command list. I don't have to use the mouse to move the cursor - I have a keyboard for that. But in applications that are not compatible with screen readers, you can only choose "close", "minimise", "maximise" buttons, and the first option - close - is the best for such an application (e.g. Sublime Text).
In other cases, SR/SA will read the text for you. If you are too tired to read, or your hands are occupied with a sandwich or utensils, you can use SR to read an article or paragraph for you.
No, at least not in VoiceOver, which I use. In my experience, screen readers/assistants don't mimic the left/middle/right click of the mouse [0]. You often get two options: left click and double click [1]. There is also a right-click menu (control space), but unless it is based on a system-native UI, it is likely to be unusable for SR.
[0]: It is even easier to not use a mouse, when you are using an assistant. With a keyboard and VO you can resize, drag and drop and do many more activities.
How the multiplayer mode would look like? Do you think about competing against the other real player? Or maybe collaborating with some friend?
I am asking, because I think I haven't seen the multiplayer support in any railroad/transport-tycoon game. I remember in Railroad Tycoon 2 and then in Sid Meier's Railroads [0] we could play against NPC. Same as us, NPC is establishing a company and we may buy all his stocks to win.
> 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.