• I put the types first in the file, sorted by importance
• then the public free functions
• then the impl blocks, sorted by importance, also. Usually, display impls and similar end up being at the end
• then the private free functions (helpers)

The idea is that I can see all the types in one glance, then I look at the rest.

Nope, my webpages are not just nested divs. I use nav, main, form, select, etc to name a few. I actually use very few JS. It's mainly for communication with the server when I need AJAX to retrieve data.

This is especially true for steam... what a crappy app

I have a degree in philosophy (and no other diploma) and I make $200k/year as a senior developer. The degree does not really matter.

While you're at it, with sum types, you can replace this stupid nil with an optional type. Also, you can replace the stupid error handling with an either/result type. Then you can add a keyword to return early if it's left/err. Then you have Swift or Rust.

You import from whatever packages you want, then you type your code. No need to create a whole project with a ton of shenanigans, a single file just works.

I didn't even know there were a survey (and I've used Rust professionnaly for years)

I honestly try and read Go news from time to time, with an open mind, but the amount of terrible footguns is astounding, especially when the language is marketed as "simple" and easy for beginner to grasp. I would pick C# or Java over it anytime.

Uh, not really? It's quite average compared to a complete inference like in Haskell and the likes.

This comment has most likely been written by a human.

Fair point. I've experienced that in big corps, so I now you're right. For example, we would lose a bunch of time because the PCs didn't have enough memory, but they couldn't get us more RAM sticks, because of the bureaucracy, it could take 2 years or so.

In most countries, a license for a year is worth less than a day of service...