doodpants

My 3 minutes in hardcore mode:

Screw Flanders. Screw Flanders. Screw Flanders. Screw Flanders. Screw Flanders. Screw Flanders. Screw Flanders. Screw Flanders. Screw Flanders. Screw Flanders. Screw Flanders. Screw Flanders. Screw Flanderss. Screw Flanders. Screw Flanders. Screw Flanders. Screw Flanders. Screw Flanders. Screw Flanders. Screw Flanders. Screw Flanders. Screw Flanders. Screw Flanders. Screw Flanders. Screw Flanders. Screw Flanders. Screw Flanders. Screw Flanders. Screw Flanders. Screw Flanders. Screw Flanders. Screw Flanders. Screw Flanders. Screw Flanders. Screw Flanders. Screw Flanders. Screw Flanders. Screw Flanders. Screw Flfanders. Screw Flanders. Screw Flanders. Screw Flanders. Screw Flanders. Screw Flanders. Screw Flanders. Screw Flanders. Screw Flanders. Screw Flanders. Screw Flanders. Screw Flanders. Screw Flanders. Screw Flanders. Screw Flanders. Screw

A rather non-obvious fact, because the language names clearly and misleadingly suggest otherwise.

He made it quite clear in the article that he was not concerned about the reversal, he was concerned about the lack of notification of the reversal.

>If anyone has tips on how I might get my Google and Twitter accounts back, I would greatly appreciate the feedback.

I know of one approach that might get results, but he's already done it: publicly shame them in an article. It's the only way to get results from these algorithm-driven companies that lack anything resembling an actual customer service department.

I was thinking the same thing. As I read the page, all I could think was, "No, shut up." :-)

Pardon the off-topic comment, but is anyone else finding the discussed web page to be sluggish to the point of unusability? (This is on Firefox 67, on Windows 7.) I'm not talking about page load time; once the page has finished loading:

- trying to scroll the page using arrow keys or Page Up/Down keys takes several seconds between key press and response

- when dragging the scroll bar manually, the new scrolled-in area is blank white for several seconds before finally filling in with content

- even right-click, or click-drag to select text, takes a few seconds to respond

I tried disabling javascript on the page, but it makes no difference, so it's not some runaway script. I'm guessing that maybe there are some very high resolution Mandelbrot images that are being scaled in the browser?

I'm hoping that this work might give me some valuable info on how to get started on various Project Euler[0] problems that I might otherwise have no idea how to approach, or that I wouldn't know what area of math to do research for.

[0]https://projecteuler.net/

> Google kinda pulled a "bait-and-switch" with Android.

> When they released it, it was pretty much 100% Open Source, then they moved more and more elements to their proprietary GApps suite, included the Play Services required to run even many 3rd party apps.

I thought the reason they did this was because third party phone makers were controlling when/whether users could update the OS on their device. So users were often several Android releases behind, even on a phone that was only a year old. By moving a lot of the core functionality into apps, users could update these apps and have access to newer features even on older OS versions.

Though, I guess that doesn't explain why the apps themselves aren't open source.

Maybe I'm weird, but being right-handed (like most people), I prefer directional controls on the right hand and action buttons on the left. Your characterization of the former as "left-handed" and the latter as "right-handed" controls seem backwards to me. So, to be honest, I don't even use WASD (or ESDF).

Why WASD and not ESDF? People have been touch-typing with their left hand in that home position since the late 1800s. (Or do you actually operate WASD with your pinky, ring, and middle fingers when gaming?)

> Released May 1, 2019

Woah, it's from the future!

The actual saying is "imitation is the sincerest form of flattery". Sorry, but it's a pet peeve of mine when people replace "sincerest" with "best", because it changes the point of the adage.

If your monitor is shining like a bright flashlight in your eyes, then you have your monitor's brightness turned up too high. (And/or your room's ambient lighting is too low.) A window with a white background should appear no brighter than a white piece of paper held up next to your monitor. If you use this technique to adjust the brightness of your monitor, you can read black-on-white text all day long and never get eye fatigue. I've been adjusting my displays this way for ~20 years.

No, there are plenty of areas of software development that are much more stable. Nearly 6 years ago, I took a new job to develop a Windows desktop application using C# and WinForms. It hasn't changed much since then. There have been a few updates to the C# language to add some syntactic sugar, and to better handle certain niche concerns, but nothing that's had any major impact on how we typically implement things.

I was wondering whether it was the same Paul Dean from SU&SD. Thanks for confirming that it was, and that I was reading the article with the correct voice in my head. :-)

Agreed. But the ExportHtml plugin isn't an entirely horrible workaround, so at least there is a way.

> Thankfully, there’s an easy solution, which is normalizing the string into the “canonical form”.

Cool, problem solved!

> There are four standard normalization forms:

(╯°□°）╯︵ ┻━┻

> Cool, cool. To preface this comment, I'm a user experience designer, and I've been doing web software development and design for over 20 years.

Cool, cool. To preface this comment, I'm a guy who owns a computer and uses software.

Most GUI redesigns I've seen in the past 10 years make the interface prettier, but LESS usable. The new design usually incoroporates three categories of changes:

1. Lists of items are rendered in a larger font with more spacing between items, leading to lower information density, thus requiring more scrolling. (For bonus points, often a window that has a scrollable area isn't resizable, so you're stuck with whatever arbitrary viewport size the designer decided was large enough.)

2. Controls that used to always be visible are now hidden until you hover or click the right spot. This is done to reduce "clutter", as though controls are somehow graffiti.

3. A bunch of convenient shortcuts enjoyed by long-time power users weren't reimplimented in the new design, because the designer didn't know about them, or simply didn't think they mattered.

I have a WordPress blog. WordPress recently overhauled their entire editing UI, and I hate it. When I started the blog several years ago, I was able to figure out how to use WordPress by exploring the UI. The new UI is an extreme example of #2; when you go to write a new post, the page is entirely blank. You have to click somewhere to get a text cursor, and there isn't even a visually delineated text area before you do so. There are a couple of features I had to hunt around for, and I wouldn't have even known those features existed if I hadn't learned them from the old UI, which presented them front and center.

My company uses JIRA for bug tracking. They switched to a new GUI a while back, and I hate it. It's harder to find things that used to be presented front and center. And as an example of #3: It used to be possible to just type an issue number like "392" in the search box, hit Enter, and be brought immediately to that issue page. Not anymore; if you do that quickly, you get a "no results found" page. If you type the number and then wait a couple of seconds, you get a list of search results, which you can then click on. Pressing Enter then takes you to the first one, but often that is NOT issue #392, it's just some issue that happens to have the text "392" somewhere in it. So you have to eyeball the search results, and then click the right one. The old way was more convenient. Fortunately, I eventually found the preference to switch back to the old GUI, which they helpfully give you because they apparently realize that the new GUI sucks. (I don't know offhand if it reverts the search behavior, because I've already changed my habits to not use it anymore.)

Agreed. Perhaps this software from the '80s should be replaced by software with interface design sensibilities from the '90s.

I'm not a Go user myself, but I skimmed through the document. What I found was a lot of good programming advice that is generally applicable, rather than being limited to the Go language. (It seems most of the Go-specific stuff is in section 5.) It's always good to see robust coding practices being promoted, regardless of language.

The new switch expression is to the old switch statement what the ?: operator is to the if/else statement.

Sometimes you want to provide one of two different values based on a condition. If you use if/else, then each statement body has to contain either an assignment (if the value is to be used later in the same function), or a return (if the value is to be immediately returned from the enclosing function). It is often more clear and concise to use a ?: expression at the site where the value is to be used.

Now consider the case where you need to choose among three or more different values. You can use chained if/else statements, which have the same drawback of needing to contain either assignments or returns. Or you can use chained ?: expressions, but there's really no good way to format this in a way that remains clean and easy to understand.

The new switch expression provides a cleaner alternative to chained ?: expressions.

I have no experience with handwriting recognition, but intuitively it seems like the facts that:

a) the grammar for chess move notation is fairly limited; and

b) each move must be valid relative to the current game state

can be used as contextual clues to resolve ambiguous characters. Of course, this means you can't use an off-the-shelf handwriting recognition package that recognizes whole words like you describe, but requires a custom per-character recognizer. (But then, isn't that what you're doing already?)

That's exactly the problem: the developer prioritizing their own convenience over the end user experience.

You can buy some here [0]. Really nifty laser-cut acrylic pieces in a variety of colors, and you can even get a vinyl mat and set of rules for a board game that uses them. (Disclaimer: I personally know the designer of the game, and helped her playtest it.)

[0] http://gamepuzzles.com/pentuniv.htm#KD

> If we include virtual interactions, the range of people a person interacts with each day continues to grow. This essentially means that the number of opportunities to “simulate” strategies for interacting with others continues to grow. If being nice is the winning strategy in modern society, then the increasing number of interactions will increase the speed at which people “learn” to adopt this strategy.

I'd certainly like this to be true, but the past couple of decades have shown that unmoderated internet fora can tend to get pretty toxic, so it's hard to be so optimistic. Part of this could probably be explained by algorithms promoting contentious content for page views. But such toxicity was also present before the rise of modern algorithmically controlled news and social media, such as USENET newsgroups in the 90's and early 2000's.

And then of course there's the SNL parody: https://www.ebaumsworld.com/videos/magical-mysteries-icp-mir...

One explanation I read somewhere is that, by constantly pushing the envelope on form factor constraints and manufacturing complexity, they are making it impossible for knock-off companies to make convincing counterfeits.

It seems to me that gyroscope data is merely input, rather than personal data. In other words, I'm not sure asking permission before accessing gyroscope data makes any more sense than asking permission before accepting touch screen input. Or for desktop applications, asking permission before accepting keyboard/mouse input.

Defeating nytimes's paywall is a simple matter of disabling Javascript in your browser.

It works! (After uninstalling, and then re-downloading and running rustup-init.exe)