4 ms·
Kinda agree. But then they failed to make the "One account all of Google" true of Gmail and Gsuite accounts (there's a long list of things you can do with one
by buro9 7y ago
Kinda agree.
But then they failed to make the "One account all of Google" true of Gmail and Gsuite accounts (there's a long list of things you can do with one account that you cannot do with the other, and this is with Google products and features).
So it doesn't feel suprising that Google lacked the organisational-wide impetus to get this working fully for Windows and Microsoft products and features.
These kinds of projects need to be driven with very strong vision from above. It makes me think of the Yegge rant about platforms at Google, and the mentioning of the Bezos mandate on APIs https://gist.github.com/chitchcock/1281611 https://gist.github.com/chitchcock/1281611
His Big Mandate went something along these lines:
1. All teams will henceforth expose their data and functionality through service interfaces.
2. Teams must communicate with each other through these interfaces.
3. There will be no other form of interprocess communication allowed: no direct linking, no direct reads of another team's data store, no shared-memory model, no back-doors whatsoever. The only communication allowed is via service interface calls over the network.
4. It doesn't matter what technology they use. HTTP, Corba, Pubsub, custom protocols -- doesn't matter. Bezos doesn't care.
5. All service interfaces, without exception, must be designed from the ground up to be externalizable. That is to say, the team must plan and design to be able to expose the interface to developers in the outside world. No exceptions.
6. Anyone who doesn't do this will be fired.
7. Thank you; have a nice day!
When it comes to making the experience right for Google accounts (of any type, anywhere)... this is what it takes. But this is precisely Yegge's rant, Google lack this.
- izacus 7y ago> But then they failed to make the "One account all of Google" true of Gmail and Gsuite accounts (there's a long list of things you can do with one account that you cannot do with the other, and this is with Google products and features). The clients of GSuite explicitly do not want any of that - even more, they (and the media and HackerNews) is very vocal that GSuite data should never be merged or touch the GMail account data, ML advertising systems and other non-enterprise data. Did you consider that perhaps you're not the target market for these kind of features? It is an Enterprise cloud system after all. (The arbitrary GSuite limitations are pissing me off as well though.)
- Already__Taken 7y agoThat's not true, We want the same products just with a work/home divide. I can't use a google home mini in the office because I can't add other gsuite accounts like a family can. That's so arbitrary.
- snazz 7y agoPart of it has to do with the different data protection regulations and privacy policies between consumer and business Google accounts. Since very few enterprise customers use consumer smart home products, Google doesn’t want to make a special version that respects deletion policies and legal holds.
- buggeryorkshire 7y agoThe OP wasn't clear, but I think I know what they mean. Years ago they offered Google Apps For Your Domain (GAFYD) - this was a normal Google account, but with your domain on it. I had one, probably for around 15 years or so, as did many other adopters and fanboys. GSuite came around, paid, and the GAFYD stuff became free GSuite account. This is where the problems started - we didn't want GSuite, we wanted a Google account on our domain with the same services. Hell, I didn't even mind paying GSuite prices, but what I did mind was services didn't work. So a few months ago I spent 3 days moving stuff from my GAFYD account to a normal Google one. Plenty of stuff is lost - photo metadata and free Pixel storage, Assistant functionality, tonnes of these things. All could have been avoided had Google bothered to write a conversion for this, but they didn't bother as usual. So, yeah, your GSuite clients may not want that - understood. However some of us were grandfathered into the GSuite limitations without a route to getting back out.
- notRobot 7y agoPlease don't use code blocks for quotes. It makes it very hard to read text on mobile, narrow viewports or via screen readers.
- mcny 7y agoA better solution is to have the client wrap long lines, break word ideally.
- cowsandmilk 7y agoAnd that's exactly that is done if you don't use code blocks for quotes on hacker news...
- bluGill 7y agoWhen you tell the client not to do that, then don't be surprised when people complain that their client didn't do it.
- jasonjayr 7y agoI see this comment all the time. Besides my bias against mobile, can HN add a blockquote syntax or fix it so mobile users have feature parity with desktop users? Is there a reason why this hasn't been done yet?
- detaro 7y ago> IMHO this works quite well as quote syntax don't you think?
- gomox 7y agoMost absurd missing feature ever. I tried to get some support for the feature request a while ago but got no attention [0]. I feel like every day I bump into this issue at least once, and there's always someone saying "don't use code formatting for quotes". My next step was going to be a Twitter bot that tweets when someone posts a quote with long lines in code format on HN. Haven't gotten around to it yet. [0] https://news.ycombinator.com/item?id=18162599 https://news.ycombinator.com/item?id=18162599
- cameronbrown 7y agoFrom my limited perspective, Google struggles with top-down commandments from leadership, of which the biggest one was Google+. Look how that turned out..