Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

I/O 2022

blog.google

Post reply on HN
Print view View original

151–160 of 237 posts

Re: I/O 2022

#151

Post by sorenjan »

adamrezich wrote: post #68
SemanticStrengh wrote: post #60

Earlier quoted context omitted.

So much hypocrisy going on. If fighting racism was the goal Unicode should not have added skin colored emojis. This is the dumbest move ever.

I will never understand why emoji, the whole point of which is to convey universal emotions (and other icons), ever needed skin tone modifiers at all. why do "thumbs up" and "thumbs up, but i'm white btw" need to be encoded differently? why is everyone OK with Native Americans and other ethnicities with reddish skin tones being excluded? just a complete mess top-to-bottom, and now we can basically never undo it. imag…

Because people didn't understand that emoji was supposed to represent concepts, and saw them as small illustrations instead. That's also why Apple's version is basically the de facto standard now, and Google and Microsoft has had to adjust theirs to look more like Apple's to minimize confusion when the small pictograms doesn't look the same for sender and receiver.

Re: I/O 2022

#152

Post by reaperducer »

three_seagrass wrote: post #122
SemanticStrengh wrote: post #60

Earlier quoted context omitted.

So much hypocrisy going on. If fighting racism was the goal Unicode should not have added skin colored emojis. This is the dumbest move ever.

Excluding skin color and gender is being blind to prejudice, not fighting it.

Excluding skin color and gender is being blind to prejudice, not fighting it.

It's largely a generational thing.

The new generations (Millennial, Z) were taught that "celebrate diversity" is the goal. Which means to highlight all the different races, creeds, colors, etc...

Previous generations (X, Boomers) were taught that being "color blind" was the ideal. Which means to treat every person the same, and disregard their race, creed, colors, etc...

Both groups are using the same language for the goal: To end racism. But the ways they were trained to do so are the exact opposite of each other.

Re: I/O 2022

#153

Post by SemanticStrengh »

disgruntledphd2 wrote: post #103
twelvechairs wrote: post #100

Earlier quoted context omitted.

The default was yellow which basically represents white people.

I mean, sortof, I guess, maybe. Given the history, one could make an argument that they represent Asians rather than Caucasians (it's always seemed odd to me that we ended up with this name for white(r) people, but such is life).

white skinned people should be called beige skinned people. Only albinos could pretend to whitehish-ness and still they are mostly not, because even if their skin maximally reflect light, they are still made of blood. https://en.wikipedia.org/wiki/Albinism_in_humans BTW humans can become easily become black in a continuous like manner https://alchetron.com/cdn/melanotan-ii-d26dbedd-94fb-434a-8d... extreme: https://www.dailymail.co.uk/news/article-3198931/Reddit-user...

It's a very nice technology and is an example of permanent whole body genetic mutation via epigenetics.The issue is that it is irreversible.. The converse, a whitening substance does not exist yet but could exist in theory, by antagonizing the melanin receptors.

Re: I/O 2022

#154

Post by The_Colonel »

scardycat wrote: post #142
valbaca wrote: post #19

Multiple mentions of "skin tone" and AI. Did they really mess up skin tone recognition that bad that they needed three different solutions to it? (I feel like I missed some major fuckup on their end) https://blog.google/products/assistant/assistant-io-2022/ https://blog.google/products/search/monk-skin-tone-scale/ https://blog.google/technology/research/ai-monk-scale-skin-t...

The Pixel 6 Pro camera, which they showcase and market as capable of representing true skin tone [1], has been a pain in the neck for me. I am a brown skinned person with a balding head and the camera preview and final product are completely different. The final product adds random blotches of dark tones on my face and head. None of the photos are usable. This is 100% reproducible especially in bright day light. I fi…

It's a catastrophe for white people as well. My wife has blue eyes, and the camera pretty consistently makes them black. Skin usually turns gray. The portrait looks fine in the preview, but the algorithm messes it up.

Re: I/O 2022

#155

Post by cromwellian »

retskrad wrote: post #2

Google is working on some interesting stuff but their live events aren’t doing them any favors. There’s no hype leading up to them and the events themselves are dull as hell. Google currently has only 40k people watching the live event. Apple WWDC events attract 10X as many concurrent viewers.

Honestly, I preferred the days when developer conferences were for DEVELOPERS and not consumers. Announce APIs, DevTools, demo new stuff developers can use. Back when I/O was "Google Developer Day" and used to be mostly Web-tech, I found it way more interesting, more of a hackers conference. The modern conferences are more about commerce, even on the developer side, and not simply about the Joy of Cool Stuff and Cool Hacks.

These days Apple and Google use developer conferences as pseudo-consumer product soft launches.

IMHO, consumer end user launches should do done at consumer conferences.

Still, compared to Apple, Google's keynotes still contain more stuff of interest to developers like PaLM, LaMDA models, and a change to play with them. Apple's WWDC keynotes are usually so dumbed down, their graphs don't even have numbers of axis labels.

Re: I/O 2022

#156

Post by kdheepak »

jabo wrote: post #126

Almost all the comments so far are negative! So let me change that: I'm excited that something I'm working on, Typesense, was mentioned by name and logo during the developer key note! [1] https://twitter.com/jasonbosco/status/1524483471988727809?s=...

That's exciting stuff! Congrats!

Re: I/O 2022

#157

Post by SemanticStrengh »

three_seagrass wrote: post #131
twelvechairs wrote: post #100

Earlier quoted context omitted.

The default was yellow which basically represents white people.

You're being downvoted but you're kinda right. The longest running cartoon show in history ( The Simpsons ) uses yellow to represent white people, while POC are brown and black.

in racists terms, yellow has always denoted asian people (which is weird btw), simpsons are a coincidence

Re: I/O 2022

#158

Post by webmaven »

ben_w wrote: post #91
staunch wrote: post #43

Earlier quoted context omitted.

It's not merely "gushing" to be excited about new technology breakthroughs. And Musk, through his companies, is actively delivering today on Starlink, Tesla, Dragon, and Starship to name a few big ones. This meme that he's "all talk" is easily disproved for any honest observer.

Yes, although: while the Starship project is incredibly impressive, it can’t really be said to have delivered until it’s actually reached orbit. Until then, it’s like the stuff Boeing, Lockheed, ULA etc. have spent even longer developing and have also not reached orbit with.

> Yes, although: while the Starship project is incredibly impressive, it can’t really be said to have delivered until it’s actually reached orbit.

True, but it isn't as if SpaceX doesn't have a track record for hiring some pretty ambitious targets with their progression of Falcon 1 →Falcon 9 →Falcon Heavy. Admittedly, Starship's planned use of the new Raptor engines seems risky, but the DOD did fund a prototype-and-test contract that presumably concluded successfully a few years ago. While the results of those tests aren't public, there have been no leaks to the contrary, at any rate, and no changes in the planned use of Raptor have been announced (and SpaceX hasn't generally been at all shy about announcing changes to their plans).

I think it's a pretty safe bet right now that Starship will launch and that they will get it working reliably, and that they will have to blow up a few along the way to make those things happen.

Re: I/O 2022

#159

Post by sorenjan »

rpmisms wrote: post #50

Pixel 6a dropped the headphone jack. Great. Gotta find another brand now.

Sony launched their Xperia 1 IV (yes, it's the fourth version of the 1, ridiculous name) today. It's probably around twice as expensive as the Pixel 6a since it's a flagship, but it still has a 3.5 mm jack, and it introduces optical zoom.

https://en.wikipedia.org/wiki/Sony_Xperia_1_IV

Only two years software upgrades though.

Re: I/O 2022

#160

Post by reaperducer »

rvz wrote: post #40
lkxijlewlf wrote: post #11

I popped in for a few minutes to verify something. I'm ... over this whole annual what's new presentation stuff. I just don't care anymore. And honestly the three presenters I saw didn't even seem like they rehearsed at all. They just read from the prompter and tried to put excitement in their voice at the same time and it just fell flat.

Yes. It is always about what they don't tell you in these keynotes that is more interesting rather than what they are already announcing on stage. The only exception is the last announcement which is them trying to re-enter the race for AR/XR glasses which again some thought they gave up. This acquisition is the reason why they are trying again: [0] [0] https://www.cnbc.com/2020/06/30/google-acquires-north-augmen...

AR/XR glasses

Is "XR" a typo for VR, or is there another new R that I should learn about?

Post reply on HN