this post was submitted on 17 Apr 2024
1364 points (99.5% liked)

Programmer Humor

19434 readers
93 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 1 year ago
MODERATORS
 
top 16 comments
sorted by: hot top controversial new old
[–] [email protected] 6 points 6 months ago

We have a love & hate relationship with unicode.

[–] [email protected] 80 points 6 months ago

It's like... WE , the viewers have the wrong encoding. Only we don't know how the owner of the sticker feels about Unicode. They themselves know exactly how they feel about it.

I like that.

[–] [email protected] 11 points 6 months ago
[–] [email protected] 125 points 6 months ago (5 children)

These errors were much more common before Unicode encodings were in broad use. Unicode pretty much solved this.

[–] [email protected] 5 points 6 months ago

I like your enthusiasm. I remember when I believed the same. The last 16 years have clearly shown this is not the case.

[–] [email protected] 2 points 6 months ago

Still needs to be widely used. It took me about an hour to figure out that my encoding issues were because of Vim being in latin1, another to figure out how to change that, and a third to realize that screen also wasn't in UTF-8 mode.

[–] [email protected] 19 points 6 months ago (1 children)

Only if it's enabled by default, or the dev knows to enable it.

I had a lot of weird problems processing some info with names in Powershell until I found out that Powershell doesn't default to unicode format when shoving output into files. You can easily specify the encoding, but if you don't it replaces any non-ascii characters with "?" by default, so it's not even immediately obvious that there's an incorrect character, as it just silently substitutes a valid one.

[–] [email protected] 1 points 6 months ago

it uses big-endian utf-16 with BOM by default unless you upgrade to PowerShell 7

[–] [email protected] 4 points 6 months ago (1 children)

No it hasn't. It has just pushed them out of sight for English natives.

[–] [email protected] 28 points 6 months ago

Can't confirm that. In the 90s encodings were a nightmare. ISO-8859-1, ISO-8859-15, CP1252, IBM850, ... If you tried to build a website with an upload form, you'd get the most bizarre encodings and there was no way to reliably distinguish them. I'm not an English native, my world is full of umlauts and s-z ligatures. Things got A LOT better in the last years, thanks to Unicode encodings.

[–] [email protected] 55 points 6 months ago (1 children)

Still happens for new emoji on old OSs, or just missing characters in the font being used.

[–] [email protected] 6 points 6 months ago

exacgly today these errors is always because some old emojis

[–] [email protected] 39 points 6 months ago (1 children)

I would have sex with this bumper sticker.

[–] [email protected] 22 points 6 months ago (1 children)

Sir, This is a Wendy's parking lot.

[–] [email protected] 10 points 6 months ago (1 children)

You're just making it worse.

[–] [email protected] 2 points 6 months ago

You're just making it ~~worse~~ better.