If you allow me to blunty borrow a quote:

„Below are the average carbon footprints of different emails:

An average spam email: 0.3 g CO2e (carbon dioxide equivalent)

A standard email: 4 g CO2e

An email with “long and tiresome attachments”: 50 g CO2e“

Not sure if the numbers are correct, but I recently heard about that on the local radio too.

Source: carbonliteracy.com/the-carbon-cost...

TIL toLocaleTimeString in Edge returns a string with directionality characters and so can't be used to set the value of an input element of type time.

Punch cards, the foundation of all computer programming, were inspired by automated looms. See en.wikipedia.org/wiki/Jacquard_loom.

Americans pronounce "cache" as "kaysh", but Australians are more likely to pronounce it like "cash".

Oh, and UK/Eire-denizens pronounce "router" like "rooter" - but that's got certain connotations here in AU/NZ ;)

Have you ever asked Siri about "Beatbox"?

useless? here ya go! Peter DeChamp Richardson has been coding for 25 years (that guy is me :P)

back in the day, you have a few models of ibm printers distinguished mostly by duty cycle. you customize via print chains that the operators can change based on what kind of material is being printed. it is possible that an APL chain was manufactured (I've never seen one in the wild, while working with ibm mainframes from 60's to 90's). what IS common is the APL typeball for the Selectric family of typewriters and teletypewriters. I even had one for a few years even though I was only an occasional user of APL, then it got lost in an office move.
so it is more akin to GM creating a special tire rim than a special truck model.

Wat is a talk on all the weird things in programming, the things that make you say
"Wat"
destroyallsoftware.com/talks/wat
I highly reccomend this :)

The hashtag/pound sign, #, is originally known as the octothorpe.

In 2009-2010 Google tried to merge a separate version of Python inside the official one but didn't ultimately succeed.

The story around it was interesting for a few reasons:

• Google at the time was really deep into Python, they were using it for all sorts of things and they employed a few core teams devs, Guido Van Rossum (the creator) included
• "Unladen swallow" (the code name of this branch), was used internally and promised some performance improvements
• Among those improvements there was a JIT compiler (Ruby 2.6 for example has merged an experimental JIT compiler, ten years later)

The reason it failed:

• they thought they could reach 5x speed in single threaded cases but actually they were around 1.x kind of increase
• The community already had a JIT enabled project, PyPy, which was a separate effort
• Developers were not excited about it and also assumed that Google would maintain the code for ever and ever (honestly, nobody wants to merge an insanely huge patch that requires a lot of work to adjust in an already successful project)

So, it was a good idea, but it technically didn't work the way they tried it and there was not enough support around it to keep at it for a long time and hopefully improve the performance gains.

I think this story mostly speaks of what it means to mantain a hugely successful open source project and the relationship with contributors, even if they are a big company ;-)

If anyone is interested, the details and the story are here: python.org/dev/peps/pep-3146/