Make Cloud UI fast is probably not their priority. This is an enterprise product, not consumer facing, users are much less likely to be turned off due to slow UI. They will wait.
Integrity/Security would be much higher on the list than UI loading speed.
>This is an enterprise product, not consumer facing, users are much less likely to be turned off due to slow UI.
Shouldn't this be the opposite? Maybe this is just me but if I have to use something to do my actual job and it take more time that it should because of the UI I'd look elsewhere.
Not the opposite, but we're missing the simple fact that enterprise products would rather get more features out over micro optimizations. There are constantly clients bringing their demands for additional features or major fixes, very rarely are they "please optimize the UI". For consumer facing products, that's not really the case, unless some massive features are missing, they would rather things be snappy as they tend to be extremely distracted at all times so dropping your app/site/whatever is no big deal.
During work, what else are you going to do if Cloud UI is slow besides just wait? Go through the entire process of trying to convince management to make a switch because UI is a little clunky? Good luck with that!
> enterprise products would rather get more features out over micro optimizations.
I've been using logs, bigquery, dataflow, and a smattering of other products pretty regularly for the past few years.
Are these products getting "more features"? Hardly. Well, dataflow deprecates minor SDK versions every month, so you have to run twice as fast just to stay in one place.
Instead, they have been redesigning the logs interface with fancy animations. And for the longest time ever they removed features from it like streaming logs.
Meanwhile the minor stupid things like displaying dates in MM/DD/YYYY format in date pickers, using AM/PM for time? Oh, they stay on. Graphs that work half of the time and you can never know if they are broken, cached, or just don't work? Oh, they stay on.
It's Google's systemic organisational failure: they suck at UIs, they don't care, and they couldn't be bothered to maintain features because "oooh, shiny new thing looks better on my resume".
I don't entirely agree... Material Design is pretty great imho and I like most of their UI choices (for applications that seem to sometimes get priority).
I think what this comes down to, is that their best technical minded developers are busy working on tooling, platforms, systems or other lower-level development. Their best design focused developers on public facing applications. This tends to leave the most junior of developers working on internally facing developer UIs. The payloads themselves are irresponsibly large on this application to say the least, and the ability/skill and understanding needed to make it better are probably not within the team(s) working on this UI to begin with.
Personally, I absolutely hate Angular and it's ironic that Angular's chosen primary UI toolkit @angular/material gets roughly half the downloads of the third party material-ui for react. Not even counting boostrap adapters.
Most web applications can easily be done in JS with an initial JS payload of ~500k-1mb (download size, compressed), with code splitting can have payloads for different areas/components come up as needed. Charts is probably the biggest beast that is practically impossible to tame, there have been a few times that I just generate the SVG directly in a React component to save the overhead of using a charting library, which is surprisingly easy to do.
- Inconsistent use of their own guidelines: https://grumpy.website/post/0Ra93yy33 (references the old design of the site, but the new one is just as bad)
- Or the hilarious story where they needed a user study involving 600 people to tell them that if a text field doesn't look like a text field, people won't be able to tell it's a text field: https://medium.com/google-design/the-evolution-of-material-d...
And that's just off the top of my head.
But all of that could be forgiven if Google bothered or cared. They don't.
I know that some of the details above are worth calling out. In terms of usability, it's important and that is as much an implementation detail as it is a design guideline detail.
Regarding the buttons, I agree they should elevate on hover and press down... with the animation for the click radial effect. Touch interfaces with just the radial click indication.
For the survey/study, I'm not convinced this is a bad thing. Actually interviewing with people to determine what works best should be actively encouraged.
This also isn't to say that I think google proper really cares all that much. I'm pretty sure their UX designers are treated like second class citizens in their engineer focused culture, let alone those that cross between UI/UX and engineering.
I also want to differentiate between "Material Design" the guidelines and "Material UI" the react component library. It's probably the single best component library I've ever worked with, which isn't saying too much as it's not perfect, just better than anything else I've seen.
edit: the main point was that Google's blessed implementation for their UI design framework is less used than a third party implementation for another framework.
I think it's more that people care about the speed of the actual cloud offering, not the internal control panel. The product isn't the control panel, it's the cloud services.
They're not saying it's ok. They are saying that the overall system (the business-business-management-employee complex) prevents optimization of this UI from being a priority.
>"I'm at work for 8 hours a day so it's ok if some time is wasted, there's plenty of it!"
that is how enterprise employers treat their employees. The time is wasted everywhere. Slow Google UI is just a one item in the long list, so no one of those enterprise customers would give Google a headache over it.
> I have to use something to do my actual job and it take more time that it should because of the UI I'd look elsewhere
The one who made the decision to use GCP would not be the one who would use it actually. If GCP offers a bigger cut than other Cloud providers, loading time would be irrelevant in that optics.
Enterprise users are risk averse. Speed is definitely a plus, but they would care more about stability/predictability than anything.
Only if you have a choice. Most people don't have a choice of what tools to use, they are dictated by their employer. And employers may have other priorities (e.g. checking off "serverless" on their bullshit-bingo-card before the next board meeting)
People who use this product largely don't interact with the web ui, a lot of things are only done occasionally. And the people that use it frequently won't use the web ui, command line tools or a third party program that abstracts that away is more likely.
Also the AWS web ui has a lot of the same problems, so switching vendors wouldn't just fix the problem
M$ is back, baby.
I would invest in them if I invested in huge-market-cap companies.
After IBM, Microsoft became the company selling Windows and Office for businesses. Huge cash cow. They lost that for a while due to the iPhone and Google and stuff moving to the Web and mobile.
Now they’re back.
The fonts and aesthetics remind me of using Windows apps 20 years ago. This ain’t Google. Small, crisp verdana, tahoma or whatever.
Meetings done right.
Office - Word, Excel - integrated. Tons of plugin support.
Compared to Slack, this is way better. And compared to Google Suite, well... Teams is faster and actually feels like a product teams would live in day-in and day-out. No need for slack, zoom, gmail and a hodgepodge of other things.
Microsoft also has a huge cache of businesses who would literally onboard their entire company and pay monthly recurring revenues. They have successfully gotten back into the Microsoft Office business.
Except this time it’s recurring revenues and on the mobile too. Even if Microsoft doesn’t sell mobile devices. They are going to eclipse Google with businesses if Google keeps doing its cute slow Web based interfaces, imho.
And I say this as a person who has not used Windows for 15 years, who hardly ever used Office or Office 360 until literally trying Teams as part of a consulting gig.
Agree. But try doing a video call in a channel in a team in Teams, and watch everyone in the team join, not just the people in the channel. At that point you won't miss just starting Zoom so much.
I happen to like MS Teams a lot... was very happy to see Linux getting proper support earlier this year, similar for o365. If you run a company with more than a handful of users, worth the price of entry imo.
> 80% of professional musicians can't make a living
It might hurt people's feeling, but most of those are not professional musicians.
I don't think it is judgemental to say that to claim oneself as professional, one need to demonstrate that they could make a living out of it. Otherwise, it is no different than a hobbyist, albeit much more time is dumped on it.
In case of streaming, now more people can declare themselves as musicians, since the barrier of publishing has been significantly lowered comparing to physical CDs. But that doesn't mean profit would follow.
To produce hit music isn't easy, and luck is certainly a factor of it.
I think too many non-musicians believe this is a case the population being comprised of a small number of professional musicians and a huge number of untalented hacks.
The reality is that there is while there are a lot of hacks and untalented musicians alongside the professional musicians, there are also actually a ton of talented musicians that are working very hard to write, record, and release music, and just simply never get heard. They submit to pandora or Spotify or wherever and it never makes it into the algorithms. It's up to them to do all their own marketing. We're influenced by survivorship bias and it's easy to say "they should just tour and play out and submit to music blogs!" and it's difficult to communicate just how hard it is to find any traction at all.
I personally don't have strong opinions on a solution, because I think it is a very hard problem. A lot of people that listen to music don't have any interest in discovering new music, or finding music that is a distinct match for their unique personality. They're just happy to listen to what is shoved in front of them. But if you change your approach away from what is good for each listener, and more toward what is good for a healthy culture, then maybe that starts suggesting some paths. I'd personally like it to be more of a combination of aggressively introducing people to new music, making hard not to rank/react to music, and heavily rewarding artists of new music that yield positive response. I also think there should be a form of progressive redistribution of the power law. Just because there's a power low doesn't mean the slope can't be flattened a bit.
How much did they earn from their music prior to streaming?
Musician for most isn't a job that sustains your livelihood, to speak the truth. Most musicians takes it a passion driven side gig besides their regular day job.
Google cares about AI ethnics because talking about it gives those people, especially higher ups, an imagined sense of significance and adrenaline rush of being a savior.
But in reality, AI ethnics is just a gloried showroom of diversity/inclusiveness.
It is not a product, it doesn't generate revenue, in corporate world, nobody cares.
> revealing the identities of every person who Megan and I had spoken to
Big red flag. Why are the identities of reviewers important here? Did she plan to take those reviewers to the court of public opinions for a trial/exposure?
A lesson is delivered in time IMO. Those entitled people need to be called out.
To limit the scope, and type of applications people should use Lambda for and Lambda is best at running them.
15 mins max runtime simplifies the resource management and avoid abuse. If you have workload for long running jobs, then that should go to something like AWS EKS/Batch/SageMaker.
That being said, things can change, if more and more people requires long running capacity for Lambda (though I am skeptical of that, as Lambda abstracts the underlying hardware away and is supposedly flexible to the requirements)
Wake up. With a president actively trying to overturn election outcome? Attacking the very system that puts him in power 4 years ago? No, the world is watching, and they are not stupid.
He's closer than you'd think. The US constitution gives state legislatures virtually unchecked authority to choose their own electors regardless of what state laws or courts say, without needing any other justification (eg. no evidence or even claims of fraud required).
Some, if not all, of the legislatures of PA, MI, GA, and WI will be sending their own GOP electors.
Those electors arguably take precedence over electors chosen by other legal processes, like democratic votes, according to the US Constitution. Because this issue does not concern state laws (or fraud allegations) whatsoever, the matter will go directly to federal courts.
Looking past the smoke screen of poorly supported fraud allegations and popular reporting's misdirected focus on the obvious lack of merit of said allegations, last night's impromptu PA legislative hearing was a major turning point in this situation.
PR is for immigration and China isn’t an immigrant country.
I agree however not a lot westerner immigrated China in masses. I don’t think you would live a normal life there without knowing Chinese, it will be painful. The immigration policy is mostly nonexisten, which by itself says a lot about the government's attitude towards foreigners in general.
On the other hand, China could be attractive place to gain experience with, it is vast complex and completely different from the West.
Make Cloud UI fast is probably not their priority. This is an enterprise product, not consumer facing, users are much less likely to be turned off due to slow UI. They will wait.
Integrity/Security would be much higher on the list than UI loading speed.
Not surprising at all.