Am I missing something here? I understand the "The IAB loves tracking users." part of the title, but where is the part about "But it hates users tracking them."? Based on the title, I would have expected an exception in their standard for themselves, or a story about how their own user tracking technology was used against them.
However, there is none of that. Just that the IAB does not want to make it easier for users to escape their tracking (which, given their purpose, is unfortunately entirely expected). What justifies "But it hates users tracking them."?
> I recently discovered a big cache - in terms of file number, 6000 files - of basically every edit I did in the last 6 months in VS Code - called Local History.
Isn't this a feature? I wouldn't want my editor to remove my local history without me knowing. I frequently use this local history (in Intellij), for whatever reason (it's easier than git, the project doesn't have version control, I haven't committed yet, ...)
> These apps [single page web applications] also tend to feel snappier because page loads are not required for every request.
This isn't my experience at all, especially when network conditions are not great. The browsers has error handling and a progress bar. Single page web applications often have bad or no error handling and you have no idea if the request failed, the code errored or something else went wrong. You need to refresh the whole page if something goes wrong, which results in having to load a ton of JS every again, negating all possible savings in time and data usage.
> Visual Mind is an AI engine specifically designed for understanding and scoring visual appearance of a website. Visual Mind has analyzed over a million websites to achieve an accuracy rate of over 97%.
How does accuracy work in a project like this, where the result is subjective?
> The Unicorn tier is for large companies or companies that would like to have a reciprocal relationship with our foundation. If you need special guarantees, indemnities or require us to sign your contract for a data license, please select this tier. If you have another creative idea you would like to propose, please also select the unicorn tier.
> For any of these cases, please detail your request in the company information field and we will work with you to fit your company's mythical situation. We will also find an appropriate monthly support amount to our non-profit foundation of $1500 or more per month. Please always consider enabling the growth of our non-profit foundation and the continuous growth of our metadata!
A lot of EE folks I've met _think_ they are competent in software, but I'd beg to differ. Similarly, I've met plenty of CS majors who know their way round hardware.
However, I do agree with some of the other contents that the style is a little dry for a webpage.
I think it would be very useful as the "print" style for articles or blog posts, without having to pipe through pandoc: most browsers support print to pdf.
I agree with the overal sentiment, yet the examples could be better.
> Modern text editors have higher latency than 42-year-old Emacs. Text editors! What can be simpler? On each keystroke, all you have to do is update a tiny rectangular region and modern text editors can’t do that in 16ms. It’s a lot of time. A LOT. A 3D game can fill the whole screen with hundreds of thousands (!!!) of polygons in the same 16ms and also process input, recalculate the world and dynamically load/unload resources. How come?
Text is very complicated. Does your 42-year-old Emacs support Unicode? And not just accents, but whole different scripts?
I'm note sure about the EU part, because in Belgium you can mention competitors, e.g. "Darktable aims to fulfil the same need as Lightroom" is absolutely allowed, without problems. There aren't even rules specifically for mentioning competitors, it's about comparisons in general. For example, saying your product is "the best on the market" counts as a comparison, and you'll need proof to back up your statements.
I am very disappointed in Matthew Walker. In fact, if I were working in the same field as him, these findings would cast a doubt on most of his other work. The density of the errors almost makes me unsure which is worse: the errors are unintentional due to carelessness or they are deliberate to create a better sounding story. (Of course, the latter is worse as it is basically academic fraud.)
I believe there should be more books that are scientifically sound, yet accessible to most people. I thought this was one such book, but alas.
Android used to recommend to open the hamburger menu when people open the app automatically, until they have opened it once themselves.
> Upon first launch of your app, introduce the user to the navigation drawer by automatically opening it. This ensures that users know about the navigation drawer and prompts them to learn about the structure of your app by exploring its content. Continue showing the drawer upon subsequent launches until the user actively expands the navigation drawer manually. Once you know that the user understands how to open the drawer, launch the app with the navigation drawer closed.
- There an option to compress images before uploading (which is probably on by default). Not unreasonable.
- Content is deleted if you do not access Google Photos in any way during two years AND do not have a paid storage plan. Not unreasonable.
- If you use more storage than you pay for during two years, content will be deleted. Again, not unreasonable.
I really do no get the complaint here.