I think it's safe to assume that being unable to select text on this page is not unintentional, as several comments here assume, nor "ironic", but an intentional effort to demonstrate how annoying this behavior is.
I don't know why so many comments are discussing "if it's intentional troll or hypocrisy", when it takes 10 seconds to check one of the other blog posts and see if the text there is selectable :(
> In an app, undoing that is pretty much impossible (or at least, above my pay grade).
In my experience it is above the average user's pay grade to work around it in a browser too. Even power users will probably give up if the usual ways don't work out (holding alt, browser extension, reader mode). The power-est of users might glimpse at the inspector, but they'll give up if the nodes are obfuscated.
All this to say that with things like Circle To Search or Apple's built-in screenshot OCR nowadays websites and apps are finally on a level playing field when it comes to anyone being able to circumvent text protection.
Google pixel devices have had this for years. It's one of the few things that keeps me glued to this platform.
Just push the button to go to the task switch view and as long as the window preview thumbnail isn't blanked out, I can just get the phone to OCR any part of the screen in real time.
"Apps" of this sort are absolutely "on the web", and generally use browser engines to display the content. The real distinction IMO is between using a locked-down mobile interface vs. a full browser on a computer with an OS and UI intended to let you have that control.
You can know. There is always telltale jank in web apps. And there are things that are basically impossible to do in web apps, like reliable camera integration.
People's stupidity will always surprise me. I mean... it's such a basic irony trick given the subject matter that it doesn't even deserve to be mentioned, let alone questioned.
There are many ways to bypass that. User scripts and user styles too. But the point is delivered: one can disable selection, with just a couple of lines of CSS/JS, and cause a lot of pain for the reader.
I recently read something that stated we've never really had more than 30% of students in the US at a level of mathematical understanding where they can tell that 3/4ths and 0.75 are the same thing, conceptually.
I cannot stop thinking about this; it honestly explains so much.
Indeed, one thing I keep in mind is that almost all progress, social, technical, political, etc. are wrought by an exceedingly small proportion of people. These are usually the people derided as deviant, nonconforming, abnormal.
Left to the vast majority of "normal" people who want to half-ass everything, there'd be absolutely no progress whatsoever, and what is more, society might actually fall apart.
That’s probably one of those cases where they use two different statistics to assume a conclusion, e.g. maybe only 30% of students pass a particular profiency test, and then add to the fact that that test is the minimum level where fractions/percentages are expected to be known, and combine it to make a scary sounding headline.
The score is an aggregate over questions testing many different skills, so while getting a low score suggests that a student is less skilled, it doesn't immediately tell you which skills they're bad at in particular. So this is exactly the scenario that 'ninkendo was talking about. If you want to know how many students correctly answered a specific question testing a certain skill, you would need the raw disaggregated data, which I don't think NAGB publishes.
I'd like to add that it's intentional that there are substantial numbers of students in each of the four buckets defined by the three thresholds, since the goal is to track the performance of the overall population, not just a few very bad or exceptionally good students.
I should've clarified it was an example, not that literally that one highly particular thing is what all American students are bad at, or that knowing .75 == 3/4ths == 75% somehow causally affects your future or whatever.
To be fair, you have to have a very high IQ to understand the joke. The humour is extremely subtle, and without a solid grasp of CSS the joke will go over a typical viewer's head. There's also the author's nihilistic outlook, which is deftly woven into his post - his personal philosophy draws heavily from Chris Coyier's classic blogs, for instance. The fans understand this stuff; they have the intellectual capacity to truly appreciate the depths of this joke, to realise that it's not just funny - it says something deep about LIFE. As a consequence people who criticise being unable to select text within the blog post truly ARE idiots. I'm smirking right now just imagining one of those addlepated simpletons scratching their heads in confusion as Bologov's genius wit unfolds itself in their browsers. What fools.. how I pity them.
And yes, by the way, i DO have a tattoo of the Lobotomized Owl selector. And no, you cannot see it. It's for the ladies' eyes only- and even then they have to demonstrate that they're within 5 IQ points of my own (preferably lower) beforehand. Nothin personnel kid.