Google is a very large company. They have capital on hand and an established, well-worn process for onboarding. It costs them comparatively little to hire.
For a small company, an engineering hire is a big investment. They don't do it as often, so it costs them more in terms of both direct costs and indirect costs - like the time it takes their existing team to go through the process and bring the new hire up to speed.
Oh, I don't know - it could be useful for long-running and/or background tasks in some cases.
The problem is that this particular model is so cheap, compared to others. Optimizing to host it locally with relatively poor performance just doesn't make sense when yesterday I burned ~180M tokens for $2.20.
Surely local hosting is not so much about cost savings as it is about data ownership and risk management. e.g. can't leak a secret if you're not calling out.
This sounds like a fun project, so I went ahead and threw my personal agent at it. I’m having it put together a summary as well, and will reply to this comment with it later if I remember.
If by chance I happen to break it, I’ll be sure to make contact with you and forward the logs I have, and perhaps let you chat with my agent if you’d like to see what it did.
> It is the best selling tablet brand, but that doesn't mean much when you look at the absolute garbage the rest of the industry is putting out.
That’s where I am.
I love my iPad, because I love the tablet form factor. I used an Android tablet for years prior to the iPad Pro releasing, and iPadOS is much better. I’ve played with Android tablets periodically since but they don’t seem to care about the form factor at all.
Just because it’s the best doesn’t mean it’s good, though. I don’t understand how they can justify selling a $300+ keyboard for a $1,700 device and never fix long-standing bugs with keyboard use, much less continue to add regressions in new releases that aren’t fixed.
iPadOS 27 broke many keyboard use cases for me, including very simple things like using tab to move to the next field on a form in Safari. It worked in iPadOS 26, but doesn’t now.
This adds to the bug where switching between apps with modifier keys tends to cause those modifiers to “stick”. That bug has been there for years, and prevents me from using my iPad as a programming environment even though the software support is there.
Agreed - and I actually went up the 13” iPad Pro this time around specifically because I wanted to see if window management was better on it. It’s not.
I gave it a try on a 32" 4K monitor with mouse and keyboard for a few hours. To see if I just need to get used to it, and if I'm just too dumb to get it without practicing. I figured out all the quirks and it still sucked.
It's also incredible how many window arrangements features they added (long press on the green button, next to the red X to close the window). Most of them are completely useless.
I’ve worked on a slaughter floor before, and while it’s certainly not an enjoyable experience I can say with all honesty that a great deal is done to minimize suffering.
Google is a very large company. They have capital on hand and an established, well-worn process for onboarding. It costs them comparatively little to hire.
For a small company, an engineering hire is a big investment. They don't do it as often, so it costs them more in terms of both direct costs and indirect costs - like the time it takes their existing team to go through the process and bring the new hire up to speed.
reply