I have the same feeling about any kind of integration. We're moving away from Google because we simply do not want to have this kind of forced relationship with products and/or services. It either fits and we'll pick it or it does not and then we don't. We won't pay for things we do not intend to use. And we don't want exposure to products that may constitute a security or a privacy risk.
replyThe forced Workspace price hike to "get" Gemini felt like the beginning of the end.
replyDo you know what you'll be moving to to replace what Workspace provides (email/IdP/calendar/Chrome policy management?)
Email and document collaboration are the big ones, email is probably going to be the easier one of those two, documents much harder because we have a pretty specific workflow that is tied closely to how google docs works. But the decision has been made and I don't care if it is going to cause us to have to work a bit slower or different, this is just unacceptable.
replyThe whole Gemini thing is just a massive embarrassment for Google I really can't follow their thinking, you'd think that after the Google '+' debacle that they would have learned their lesson not to cannibalize your old products to launch a new one.
I actually think Gemini Pro is great and I don't have a problem paying for it, but I don't want its tendrils in Drive and Gmail or anywhere else, it actively damages the product experience there. Everywhere they've tried to integrate LLMs, it generally provides an experience that's inferior to just chatting with Gemini.
replyThe closest to useful it's been is in the GCP console, but it seems to decide at random to forget context, and it might just be Gemini Flash with minimal thinking, which tends to mean it's just repeating things it's already said.
What about office 365 that became Microsoft copilot 365 ? Talk about shoving copilot down the throat lol.
replyWhat actually _is_ copilot? Is it a set of office programs? A plugin for VS code?
reply