I recently tried to get Go running on a Windows PC and was surprised at how immature the ecosystem is for that configuration. The thing that seemingly everyone uses for hotreloading (Air) can't be configured to support Windows and Linux at the same time. Console output from the application in question was also completely missing, which admittedly, they fixed as soon as I created a bug report and repro project.

I want to use Go for some low-cost projects hosted on VPS's but the dev experience isn't quite there yet.

I wouldn't say "everyone" uses Air. I had never even heard of it, despite frequently developing in Go for close to a decade at this point. Modd is quite nice: https://github.com/cortesi/modd

But, why couldn't you just use WSL? It is one of the main selling points of using Windows as a developer these days.

That's a great point!

In situations like this, I try to focus on whether the other person understood what was being communicated rather than splitting hairs. In this case, I don't think anyone would be confused.

Probably best to just fix the spelling.

That's what you get when you don't use AI to write an article :p

They better ban password protected zip files too!

They will when they can.

I'm glad that he is raising the flag after the devs failed to take it seriously. Evolution is going to have to do PR damage control soon and talk about how they're changing things to avoid this in the future.

Be careful with this. Each project has different practices which could lead to false positives and false negatives. You may also create the wrong incentives, depending on how you measure and report things.

it seems worthwhile to only mention it as a sidenote rather than a negative score

This sort of slogan says nothing about what actually makes it worth looking into.

What more do you need than "written in Rust"?

I wonder if you could track the usage of features known to be used for fingerprinting and disable the functionality if enough are used. I assume that most sites using advanced fingerprinting like this are also the kind that would remove it quickly if it causes the site to break.

tor tries to do this by offering different "safety" levels that the user can choose between

some browsers try to randomize fignerprintable parameters but that's easy to detect

I've found that the best you can do is complain about "process overhead" and hope someone helps you.

re: PanGui, it seems nice but the fact that they don't even have "accessibility" in their docs means it really shouldn't become widely used until they address that. It would be a big step backwards and one that is unacceptable in these modern times.

Unfortunately, the way they've designed it without accessibility in mind from the start means it's unlikely ever to be anything other than an after thought.