According to this article, an average smartphone uses 2W when in use. That number will largely be dependent on the screen and SOC, which can be turned off or be placed in a lower power state when the phone isn’t actively being used. (The 5W - 20W figure is for charging a phone.)

With 8 of these cells, you’ll have 800μW, or 0.0008W, and you need 2W. You will need to add a few more batteries… About 19,992 more. If 8 of these batteries are about the same size as a regular smartphone battery, you will need the equivalent of 2,500 smartphone batteries to power just one phone.

Too bad they don’t say how much the new batteries weigh! It would have been fun to see…

If we ballpark it and assume something the size of a regular smartphone battery is 50g (1.7 oz), then our stack of 20,000 of these new batteries could be about 125kg (275 lbs).

I won’t be replacing any of my batteries just yet.

I like your optimism, but no, they are actually serious.

Sadly, yes. On the off chance you speak Dutch, here is a fact-checking article on that exact ad. I know it’s a weird thing to link articles in uncommon languages, but I came across that article recently and thought it really provided a lot of context, so I’m afraid it’s the best source I have. You can always run it through a translator too :-)

That may be true for the exact hardware you used, and the exact tests you have done. For Microsoft the problem would be that they need to actively continue supporting older and older devices. At some point it makes sense to drop active support. If it works, that’s fine, but they won’t continue testing and fixing for unsupported configurations.

Phrased differently: Microsoft announces the end of support for a product. If you want to pay for it, they will make an exception and continue to support it just for you.

I understand people dislike Windows 11, but complaining about life cycle management isn’t going to help that.

You want to translate COBOL to another language? That exists as a commercial product! The complexity is not the syntax though, it is the environment and subsystems surrounding the code. A lot of COBOL is designed for mainframe systems, and emulating a mainframe is complex.

You also end up with code that is still written as if it were COBOL. The syntax for COBOL is the easy part and that is all you can easily replace. Afterwards you’re still stuck with the way of working and mindset, both of which are quite peculiar.

The company I work for recently looked at all of this, and we decided not to translate our code.

One of the arguments that gets used is that the employees should look neutral. For example, if you want to get your gender changed you might not be comfortable with someone who is visibly associated with a religion that disproves of gender changes.

It’s not racism of you believe those people were born into a lower caste because of their actions in a previous life. It is their punishment and thus you should treat them like shit!