That is not enough, since you may still get stuck in a loop.

Fair point, but that is inevitable unless it's a game where the user cannot go back, very few games would fit that bill then.

40 microwatts of power, to be precise. Compared to, say, 5V*1A=5W of typical phone charger, this is impractical by a large margin.

Why is “enough power to charge your phone” your line of practicality? Phones contain an enormous amount of power hungry electronics, bright screens, speakers, multiple GHZ CPUs and radios for transmitting across different spectrum. With 40uW, you’d have to strip most of that away, but you could do something like: power up, take a temperature/CO2/RH/etc reading, transmit to a base station, sleep and repeat every 5 minutes. Sensor networks like these are extremely practical, especially in an industrial setting. Being able to accumulate some power, eg. with an integrated capacitor could also increase your max power draw for when your device is doing work.

Because the first line of the article alludes to using this to power your phone.

It also states. "Promising early applications for the proposed rectenna include powering flexible and wearable electronics, medical devices, and sensors for the “internet of things.” Flexible smartphones, for instance, are a hot new market for major tech firms."

It'd be great for spy devices though

Another nice site aggregating many clever tiny x86 programs: https://www.xorpd.net/pages/xchg_rax/snip_00.html

maybe not the tiniest but reddit.com/r/tinycode has some

This could actually be caused by disk caching effects. Have you tried running cloc second time afterwards?

I tried cloc multiple times. tokei much faster. Try it yourself.

Well, that's why I always define RED(x) (for reduce modulo) as ((((x) % MOD) + MOD) % MOD). Quite useful in algorithmic competitions, which often ask you for answer modulo some prime.

And thus you used a throwaway account...

I use throwaway accounts for everything, so only God (if She exists), NSA and Google know my identity.

From the listed words only two have immediately obvious Polish connotations (dźjada (grandpa), and dziadek is grandpa in Polish; śpjelik (sparrow), where śpiewać is "to sing"). Most words have German-ish sound to them, somewhat similar to Silesian subdialect of Polish (though Silesia was occupied by Germany, which is the reason for its influence). The spelling is mostly Polish-like, perhaps from older centuries though; except for some umlauts which clearly originate in German and similar.

Looks like jewellery is popular in language namimng: we've got Ruby, Crystal, now Emerald...

Don't forget Perl, who (I think) started this trend.

Emerald is older than Perl by several years, though.

The first rock-pased programming environment was silicon.

Eventually someone will have to settle for Cubic Zirconia.

It's done so that the bits will compare the same way whether treated as float or int. (modulo NaNs and stuff)

That is only true for non-negative floating point numbers. It's still useful though.

Interestingly, posits as originally proposed do have this property (except for infinity).

Would have been nice if IEEE stored the complement sign.

The decreasing health bar looks like a really weird idea. I don't like to be forced into thinking fast, I prefer to make a clear point even if it takes longer.