Too many emojis in 'Concurrency and async / await' explanation

[kittenswolf]

The explanation page for concurrency, and more specifically its example with burgers (https://fastapi.tiangolo.com/async/#concurrent-burgers) becomes hard to read for me because of its many emojis.

An excerpt:

You go with your crush 😍 to get fast food 🍔, you stand in line while the cashier 💁 takes the orders from the people in front of you.
Then it's your turn, you place your order of 2 very fancy burgers 🍔 for your crush 😍 and you.
You pay 💸.
The cashier 💁 says something to the guy in the kitchen 👨‍🍳 so he knows he has to prepare your burgers 🍔 (even though he is currently preparing the ones for the previous clients).
The cashier 💁 gives you the number of your turn.
While you are waiting, you go with your crush 😍 and pick a table, you sit and talk with your crush 😍 for a long time (as your burgers are very fancy and take some time to prepare ✨🍔✨).
As you are sitting on the table with your crush 😍, while you wait for the burgers 🍔, you can spend that time admiring how awesome, cute and smart your crush is ✨😍✨.
...
But as you go away from the counter and sit on the table with a number for your turn, you can switch 🔀 your attention to your crush 😍, and "work" ⏯ 🤓 on that. Then you are again doing something very "productive" 🤓, as is flirting with your crush 😍.

In my opinion, the many emojis don't add anything to the explanation and make it hard to read. Every emoji breaks the flow when reading because my eyes are distracted by the emojis' size and colour.

Is the '😍' after every 'crush' necessary? Same with burger and 🍔, cashier and 💁 and so on.

I propose cutting down on or completely removing emojis from the documentation to help with readability.

The same issue, though less pronounced, is also apparent in the section 'Asynchronous Code' (https://fastapi.tiangolo.com/async/#asynchronous-code).

---

(If you want to know what it feels like to read the documentation, try reading this:)

In my 🧑opinion 🤔, the many🔢 emojis don't add anything😣 to the explanation😪 and make it hard to read😓. Every emoji🤪 breaks the flow☄🌬 when reading📖 because my eyes👀👀 are distracted😜😒 by the emojis' size🥵 and colour🤡.

[Kludex]

Emojis are part of our culture. 😅

(If you want to know what it feels like to read the documentation, try reading this:)

I've read the documentation, and I don't feel the same as reading your example, as it's clearly ill-intentioned to prove your point. 😗

That being said, we can wait to see if people have the same opinion as you, and/or you can propose a PR changing that page, and @tiangolo you'll check it at some point.

I don't think this change is needed, nor do I feel harmed by those emojis, sometimes I even get the opposite effect as the one you mentioned. Which I think is because humans tend to relate images better than letters.

EDIT: Well... Months have passed, and my opinion has changed. I no longer have strong feelings about this. Although, I think the most important argument here is the one mentioned here. 👋

[baby5]

you can write non emojis one in your self page.

[ParitoshSingh07]

That page was painful to read. Can the emojis be toned down please?

For a middle ground, perhaps introduce them in the opening sentence, and then stick to using them at the end of sentences, avoiding the temptation to use them mid-sentences outside their first occurrence.

[kms70847]

"we can wait to see if people have the same opinion as you". It's been a few months, which seems like a reasonable time frame for waiting and seeing. The original post has 14 thumbs up and 2 thumbs down, so it seems like the community is in favor of it.

[sanchesper]

Found this post because I made a search on Google: "why fastapi doc full of emojis". I didn't understand why the words are not replaced by the emojis, but instead have the word and the emoji together. If want to keep the emojis, so remove the redundancy for better reading. (i.e. "You go with your 😍 to get 🍔, you stand in line while the 💁 takes the orders from the people in front of you.")

[v3ss0n]

May be targeted audience is 16 year olds.
J/K.

[Zeta611]

When I landed on the FastAPI documentation page explaining concurrency last week, I almost immediately returned to the previous page.
I even stumbled upon this issue page after googling concurrency emoji--I was looking for an emoji that fits with the concept concurrency for my blog post.

The reason I left the doc was mainly because I already knew the concept, but I would have at least tried to read it to see how it explains concurrency if it were not for the emojis.
And even if I were new to the concept, I probably would have searched for an alternative source explaining it.

IMHO, the use of emojis 🔀 and ⏯ was actually pretty smart, and perhaps the use of 😍s has lightened the mood... But the current 3😀/sentence is definitely not helping the readability.

[joe-butler2]

cope

[acidjunk]

or not to cope

[chocabloc]

that is the question

[YodaEmbedding]

The 🎡 of 🕦 turns, and ages come and pass, leaving emojis that become legend. ✨✨✨ Legends ✨✨✨ f a d e to myth, 🐉 and even myth 🐲 is l o n g forgotten when the Emoji that gave it birth 🧑‍🍼👩‍🍼 comes again. ⏳ In one such Emoji, called the 🏎️ 🏎️ 🏎️ Fast API 🏎️ 🏎️ 🏎️ by some, an Emoji yet to come, an Emoji long past, a wind 🪁 🪁 rose in the ⛰️ ⛰️ ⛰️ Misty Mountains ⛰️ ⛰️ ⛰️ of Emijiji. The wind 🪁 was not the beginning ⏳. 👉 There are neither beginnings nor endings to the turning of the 🎡 of 🕡. But it was a beginning. ⏳

[intrnl]

Another major problem with this which isn't being talked enough is that for people who have reading/visual impairments and thus needs to rely on screen readers, the overuse of emojis adds a lot of noise that otherwise distracts from the actual material.

screenrecord-2022-01-21_15.49.15.mp4

Accessibility is important.

[vimpostor]

I like the irony of reacting to the original issue above with all sorts of different emoji. 👀