Live data from Hacker News

Emoji Kitchen

emojikitchen.dev

51–60 of 65 posts

Re: Emoji Kitchen

#51
post #27

Earlier quoted context omitted.

> > why don’t devs put in the minimal effort You left out the noscript part. I’m not implying the project as a whole is minimal effort. It would be nice to at least see a small explanation of what I as a user am missing out (one or two sentences), or the bare minimum is to at least name the application in the noscript instead of leaving the default text of create-react-app (or similar project generator). It could be…

How would this change anything? Would it really increase your trust in this site, if the site itself told you it's content? A malicious actor would just put "Enable JavaScript now or you will miss out on cool prices" or something like this. "noscript" shouldn't serve any other means but telling you that javascript is disabled.

No script is also a place for normal fallbacks where relevant in a multi-page app such as a static image instead of an interactive SVG. You can let crawlers and scrapers that don’t execute JavaScript know what content should be there. There’s still malice in many noscript elements embedding fishy tracking pixels.

If this application said “Emoji Kitchen let’s you combine existing emoji to create new hybrid emojis” I could decide if I think that’s silly, probably legit, and it’s worth the ‘risk’. It would also assist the aforementioned crawlers and scrapers.

Re: Emoji Kitchen

#52
post #45
post #42

You can also combine the same emoji with itself, getting an exaggerated version.

LMAO You're right https://i.imgur.com/PVhWci3.png Good lord, I wonder how long this took to create. Some of these are insanely hilarious with the more exaggerated version. Like the salute emoji uses both hands

Yeah, it's amazing that Google paid a bunch of designers to do this for over 30.000(!!) combinations. The feature isn't even advertised in the Google software keyboard, it's easy to miss.

Re: Emoji Kitchen

#58
post #50

Earlier quoted context omitted.

Aren’t web crawlers of all search engines executing JavaScript nowadays ?

Nope. You can see it in Brave search results. It’s also a massive barrier for a small start-up to index the web if it has to expend resourses to download and execute JavaScript. More generally, there’s also web scrapers (the good kind), TUI browsers, old hardware that shouldn’t be obsolesced just because of “browser target = current browsers only” (with this being more important for informational type websites rather…

I understand your point about supporting old hardware but the economics or the mental health don’t allow to support any kind of hardware forever.

I had to support obsolete computers running internet explorer too many times in my life and I am glad that I don’t have to right now.

We also eventually stopped the Minitel, even though it was still used by a few people.

Re: Emoji Kitchen

#59
post #28

Earlier quoted context omitted.

Of all things to worry about when designing a website, the basically-zero percentage of people who voluntarily disable JS doesn't even make the list. I view the noscript tag more along the lines of "Hey, your browser isn't working" than "Here's a sales pitch for my site for you and the 2 other people who disabled Javascript".

As time has gone on, more and more folks recommend disabling JavaScript as the default behavior and opting in on a per-site basis. This is easy to do with uBlock Origin. This isn’t a broken browser behavior but a conscious decision for the security and privacy of many users. Leaving one or two sentences isn’t much, and the “sales pitch” will help with SEO for web crawlers that don’t execute scripts.

In retrospect, you're definitely right and I will make note of that in the future.

Re: Emoji Kitchen

#60
post #50

Earlier quoted context omitted.

Nope. You can see it in Brave search results. It’s also a massive barrier for a small start-up to index the web if it has to expend resourses to download and execute JavaScript. More generally, there’s also web scrapers (the good kind), TUI browsers, old hardware that shouldn’t be obsolesced just because of “browser target = current browsers only” (with this being more important for informational type websites rather…

I understand your point about supporting old hardware but the economics or the mental health don’t allow to support any kind of hardware forever. I had to support obsolete computers running internet explorer too many times in my life and I am glad that I don’t have to right now. We also eventually stopped the Minitel, even though it was still used by a few people.

IE7 was the oldest version I ever had to support--I understand it being a pain and there is always a cut-off point. This said, not JavaScript is often an option too for entire categories of the web ...and I say this as someone whose career has mostly been built on CSS & JavaScript. There’s a lot of old machines that should and could be able to read the sites we have today if wasn’t for that pesky scripting language being used where it didn’t need to (looking at you blogs and news sites that blocked your image loading behind JavaScript even though native loading="lazy" exists and would be a progressive enhancement).
Post reply on HN