Live data from Hacker News

Google I/O 2023

io.google

91–100 of 443 posts

Re: Google I/O 2023

#91
post #41
post #33

Earlier quoted context omitted.

Heh, yours and other comments here disparaging I/O as "business" or "corporate" talk these days come across as quite ignorant - and I don't mean this in a nasty way, more in a literal way. It seems perhaps you're missing the fact there are many different styles of talks for many audiences. At every I/O there is a "keynote" and a "developer keynote", and similarly there are business / product talks and developer-focus…

> live in a world where they have no choice but to use Google SDKs and services Which world is this? I’m genuinely interested not trying to be rude.

anyone that wants to ship a mobile app?

Re: Google I/O 2023

#92
post #64

I find it interesting the sentiment in the comments... Yesterday we had an Apple post where everyone was losing their minds all day about Final Cut Pro on iPad (which in my opinion as a Software Engineer is the most boring thing I’ve had to read all week). Today we have probably a massive lineup of a bunch of new AI features to be announced for products most of us use on the regular, or could use as devs, and 90% of…

I've noticed that the sentiment on HN tends to skew heavily against Google and more towards Apple. When I go to in-person tech meetups it's usually not at all like that. Not sure why.

Re: Google I/O 2023

#94
post #64

I find it interesting the sentiment in the comments... Yesterday we had an Apple post where everyone was losing their minds all day about Final Cut Pro on iPad (which in my opinion as a Software Engineer is the most boring thing I’ve had to read all week). Today we have probably a massive lineup of a bunch of new AI features to be announced for products most of us use on the regular, or could use as devs, and 90% of…

This is due to Google's track record on killing products.

Re: Google I/O 2023

#95
post #50

Earlier quoted context omitted.

No problem! My team is a small subset of engineers in a 10yo+ startup, and the organisation chose to go all in on many Google services long before any of us joined the company. I have my issues with Google and some of their services but the GP stands out as an odd comment to me because it's at odds with my own experience of keeping up with I/O talks.

Is it still a startup after a decade? Isn’t it just a company at that point.

It’s still a startup if it’s not profitable yet ;)

Re: Google I/O 2023

#96
post #71

Earlier quoted context omitted.

Is it still a startup after a decade? Isn’t it just a company at that point.

Related: It drives me bananas when a mega-corp makes a small R&D team and the job req says “we are a small startup in a big company.” The benefits, bureaucracy, speed of innovation, and equity all fit the usual mega corporate shoes, so it’s probably still a traditional role.

[dead]

Re: Google I/O 2023

#97
post #64

I find it interesting the sentiment in the comments... Yesterday we had an Apple post where everyone was losing their minds all day about Final Cut Pro on iPad (which in my opinion as a Software Engineer is the most boring thing I’ve had to read all week). Today we have probably a massive lineup of a bunch of new AI features to be announced for products most of us use on the regular, or could use as devs, and 90% of…

Ceci n'est pas une pipe. The features are exciting. Google I/O, the conference with talks, is seen as less so. Notice how all the comments are about the talks. Yesterday's Apple announcement was _not_ a conference, and the comment thread was about the new app. It's not the same thing at all.

Here are some snippets from top-level comments in this discussion thread.

> It's all business talk

> I for one benefited so much from Google Developer Groups

> looking forward to the event and plan to watch it

> just corporate talk

> alternate conference

> separate conference

> I can understand now why my company is less eager to send developers to events

You see it, right? They're all about the talks at the conference and not the features. This HN post is specifically about the conference, that's why the title is "Google I/O 2023".

Re: Google I/O 2023

#98
post #64

I find it interesting the sentiment in the comments... Yesterday we had an Apple post where everyone was losing their minds all day about Final Cut Pro on iPad (which in my opinion as a Software Engineer is the most boring thing I’ve had to read all week). Today we have probably a massive lineup of a bunch of new AI features to be announced for products most of us use on the regular, or could use as devs, and 90% of…

HN tends to bias towards pro Apple.

You would see people doing mental gymnastics trying to defend their closed anti competitive practices, disregard for standards. I would cheer a Sennheiser/Bose more than any version of Airpods, I would rather not have a multi trillion dollar company gobble up other industries through unfair advantages.

Seeing a hacker crowd do this is just beyond bizzare.

Re: Google I/O 2023

#99
post #20

I for one benefited so much from Google Developer Groups while at University. Google made sure we learned how to build Android Apps, and consume API's and services like Maps, Firebase, etc. Overall, I gained a good understanding of how systems work, Thanks Google! --From Uganda

Google did not do this out of the goodness of their heart. They did it to lock you in with Firebase, Maps, etc. And believe me, the moment they start charging you for it, you quickly realize why Google is not a company to give an ounce of trust to.

[flagged]

Re: Google I/O 2023

#100
post #5

I stopped caring about I/O when it became just corporate talk

Which one of these talks from ML/AI at I/O 2022 would you describe as "just corporate talk"? https://www.youtube.com/playlist?list=PLQY2H8rRoyvyY0AsvPIkb...

I understand him. Maybe Im cynical but everything I see on your link looks like something a technical sales person would come up with… How easy is it to onboard people? Easy! Are we helping save the world? Yes! Can we build it ethically? Yes!

Are those questions really what’s on the mind of the developer? Where is the: we have a way to revolutionize the debugging experience when doing ML(for people with PhDs) talks?

I know it wouldn’t sell to the masses but that was kind of the point if you want jaded devs on your side.

Post reply on HN