Nah, you're cool. I know my system's old, but as you say there's still plenty of life in it, so I'll keep it for now. Especially since I stick entirely to indie games these days.

But actually, I'm keeping an eye on auctions for something just a few years newer. Games that require AVX2 extensions are finally starting to come out, and my CPU doesn't support them. Even with indie games, most of them use third-party engines, so it might not be too much longer before it's an issue even for me.

I'm guessing it's because "SyncThing" is a proper noun.

I scored 12/28 on https://jsdate.wtf/ and all I got was this lousy text to share on social media.

A tiny number of original releases don't run properly or at all on some 2600 Juniors or 7800s, due to a reliance on quirks that were changed in later versions of the graphics chip. Probably not a major issue for classic collecting, but if you're interested in modern homebrew, it could be worth considering.

One of my favorites. I'm so glad that I played it without any guides, so I could find all the little touches on my own.

Also, if you've got the time (or a cheat device), it's mildly amusing to grind to the maximum level so you can virtually one-shot the final god-like boss after all its posturing.

Nope, you got it right. It was very much seen as only a console, despite the naming, Family BASIC, FDS, other peripherals, etc. I've been living in Japan for years with a keen interest in retro gaming/computing, and FC is never mentioned in the same breath as PC-88/MSX/FM/etc. By the by, on the rare occasions that it's mentioned, the SC-3000 is also lumped in with the consoles rather than the home computers.

The Steam Deck is a handheld Linux-based PC with a built-in game controller. The special Steam version of Linux (SteamOS) comes with software (Proton) that lets you run a lot of Windows games, and Valve have put some effort into helping/encouraging developers to get their games working with it.

The Nintendo Switch is a closed system that can only play official Nintendo-licensed software. Even if you "jailbreak" a Switch, I don't think that there's any realistic way to get modern Windows games running on one.

And "doronko", as we might guess, basically means "mud" or "muddy".

It's definitely bad design, but in a pinch it is readable in landscape mode for me. Alternatively, if your browser has a "force desktop mode" option, that often makes badly-written websites useable, if annoying.

"Inventory" usually refers to the list of items that the player character is carrying while the game is running. Why would you store that in a file and not memory? Are you talking about a game save file?

Drawing on Japanese, which is the only non-English language I have significant experience with, object.method(parameter) would feel more natural as object.(parameter)method, possibly even replacing the period separator with a Japanese grammatical construct (with no equivalent in English) that really suits this use case. Even the alternative function(self, parameter, ...) would mesh better with natural Japanese grammar as (self、parameter、〜)function. The majority of human languages have sentences which run Subject-Verb-Object, but a handful which includes Japanese run in the order Subject-Object-Verb.

I gave an example of an alternative for...in loop in another comment here, so I won't rehash it here. But following the general flow of Japanese grammar, that for at the beginning of the statement would feel much more natural as a で (or "with") at the end of the statement, since particles (somewhat similar to prepositions in English) go after the noun that they indicate, rather than before. And since semicolons don't exist in Japanese either, even they might be replaced with a particle like "と".

There aren't any big problems here, but a plethora of little things that can slowly add up.

I'm no linguist, but I have some Japanese language ability, and Japanese seems to be pretty different, grammatically, from English, so I'll draw on it for examples. I also had a quick look at some Japanese-centric programming languages created by native speakers and found that they were even more different than I'd imagined.

Here's a first example, from an actual language, "Nadeshiko". In pseudo-code, many of us would be used a statement like the following:

print "Hello"

Here's a similar statement in Nadeshiko, taken from an official tutorial:

「こんにちは」と表示

A naive translation of the individual words (taking some liberties with English) might be:

"Hello" of displayment

I know, I know, "displayment" isn't a real English word, but I wanted to make it clear that the function call here isn't even dressed up as a verb, but a noun (of a type which is often used in verb phrases... it's all very different from English, which is my point). And with a more English-like word order, it would actually be:

displayment of "Hello"

Here's another code sample from the same tutorial:

「音が出ます！！」と表示。
1秒待つ。
「プログラミングは面白い」と話す。

And another naive translation:

"Sound comes out!!" of displayment.
1 second wait.
"Programming is interesting" of speak.

And finally, in a more English-like grammar:

displayment of "Sound comes out!!."
wait 1 second.
speak of "Programming is interesting".

And here's a for...in loop, this time from my own imagination:

for foo in bar {  }

Becomes:

バーのフーで {  }

Naively:

Bar's Foo with {  }

More English-y:

with foo of bar {  }

You may have noticed that in all of these examples, the "Japanese" code has little whitespace. Natural written Japanese language doesn't use spaces, and it makes sense that a coding grammar devised by native speakers wouldn't need any either.

Now, do these differences affect the computer's ability to compile/interpret and run the code? No, not at all. Is the imposition of English-like grammar onto popular programming languages an insurmountable barrier to entry for people who aren't native English speakers? Obviously not, as plenty of people around the world already use these languages. But I think that it's an interesting point, worth considering, in a community where people engage in holy wars over the superiority or inferiority of various programming languages which have more in common than many widely-spoken natural languages.