I’d add the language specification. It is well written and Go is a relatively small language so the spec is not difficult to digest:

https://go.dev/ref/spec

And pretty much everything from the official documentation page is a good read:

https://go.dev/doc/

Sales numbers ($) by platform would be interesting to see too.

Correct, that’s what I meant to imply in the first part of my comment. When I research new games I do that from a web browser and that’s when I care about Proton status the most so this works great for that. It does not help when using the Steam client.

I tend to do my Steam shopping in the browser and I use the ProtonDB-Peek userscript. This gives a ProtonDB status badge in the right column under the review links.

I personally welcome this decision. I am fairly happy with the current syntax and I enjoy the explicit “does what it says” nature of Go code. None of the proposed alternatives would have made error handling more robust, they were pure syntactic sugar with no nutritional value.

Saying no to multiple proposals when you feel that the status quo is better can be difficult to do and I am happy that the Go team is able to make these kinds of decisions.

This hasn’t been true for years, see the relevent Arch wiki page for example.

The Internet was already a teenager by then. It hooked up with Hypertext and the result was this brat called WWW.

My first WWW experience was trying Mosaic on a computer without an Internet connection. I knew what the Internet was, we had access through an X.25 PAD (kind of like a dial-up shell session, no direct TCP/IP) so I’d already used IRC, Usenet, FTP, Archie, Gopher etc. I also knew what hypertext was from various local help and document browser programs. So I figured out that Mosaic can display HTML documents but of course without Internet connectivity just showing some local demo pages didn’t seem all that special. But I figured it out later on…

deleted by creator

I like my 8bitdo controller but I have an older model so can’t speak for the more recent ones.

Mesa 25.0.0 Release Notes / 2025-02-19

[ 5067.696] (II) Applying OutputClass “AMDgpu” to /dev/dri/card1

Make sure that you actually have permission to that /dev/dri/card1 device. This may be arranged by udev or “video” group membership.

Regarding AMD vs Nvidia, unless you need CUDA you probably made the right choice. This sounds like a config issue and you’d probably be dealing with the same thing with Nvidia too.

To be fair the “no USB support” window was quite short. USB started becoming available to consumers around 1998-1999 and there was some level of USB support in the Linux kernel within a few months. I remember using an early USB stack written by someone else that Linus didn’t like so he rewrote it from scratch. Even the new Linus stack was in place by 1999. We got USB-2 and 3 support pretty quickly too.

deleted by creator

deleted by creator

What I see is an inexperienced developer who instead of systematically debugging the issue keeps trying random stuff hoping that it will somehow work.

Fixed formatting

Mastodon

I. Web Clients

• https://phanpy.social/
• https://elk.zone/m.webtoo.ls/public/local
• https://statuzer.com/
• https://n1k0.github.io/tooty/v2/
• https://trunks.social/
• https://pinafore.social/
• https://nicolasconstant.github.io/sengi/

II. Android apps

• Plachi
• Rodent
• Megalodon
• Trunks
• Focus App

III. iOS apps

• SoraSns
• Ivory
• Trunks
• Radiant
• Feather
• Mona
• Woolly
• Tusker
• Manny
• Ice Cubes
• Mammoth
• Feditext
• Fedigardens

Friendica

• Relatica
• Firefish
• SoraSns
• Kimis
• MissRirica