Here's a smaller sample size (2417 people at the time of writing) but all you need to do is fill in your details on the website: https://www.gamingonlinux.com/users/statistics/

X is at 66% and Wayland is at 33% for GamingOnLinux.

On Arch, I use ffmpegthumbnailer to accomplish this.

Kickass Women isn't going to see this comment because this user is from lemmy.world, which has blocked my instance.

Here's why.

Because I like the 2-clause BSD license. I am not a fan of “copyleft” or forcing obligations on people in general. I want my software to be available for anyone who wants to use it.

The reasons are made clear on their roadmap.

The GTK3 port is done, and now they need to finalize the new extension API and improve their color space support (particularly CMYK). It would be nice if Wayland had a color management protocol extension standardized by then, but I don't think it's a blocker.

I wonder if the same is going to be true of Thunderbird. Thunderbird actually requires you use Mercurial to contribute at all, rather than managing both git and Mercurial.

That being said...it's kind of odd to me how swiftly Mozilla of all companies/orgs is to embrace a code forge hosted by Microsoft for their main software. Surreal, even.

This is the original developer/maintainer of Sway and Wlroots' opinion on NVIDIA with regard to Wayland. This doesn't seem like an unfair opinion to me. Gamescope breaks regularly due to bugs in NVIDIA's proprietary driver; even if they know what the issue is, they can't send patches to fix it because it's proprietary. The best they can do is open a bug and beg them to fix it, which is what they do. If there's an issue on Intel or AMD, they can just send patches upstream to Mesa, and I would guess they do.

Thankfully, with the heavy active development of NVK, this might change in a few years.

Mind you, I've actually had a better experience on KDE Wayland than Xorg. Categorically...with the exception of Steam. While the games themselves play fine, the client is very glitchy. But it's a small price to pay for all the other nonsense I've had to deal with on GNOME/KDE X11.

Windows users have been asking for HEVC support for years: https://bugzilla.mozilla.org/show_bug.cgi?id=1332136

7 years ago, this was the answer:

Mozilla currently has no plans to support H.265. Our focus will be on AV1.

The reason we won't support H265 has nothing to do with the difficulty in finding a decoder, or that a decoder source code is released under GPL. Those are trivial matters.

We will not support h265 video while its patent encumbered.

BTW, even today vp9 provides better results than H265.

The conversation changed to, "Firefox could at least do hardware decode support without worrying about patents, right?"

My guess is they're doing this because Chrome added HEVC hardware decoding support last year.

They do say that:

Usually combined with the kernel Linux, GNU forms the backbone of the Internet and powers millions of servers, desktops, and embedded computing devices.

Hell no, no way I’d trust Google with my code. Personal or otherwise.

Ditto. But at the risk of playing devil's advocate, if you were writing free software code you were going to stick on a code forge somewhere anyway, would you still be against it?

Are there Google services that only work in Chrome? I don't use any of them, so I don't know. I do know Google is generally less annoying than Microsoft in that department.

Google et al. run crawlers primarily to populate their search engines. This is a net positive for those whose sites get scraped, because when they appear in a search engine they get more traffic, more page views, more ad revenue.

This is not necessarily true. Google's instant answers are designed to use the content from websites to answer searcher's questions without actually leading them to the website. Whether you're trying to find the definition for the word, the year a movie came out, or a recipe, Google will take the information they've scraped from a website and present it on their page with a link to the website. Their hope is that the information will be useful enough that the searcher never needs to leave the search engine.

This might be useful for searchers, but it doesn't help the sites much. This is one of the reasons news companies attempted to take action against Google a few years ago. I think a search engine should provide some useful utilities, but not try to replace the sites they're ostensibly attempting to connect users to. Not all search engines are like this, but Google is.

I wrote a fairly detailed spec for some software and told it what dependencies to use, what it should do, and what command-line options it should use. The base was a decent starting point, but after several hours of back-and-forth, after actually reading the code, I realized it had completely misinterpreted my spec somehow and implemented a similar feature in a completely broken way, as well as making a few mistakes/redundancies elsewhere. I tried to coach it to fix these issues, but it just couldn't cope.

I spent about 3 hours getting this base code generated, and about 5 hours re-writing it and implementing the features properly. The reason I turned to ChatGPT is because I needed this software written by the end of the day, and I didn't have time to read all the different docs for the dependencies I needed to use to write it. It likely would have taken me at least 2 days to write this program myself. It was an interesting learning experience, but my only ChatGPT usage in the future is likely to be with individual code blocks.

You really need to pay attention if you're using LLMs to generate code. I've found it usually gets at least one thing wrong, and sometimes multiple things horribly wrong. Don't rely on it; look for other sources to corroborate all of its explanations. Additionally, please do not feed proprietary, copyrighted code into ChatGPT. The software I was writing was released under a free license. OpenAI will use it as training data unless you use their API and opt out of it. ChatGPT isn't really a tool; it's a service which is using you as much as you're using it.

but browser should not crash what ever some website does.

Sometimes crashing would be better than trying to beat wonky code into shape: https://samy.pl/myspace/tech.html

3. Sweet! Now we can do javascript with single quotes. However, myspace strips out the word "javascript" from ANYWHERE. To get around this, some browsers will actually interpret "java\nscript" as "javascript" (that's javascript). Example:

But on principle I agree. I can't say whether Google Images works or not on my Firefox browser, because I'm using Mojeek.