Earlier quoted context omitted.
I think Teams is exactly excellent because it allows you to secure your collaboration tool. Especially valuable post GDPR where you really don’t want your non-tech savy employers putting privacy data into some online Trello board, or slack/discord for that matter. The fact that teams is just part of your 365 platform is soooo awesome in non-tech enterprise that it’s hard to describe just how useful it is. But basical…
How is putting privacy data in Teams different from putting it in Slack?
The Horror of Microsoft Teams
251–260 of 344 posts
Re: The Horror of Microsoft Teams
#252I use both daily. I think the biggest problem with Teams can't be discovered by feature comparisons and performance metrics. Teams enables a company to "secure" the application in the same way other MS products can be. That makes the product easy to sell, but in practice, it prevents Teams from being an effective collaboration tool. If I want to create a new channel, I need to get approval from IT. If I want to invit…
I think Teams is exactly excellent because it allows you to secure your collaboration tool. Especially valuable post GDPR where you really don’t want your non-tech savy employers putting privacy data into some online Trello board, or slack/discord for that matter. The fact that teams is just part of your 365 platform is soooo awesome in non-tech enterprise that it’s hard to describe just how useful it is. But basical…
Re: The Horror of Microsoft Teams
#253Earlier quoted context omitted.
> What is it again that Microsoft is getting such accolades for? Visual Studio Code is fantastic. Visual Studio is great.
For what? Legacy desktop developing? We used Visual Studio daily. Everyone I speak to wants to switch to VS Code because we're tired of the laggy mess that is Visual Studio 2019. Even with no addons it stutters and micro-freezes all day long with medium-large solutions. Somehow VS Code, an electron app(!), feels snappier than VS a native app. We're just waiting for feature party (and nothing special, just managing pr…
Nothing on Windows comes close to C++ for UI speed (or any other kind of speed).
Re: The Horror of Microsoft Teams
#254Earlier quoted context omitted.
How is putting privacy data in Teams different from putting it in Slack?
I’m the wrong person to ask, all I know is that Microsoft, Azure and Offfice365 is on the government list of places we can put our data (which doesn’t go above NSIS level 3) safely and legally. Slack isn’t on that list.
Re: The Horror of Microsoft Teams
#255Re: The Horror of Microsoft Teams
#256I like it. The reason is that in my situation, large enterprise corporate setting, it's the best I can get. Believe me it's been a breath of fresh air.
I believe some teams have used Matterhorn or Slack internally but it was not necessarily 100% approved and not company wide
Maybe, I should but I don't think that the using one solution versus another is such a game changer. People rarely fight about email clients either.
Since we are subscribed to Office 365, I believe Teams is part of the package and it is likely an easier sell.
Pretty clearly, it shows the power of Microsoft and bundle. Also, I am also glad that the "new" Microsoft is really focused on providing better tools, and not stuck with Office/Sharepoint only.
Re: The Horror of Microsoft Teams
#257The Teams client is built on Electron? Why? Developers need to stop building slow applications. This is ridiculous. It's 2019 and software is slower than it was in the 90s. It must take an enormous number of CPU cycles to execute simple tasks in an Election-based app. It's just incredibly inefficient. I heard similar things about Slack – that it was built on Node, maybe Electron, and was dog slow, especially to open.…
It makes sense for Teams. The app is a chat client, sure, but it also contains the entirety of Office 365 and a third-party app platform. Chats can have tabs with Excel documents, wikis, polls, etc. By leveraging browser technology they have a platform that is incredibly extensible. Building that from scratch across iOS, Android, Windows and macOS is not feasible. And the benefit of having people reach to the tools a…
Building a few chat apps is not feasible for one of the largest software companies in the world ?
Re: The Horror of Microsoft Teams
#258Earlier quoted context omitted.
Who cares if an application's UI elements look the same across platforms? I want it to work on the platform I am using. I simply do not care what it looks like on someone else's platform, and I especially do not want to pay a performance penalty so some designer can have a virtual feather in their cap over it.
> "Who cares if an application's UI elements look the same across platforms?" Designers. End users simply want a functional, working product. Polish on top is a nice added bonus, but these days it's been turned into the focal point of software development. A Teams/Slack-caliber project begins with product requirements, immediately followed by design and UI mocks - the software/tech always comes last.
A computer program is a tool to convert data from one form to another. FULL STOP. Unnecessary added complexity, on top of that data transformation, is wasted effort, wasted time, wasted energy.
Software development has caused so many problems for itself because of things like this. People forget so quickly that programming is not the job! Solving the data transformation problem is the job. Effort spent that does not solve the problem is wasted effort, and we've made a fucking industry that churns out far more waste than product.
Re: The Horror of Microsoft Teams
#259Re: The Horror of Microsoft Teams
#260Earlier quoted context omitted.
My VS code was using 10 GB of RAM today... It's better than other electron apps, but I would argue still not efficient
Did you open a 10GB file in it? Mine is using 200MB right now with a PHP project open in it.