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

111–120 of 237 posts

Re: I/O 2022

#111

Post by pjmlp »

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.

Same here, I used to care, but since Google has never seriously pushed for updates (Treble doesn't require OEMs to actually care to update), gave up on keeping Java support up to date, I lost interest.

As long as Chrome and the NDK stay around, I am good and don't care anymore whatever version I can only use 5 years from now with already deprecated APIs.

Re: I/O 2022

#112

Post by adamrezich »

twelvechairs wrote: post #100
adamrezich wrote: post #68

Earlier quoted context omitted.

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…

The default was yellow which basically represents white people.

this is the most insane recurring argument and I'll never understand it. sure that's how The Simpsons works, but that's not how LEGO works, so that argument gets canceled out. then you look at the yellow smiley face iconography that I'm sure has cultural roots somewhere but was universally used to specifically express universality—back when WAL*MART used it as their logo, were they specifically trying to market to white people, at the exclusion of all others??

then you take the history of emoji into account and you see that that doesn't really work as an explanation at all. it's like you (and everyone else who makes this inane argument) are trying to make something that's not white-people-centric, white-people-centric, just so you can complain about it being white-people-centric.

Re: I/O 2022

#113

Post by reaperducer »

izzydata wrote: post #48
systemvoltage wrote: post #28

Earlier quoted context omitted.

I miss Steve Jobs era of keynotes. All keynotes are just so dull today. What went wrong?

Technology was advancing more rapidly so there were actually new and exciting things to show you. We seem to be hitting diminishing returns and most of the low hanging fruit and almost all the high hanging fruit problems that we have in our day to day lives have been solved that can be solved with a computer. Now since they have run out of problems to solve they are inventing problems so they can solve them.

most of the low hanging fruit and almost all the high hanging fruit problems that we have in our day to day lives have been solved that can be solved with a computer.

I don't watch the Google presentations, but I'm an avid consumer of Apple's.

That said, even I'm disappointed with the state of technology today. There's still plenty of fruit to be harvested at all levels.

But all I ever see from Apple and Google is variations on "How do I get together with a bunch of people I already know for Thai food in an area that I can walk to?" Or "How do I get through my morning, which is completely predictable and never varies in even the slightest way from one day to the next?"

Here's a softball for both of them:

Using their maps app, allow me to choose a starting point, a destination, and a departure time. Then show me all of the coffee shops within x distance of that route that will still be open for one hour when I pass that location.

Re: I/O 2022

#114

Post by pjmlp »

oofbey wrote: post #80
cogman10 wrote: post #20

Earlier quoted context omitted.

They've become really disappointing. When Google IO started it was a nice fun tech presentation with a lot of side classes showing devs how to work with these new google technologies. Now, it's mostly just google introducing new products to the press.

When they introduce new products, do they say "and really we won't abandon this in 2 years" and keep a straight face, or do they just not even bother?

They push as if they firmly believe in it and then let it drop, see Project Tango, Sceneform, NDK packages,...

Re: I/O 2022

#115

Post by SemanticStrengh »

stickfigure wrote: post #107
twelvechairs wrote: post #100

Earlier quoted context omitted.

The default was yellow which basically represents white people.

Maybe in an advanced stage of liver failure. It's really stretching to say yellow == white. The default color made nobody happy, which is exactly why it was the right solution to the problem.

actually the excessive yellowness brillantly avoided the uncanny valley of half-baked underspecified realism

Re: I/O 2022

#116

Post by adamrezich »

ben_w wrote: post #95
adamrezich wrote: post #68

Earlier quoted context omitted.

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…

People like customising these things to be mini-avatars as a form of self expression. I don’t see a reason to get upset about this option existing — not even from the perspective of “oh no strings are even weirder, I can’t safely treat them as a stream of bytes all the time”, given that combining characters are needed for other stuff anyway. (No idea why you think other skin tones can’t be added later).

>(No idea why you think other skin tones can’t be added later).

because why would we add further bloat and implementation complexity to something that is already bloated and complex to implement?

Re: I/O 2022

#117

Post by Hasu »

hobofan wrote: post #66
izzydata wrote: post #46

Earlier quoted context omitted.

I think Apple, Samsung and Google should give up on this whole iPhone 13 and Pixel 6 naming and numbering scheme and stop pretending like it is going to be an exciting brand new product every single year. They should name them more like cars where you can always expect there to be the latest revision each year, but you never expect it to be something completely new that you need to upgrade to. We need the iPhone (202…

> iPhone 13 and Pixel 6 I think the fact that they are in those high numbers already shows that they "stopped pretending like it is going to be an exciting brand new product every single year". The numbering there is pretty straightforward compared to e.g. the Macbook namings, or the convoluted naming of other brands with stacked variation signifiers, like the "Xiaomi 11 lite 5G NE".

> The numbering there is pretty straightforward compared to e.g. the Macbook namings

I'm confused, while Apple has silly naming conventions for their operating system, the Macbook line doesn't have that at all. It's just the Macbook (and the Macbook Pro and the Macbook Air), Apple doesn't even give them different names or years.

Am I missing something that isn't incredibly straightforward about the Macbook naming?

Re: I/O 2022

#118

Post by SemanticStrengh »

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…

It can and should be undone. There is a difference between the identifier and the representation, android should render color skinned emojis in their yellow equivalent, as simple as that.

Re: I/O 2022

#119

Post by hbn »

dylan-m wrote: post #9
indy wrote: post #7

Earlier quoted context omitted.

There's no hype because they don't have anything to show that deserves hype. It's all the same: AI to improve photos, AI to improve translations and small iterative improvements to Android that you swear were shown at a Google IO event years ago Edit: watching the livestream and they've just announced an Android tablet! Honestly this déjà vu is getting ridiculous

Not to mention Google Wallet, an "amazing new" product by the same name of an existing product they keep renaming and haven't finished retiring yet. They could just say they were updating Google Wallet or whatever it's called now, but I guess you don't get promoted for that. I laughed when the Pixel guy (before announcing the tablet) said they don't usually announce products so far in advance. Has he seen Google I/O?

The tablet announcement is funny too. Another generation of people who haven't been through multiple cycles of this by now are gonna be run through the process of believing Google when they say they're focusing on tablets for real this time, until they launch their tablet and get bored of it a year later and then you wait a few more years before Google makes a totally real commitment to tablets.

Re: I/O 2022

#120

Post by AnimalMuppet »

bsimpson wrote: post #56
izzydata wrote: post #46

Earlier quoted context omitted.

I think Apple, Samsung and Google should give up on this whole iPhone 13 and Pixel 6 naming and numbering scheme and stop pretending like it is going to be an exciting brand new product every single year. They should name them more like cars where you can always expect there to be the latest revision each year, but you never expect it to be something completely new that you need to upgrade to. We need the iPhone (202…

I work at Google and I don't always know which phone is which. It's a phone. It does phone things.

And, really, how many more phone things do you need it to do? Will doing more phone things make it noticeably better?
Post reply on HN