magic_lobster_party

For example, in Swift, if you declare a function to throw an exception, then by God every call to that function, all the way up the stack, must be adorned with a do-try block, or a try!, or a try?

I agree with him on this point. Sounds similar to how it’s in Java, and I hate it. I always wrap my exceptions in a RuntimeExceptions because of this.

I disagree with him the rest of the post. The job of the programmer is to communicate the intent of the program. Both for others and for yourself. The language provides the tools to do so. If a value is intended to be nullable, then I would like to communicate this intent. I think it’s good when a language provides this tool.

Tests don’t communicate the intent of the code. Tests can’t perfectly validate all the possible edge cases of the system either.

He realized he couldn’t polish a turd.

Red carton is chosen because that’s how it’s commonly depicted in cartoon images.

https://duckduckgo.com/?q=french+fries+cartoon&t=h_&iar=images&iax=images&ia=images

Unicode Consortium decide which emoji should be included. It’s up to each vendor themselves to come up with how they should look like. I don’t think Unicode Consortium explicitly state it must look like McDonald’s fries.

It’s so good it got not only one, but two standard libraries.

Stack overflow intensifies

https://unicode.org/emoji/proposals.html#Faulty_Comparison

The existence of other emoji can’t justify the inclusion of a new emoji. Those emojis are old, and it’s unlikely they would’ve been approved under Unicode’s current guidelines.

The logo and name is the brand. How do you visually represent a specific payment protocol without using its logo? There’s no emoji for HTTP or TCP either.

The problem with having cryptocurrency as emoji is agreeing on the specification how it should be drawn, and also make it different enough from already existing emojis such as coin 🪙. It is not exactly a tangible thing.

It probably falls under faulty comparison:

https://unicode.org/emoji/proposals.html#Faulty_Comparison

Their guidelines change, and it’s possible these emoji were added with old guidelines. They can’t remove old emoji, which means specific buildings like Tokyo Tower🗼is an emoji, even if they prohibit the addition of specific buildings nowadays.

https://unicode.org/emoji/proposals.html#Faulty_Comparison

The Tokyo Tower🗼(a specific building) does not justify adding the Eiffel Tower.

Many historical emoji violate current factors for inclusion. Once an emoji is encoded it cannot be removed from the Unicode Standard.

It was added when Unicode Consortium had different guidelines. They don’t accept specific buildings anymore.

Under automatically declined:

Specific buildings, structures, landmarks, or other locations, whether fictional, historic, or modern.

The Bitcoin logo is the brand. Corporations like exchanges use this brand to market their services.