I think the JS/Node scene was the pioneer in spamming emojis absolutely everywhere, well before AI. Maybe that's where the models picked it up from.

▲ hedora 4 days ago | parent | next [-]

Remember, if you’re going to do this, also make liberal use of ansi codes.

Make sure terminal detection is turned off, and, for god’s sake, don’t honor the NO_COLOR environment variable.

Otherwise, people will be able to run your stuff in production and read the logs.

▲ dvfjsdhgfv 4 days ago | parent | prev | next [-]

I'm a bit ashamed to say that, after using various ASCII symbols (for progress, checkmarks etc.) in the 90s and early 2000s, when I first discovered we can actually put special Unicode characters on the terminal and it will be rendered almost universally in a similar way, it was like discovering an unknown land.

While rockets and hearts seem more like unnecessary abuse, there are a few icons that really make sense in CLI and TUI programs, but now I'm hesitant to use them as then people who don't know me get suspicious it could be AI slop.

	▲	elzbardico 4 days ago \| parent [-]
		I absolutely love the checkmark and crossmark emojis for use in scripts. but I think they are visual garbage in logs.

▲ pjmlp 4 days ago | parent | prev | next [-]

I really hate all those CLI applications and terminal configurations that look like circus came to town.

▲ henrebotha 4 days ago | parent | next [-]

I don't love emojis for this purely because they're graphically inconsistent; I can't style them with my terminal font or colour scheme. But I'm a huge fan of using various (single-width) unicode chars with colour to make terminal output a lot easier to parse, visually. Colour and iconography are extremely useful.

▲ JdeBP 4 days ago | parent | next [-]

Hieroglyphics are vastly underused.

    𓂫 ~ 𓃝 JdeBP𓆈localhost 𓅔 %                                𓅭 pts/0

▲

rvnx 4 days ago | parent | next [-]

Love it, first time I see that online on forums (genuinely). Gives ideas for Reddit posts

	▲	hedora 4 days ago \| parent [-]
		U+130B9 is probably a good one to start with over there. (Nsfw)

▲

hooverd 2 days ago | parent | prev [-]

what isn't in the unicode standard these days???

▲ 4 days ago | parent | prev [-]

[deleted]

▲ jiggawatts 3 days ago | parent | prev [-]

It's the same thing as naming your servers Titan and Cerberus, using garish RGB LEDs on every computer part (in a glass case of course), and having a keyboard that looks like a disco.

▲ userbinator 3 days ago | parent | prev | next [-]

The more vapid parts of social media also seem to have plenty of emoji floods, and I suspect that also made it into the training data for ChatGPT and others.

▲ noosphr 4 days ago | parent | prev | next [-]

That's because utf-8 was such an absolute mess in JS that adding an emoji in your code was a flex that it worked.

Sane languages have much less of this problem but the damage was done by the cargo cultists.

Much like how curly braces in C are placed because back in the day you needed you punch card deck to be editable, but we got stuck with it even after we stared using screens.

▲ delecti 4 days ago | parent [-]

> Much like how curly braces in C are placed because back in the day you needed you punch card deck to be editable, but we got stuck with it even after we stared using screens.

Can you expand on this? What do curly braces have anything to do with punch card decks being editable? What do screens?

▲ noosphr 4 days ago | parent [-]

Each punch card was it's own line of text.

By putting the final curly brace on it's own card, and hence line, it meant you could add lines to blocks without having to change the old last line.

E.g. the following code meant you only had to type a new card and insert it.

     for(i=0;i<10;i++){         /* Card 1 */
          printf("%d ", i);     /* Card 2 */
     }                          /* Card 3 */

     for(i=0;i<10;i++){         /* Card 1 */
          printf("%d ", i);     /* Card 2 */
          printf("%d\n", i*i);  /* Card 3 */
     }                          /* Card 4 */

But for following had to edit and replace an old card as well.

     for(i=0;i<10;i++){         /* Card 1 */
          printf("%d ", i);}    /* Card 2 */
     
     for(i=0;i<10;i++){         /* Card 1 */
          printf("%d ", i);     /* Card 2' */
          printf("%d\n", i*i);} /* Card 3 */

This saved a bit of typing and made errors less likely.

▲

jcranmer 3 days ago | parent | next [-]

I'm dubious of this explanation because C itself largely postdates punched cards as a major medium of data storage, and some quick searches doesn't produce any evidence of people using punch cards with C or Unix.

	▲	noosphr 3 days ago \| parent [-]
		Ed was also line oriented. Using regex to edit lines instead of typing them out was a step up, but not much of one. Also my father definitely had C punch cards in the 80s.

▲

3 days ago | parent | prev [-]

[deleted]

▲ JustFinishedBSG 4 days ago | parent | prev [-]

"FastThingJS: A blazing fast thing library for humans . Made with on "

▲

Dilettante_ 4 days ago | parent [-]

I can still see them!

	▲	dormento 4 days ago \| parent [-]
		At this point, we're here just to suffer.