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…
Google I/O 2023
241–250 of 443 posts
Re: Google I/O 2023
#242[flagged]
Because otherwise developers will write bots that generate and upload fake videos, then download the generated captions, in order to use YouTube as a free deep-translation API. (People already proved willing to generate and upload videos in order to use YouTube as a bulk data storage API.)
Re: Google I/O 2023
#243When you google for project tailwind you obviously get results for Tailwind (the css framework).
Did just GOOGLE FORGOT HOW TO DO SEARCH ENGINE OPTIMIZATION?!?
(sorry for the capslock, but I'm lost)
I feel that this comment might bother some people. But the idea that the company will demonstrate on stage a project and fail at choosing a proper googable name, when this company is google itself it's just mindboggling.
Re: Google I/O 2023
#244Earlier quoted context omitted.
When was that? (I expect whatever year you give other people will say it was already just corporate talk before then)
Around 2013 is when I/Os became less about showing technological progress and more about corporate talk. Examples of I/O topics before 2013: Android, Maps API, App Engine (cloud), Chrome, AJAX for their APIs, real-time collaboration/Wave, Google TV (early predecessor to Android TV), Chromebooks, Chrome Web Store, Google Drive, Google Docs, Google Glass, Gmail updates, Google+, YouTube updates. Most I/O topics after 2…
I don't understand how a corporate culture that's so focused on shipping new projects at the expense of maintenance, manages to ship so few new projects.
Re: Google I/O 2023
#245I was very enthusiastic about Google I/O in the past (around the year 2010). Full of nice tech talks; I learned a lot. These years, I couldn't care less. It's all business talk. I guess developers are not the target audience anymore (and for newcomers, perhaps the "I/O" may be misleading).
Re: Google I/O 2023
#246So funny to see google stressing EVERYTIME that they have been using AI for years. Dude, you were seated in the pot of gold and let your organizational disfuncionality block you from really using that. And now you come trying to get the crown of AI? Catch up and them we can talk.
OpenAI must be sweating profusely after viewing that I/O presentation. Not only do they not have the integration, scale and user base of Google, but the migration of Bard to PaLM 2 it will exceed whatever OpenAI currently has. Also, it's only a matter of time before their top employee's are poached by Apple and Google.
Re: Google I/O 2023
#247Re: Google I/O 2023
#248So funny to see google stressing EVERYTIME that they have been using AI for years. Dude, you were seated in the pot of gold and let your organizational disfuncionality block you from really using that. And now you come trying to get the crown of AI? Catch up and them we can talk.
I mean, Google Translate has been basically completely AI powered for 5+ years, and it's one of the most used products in the world... The majority of what you see on SERPs has been AI generated for a decade, and that's Google's main money maker. This idea that Google sucks at AI and is clearly a million miles behind is intriguing. Google is currently the company everyone loves to hate like MSFT was 5-10 years ago. T…
Re: Google I/O 2023
#249Earlier quoted context omitted.
The AirPods are capitalizing on lock-in. iPhones have always had Bluetooth, but almost nobody used BT headphones cause they suck. Then Apple released AirPods with first-party integrations to make it usable, and to make sure people would buy them, they also took out the jack. I care what my options are in the end, a lot more than ideology or something, and Apple worsened my options compared to before. The end result i…
> I care what my options are in the end, a lot more than ideology or something, and Apple worsened my options compared to before. How did AirPods existing ruin your options? You can choose to not buy them, I don't, I like conductive head phones better anyways (non-Apple, before the AirPods came out, and they don't suck, so I don't get what you mean by apple producing the only BT headphones that don't suck?). Or do yo…
Now my choices are:
- AirPods, which I don't want to shell out more money for and deal with charging/caring for them, but otherwise they'd be the best option.
- Non-AirPod BT headphones. I have nice Bose ones from work. These lack Apple's extensions to improve pairing and headset (mic) mode. In headset mode, the earphone quality drops to like worse than early 2000s cellphone. Standard pairing is annoying. It's a bit annoying having to charge them. I also don't want to shell out more money for earbuds (the headphones aren't so portable).
- Dongles, which I tried. Turns out they don't work with inlined mics, don't work with older iPhones (so I can't leave them on a shared car aux), are fragile, and are really easy to lose. Can't charge while using one either, but that's nbd. My car seats ate two and the last one broke. It also just feels stupid having to use these.
- Old iPhone. I kept my 6 until it broke. I still have a spare 5, no longer usable with AT&T, which I use to play music in the car.
Yeah I want to listen to music on my phone, but they've made it sufficiently annoying that I don't anymore. It's a clear regression.
Re: Google I/O 2023
#250Earlier quoted context omitted.
I built a business that did $80m of (profitable) revenue, in the first year. We were profitable after 3 months. Is that not a startup?
Your company was new. But the situation you describe is not typical of a startup as commonly understood.
In other words, our success was because we identified a critical missing piece in a profitable industry and built exactly what people were asking for, and more importantly, willing to pay for.
After that success (and a couple more after it), I refuse to ever build something without finding customers first. You have to build products people want, not try to convince people into believing they want your product.