I always see these kind of comments, that many sites don't work in Firefox while they do in Chrome. When I encounter a broken site I always also check it in Chrome but the times where it is actually a browser's fault is like once a year. Usually it is some blocking of cookies or something that I have enabled in Firefox. Even sites from Google which everyone seems to describe that they are specifically made to work only in Chrome I never had issues with.
Yes I agree, there was a time where it was worse and FF just did not have the same support coverage for Browser APIs etc, but now if I encounter a problem in FF I tend toward blaming the website developer for ensuring it works ok.
Firefox on Linux has much more problems than Firefox on Windows, mostly because it does not support many GPUs, so it frequently disables WebGL or it cannot use hardware support for playing videos, even now, in 2026. This breaks many sites.
Unlike Firefox, the Linux versions of Vivaldi/Chromium/Chrome do not appear to have any deficiencies in comparison with their Windows versions.
That has not been my experience of Firefox on Linux.
Whenever I encounter a broken site, it's because I blocked some advertising scripts and the whole thing fell apart with a slew of JavaScript errors. I'm quite happy to avoid such shoddy sites.
For the kind of things needed by Firefox, the Linux APIs have been stable for decades.
The problem is not stability, but the fact that there are multiple APIs, and it is unknown which of them will be available on the user system, so a browser may need to support all of them.
For instance, for video decoding on a GPU, the Linux APIs differ depending on the GPU vendor, unless you use Vulkan, but Vulkan video decoding is not available in old computers. Even so, Firefox could have used some higher-level API that takes care of the low-level GPU-dependent details (e.g. ffmpeg).
More baffling is the failure of Firefox to use OpenGL or Vulkan for implementing WebGL, depending on the GPU vendor, because at least the OpenGL API has not changed in a very long time. I have no idea which is the reason (because Firefox does not provide adequate error messages), unless they depend on some vendor-specific OpenGL extensions. I use an NVIDIA GPU, on which I cannot enable WebGL in Firefox, despite the fact that WebGL works fine in Vivaldi and Chromium/Chrome and I use a very great number of OpenGL and Vulkan applications, including some written by myself, all of which work perfectly, with no problems whatsoever.
The usual explanation by Firefox team is that the drivers are not uniformly compliant and/or working well. There had been progress, though.
For your specific system, you can open about:support and search the page for the word "Blocklisted" - that section of the page includes failure codes that can be then passed to web search (or interpreted by name).
I don't know all the details of what works well or not, but the Chrome team logically should have more manpower to implement workarounds for driver problems, and Vivaldi reuses the engine.
Speaking of the other applications though, most of them don't have to use the dma-buf subsystem, to embed hardware rendered content inside a "regular" application. That imposes a certain limitation on the driver capabilities.
It's crazy, but in 2026, websites still check the user agent string and will simply refuse to work if it's not one that they like. Financial and enterprise software is the worst for this. It's one of the reasons Vivaldi switched to simply copying the Chrome user agent string instead of their own.
Some sites also simply to not test their stuff on Firefox since it has such a small market share, and Firefox _does_ have minor incompatibilities that only tend to show up when using overly fancy Javascript or CSS frameworks. (But this is far less common than the first point above.)
I have never owned a touchscreen laptop and I agree with most of the criticism in comments here against it. But after just briefly using one from my father I have to say there is some thing in our brain that makes it kinda more satisfying, if that is the right word, to touch on things that appear on a screen. Even as a power user being used to just using keyboard most of the time, after 10 minutes with a touchscreen my mind prefers to touch on screen instead of touchpad.
I agree with your point about Google being more stable company then the rest so the decision probably makes sense. But there was a study done by multiple news companies in Czechia by asking about news topics and Gemini was consistently the worst in citations and straight up being incorrect (76% of its answers had "issues", I don't have exact issues specification).
I have used MAUI at my previous job to build 3 different apps, used only on mobile (Android and iOS). I don't know why many people dislike XAML, to me it felt natural to use it for UI, I researched flutter and liked MAUI/XAML more. Although the development loop felt smoother with flutter. What I didn't like was the constant bugs, with each new version that I was eager to update to fix current issues, something new appeared. After spending countless hours searching through the projects GitHub, I am under the impression that there aren't much resources dedicated to MAUI development from Microsoft, the project is carried forward by few employees and volunteers. If I would start another project I would seriously look into Avalonia. But I always was a backend guy so now at my current job I do server backend development in C# and couldn't be happier.
Did I really just waited couple of seconds on 2 different loading screens to see a small blog post that is more of an advertisement to some AI tool? Also the analogy of something that tries to stay as open as possible (self-hosting) needing its "iPhone" moment to be locked into single ecosystem doesn't really work for me.
Holy moly, you must have very different life than most people I guess. I am from the younger generation which supposedly avoids making old-style phone calls as much as possible and I don't think I know anyone who has made less than 100 calls in the last decade.
I think those very total attention expected during phone calls, and the speed at which it happens, contributes to a higher level of anxiety compared to texting. The younger generation hate these elevated stresses and prefer more async communication
This is better indeed, but from recollection last time I tried this.. I think that still requires a full OpenJDK installation and I believe those `sdkmanager` commands install multiple GB of tools sadly.
I followed the same logic when deciding what kind of blinds control to choose building my house few weeks ago. Now I am in the planning of adding automation to it. Did you use Shelly Plus 2PM or are there any cheaper options to choose from (they seem to start at 30€ in my country shops)? Did they fit nicely in the wall switch socket?
I initially got the Shelly 2.5, now discontinued. The one that failed was changed to a 2 PM which is 31€ on Amazon in France (you could probably get better deals (I just checked with Amazon Germany and they are at 25€).
I mounted them right next to the roller (in the roller enclosure) and if I did not have that possibility, I would have done it close to the ground to have good access. I do not have a socket per see, rather a small switch on the wall not inside the wall, this is not permitted where I am)
I had a look at cheaper solutions in the past but gave up - I do not have a lot of rollers so the cost difference is likely to be minimal. I like the fact that they work well and it is really a kind of mount-and-forget kind of setup.
reply