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.
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.
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.
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.
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.
Definitely more accurate however it's UX is awful and doesn't do a good job of prioritizing issues. It sucks that you basically have to install a screen reader app to get the most accurate idea of how screen readers see your site.
Sounds like they were caching it since they could execute it before getting the response. The difference is that they wanted to avoid the situation where they execute stale code that the server never would've served. So they can execute the stale code while waiting for the response then either toss the result or continue on with it once they determine if the server response changed.
Instruction manuals make it easy to game it but people can still game it without an instruction manual. This seems similar to the idea of security through obscurity. The same argument could be made about linux, right?
Letting people see into it could make it easier for people to learn how to game the system but it could also make the system harder to game in the first place.
You can also use the ifdef-loader module to have code that is conditionally included in the output build, allowing you to have debug code not make it into prod builds. The `rc-dev-` license keys being a good example of that.
The vscode extension builds are including your full source code and node_modules directory which makes it 21 mb. You can reduce the size (and potentially keep your code less easily reversable) by excluding those from the final package
Seems like a cool thing, I'm definitely interested as my work provides us with an API key to use. However I can't find anywhere that lists all the functionality offered. Maybe I'm missing something? It might be premature to launch the app before listing what it does.