Earlier quoted context omitted.
I agree with this. Also how can they forget an option to “paste without formatting”? Copying stuff from other sources is extremely painful. At this point, I leave it as is. I don’t have time to micromanage each copy and paste. Also teams has this arbitrary message character limit that makes it terrible for sharing large chunks of text (partial logs for example). While the integrations with outlook (mail/scheduling) +…
Paste without formatting is Ctrl-Shift-V, isn't it? I don't know if I've ever tried it in Teams though.
Microsoft Teams 2 will use half the memory, dropping Electron for Edge Webview2
221–230 of 359 posts
Re: Microsoft Teams 2 will use half the memory, dropping Electron for Edge Webview2
#222Earlier quoted context omitted.
Everytime Electron is mentioned, VSC will be presented as counter example. The problem is VSC is the only snappy Electron app out there, Microsoft spend millions optimizing it, while most other Electron apps are crap. Native programs can be made snappy easily . That's the whole point.
But then with native you have to pay the cross platform price. Which is higher do you think? With Electron you get cross platform more or less for free and ostensibly you can make it faster later. Don't get me wrong, I love doing native work, but as someone who has to deal with cross-platform issues in native applications (well games) on the daily, I can tell you that even with massive code reuse and good interfaces,…
You could for example use Qt. It is cross-platform and if you write your application well, the amount of platform-specific code will be quite small.
>With Electron you get cross platform more or less for free and ostensibly you can make it faster later.
It's not for-free. The effort/work for the developer is reduced, while the amount of work for the users' PC is increased. Sure, a lot will think, that this is a great deal, but at in my opinion, you should do it the other way round.
How often have you seen electron apps going faster? I never did. With a native toolkit, you have performance from the beginning for the same quality.
Re: Microsoft Teams 2 will use half the memory, dropping Electron for Edge Webview2
#223Earlier quoted context omitted.
I agree with this. Also how can they forget an option to “paste without formatting”? Copying stuff from other sources is extremely painful. At this point, I leave it as is. I don’t have time to micromanage each copy and paste. Also teams has this arbitrary message character limit that makes it terrible for sharing large chunks of text (partial logs for example). While the integrations with outlook (mail/scheduling) +…
My trick for paste without formatting is to throw it in the url bar and copy it back out.
Re: Microsoft Teams 2 will use half the memory, dropping Electron for Edge Webview2
#224Earlier quoted context omitted.
I agree with this. Also how can they forget an option to “paste without formatting”? Copying stuff from other sources is extremely painful. At this point, I leave it as is. I don’t have time to micromanage each copy and paste. Also teams has this arbitrary message character limit that makes it terrible for sharing large chunks of text (partial logs for example). While the integrations with outlook (mail/scheduling) +…
Can somebody explain why "paste with formatting" is so widely the default option? I have literally never wanted to paste with formatting and neither have multiple family members who have needed help with preventing it from happening.
Re: Microsoft Teams 2 will use half the memory, dropping Electron for Edge Webview2
#225A few decades ago I paid about $1000 for a one MEGABYTE memory upgrade, and even that was needed only because a single graphics application at that time could clearly benefit from the extra RAM to do more things.
Now? I have 32 GIGABYTES of RAM, and we are celebrating that a chat client has now managed to find a way to use a slightly less absurd amount of memory, and has graciously returned some of our massive computing resources to us? This app barely does anything!! The apps that require all that power should at least be more useful...right?
As far as I can tell, every person on the planet is using more battery power and upgrading their machines more often just to make up for the laziness of software companies. In exchange for the ability of software teams to “easily” write one obnoxious cross-platform beast, we all get to burn through our CPUs and memory. These companies have more than enough money to invest in writing software for different platforms using the heavily-optimized system frameworks on those platforms.
Re: Microsoft Teams 2 will use half the memory, dropping Electron for Edge Webview2
#226Earlier quoted context omitted.
You can't even read stuff from other tenants if you are in a video call. Teams came for free at a lot companies I worked with and all of them have moved back to Slack and many of them are also paying for it.
My favorite about video calls is at one of my organizations I am access denied to recordings even when I participated in it. I can't attach images either. Someone built these features. Why are you building a feature on who can attach images?? The entire mindset is completely wrong and comes from an overcontrolling enterprise mindset completely incompatible with what we expect from a chat tool. Oh and every time I log…
Re: Microsoft Teams 2 will use half the memory, dropping Electron for Edge Webview2
#227Not sure what everyone issues are. I use Teams (in the browser) on Linux and it works fine under both X11 and Wayland (with some work). A bit less polished than Slack but it also has a lot more features. The worse thing about the desktop/Electron version is that they are really bad about keeping the electron version updated so the browser version will support screen sharing on Wayland while the desktop app doesn't.
Teams is more complex than Slack but also does more, but it's also not a complete superset of Slack, so unplanned/unguided transitions from Slack to Teams tend not to go well. Like any sort of knowledge management change, it can go well with empathy, planning, and care.
Re: Microsoft Teams 2 will use half the memory, dropping Electron for Edge Webview2
#228The fact that they market Xamarin/MAUI as cross platform and Blazer for web, and not use any of their tech to build a cross platform native/web app is laughable.
Blazor is very new & was considered experimental until recently. It's still fairly bleeding edge.
Microsoft started Teams in 2016 & bought Xamarin in 2016.
JavaScript developers are also more plentiful than Xamarin I assume.
They should choose the best tools for the job, even if it's not there own.
- Edit - It looks like WebView2 is a Microsoft thing based on their Chromium browser version. Super common for Microsoft to make multiple competing products that do similar things.
Re: Microsoft Teams 2 will use half the memory, dropping Electron for Edge Webview2
#229The fact that they market Xamarin/MAUI as cross platform and Blazer for web, and not use any of their tech to build a cross platform native/web app is laughable.
TypeScript is also there thing. They've been pushing React as well in SharePoint & other areas for quite a few years. Blazor is very new & was considered experimental until recently. It's still fairly bleeding edge. Microsoft started Teams in 2016 & bought Xamarin in 2016. JavaScript developers are also more plentiful than Xamarin I assume. They should choose the best tools for the job, even if it's not there own. -…
Re: Microsoft Teams 2 will use half the memory, dropping Electron for Edge Webview2
#230Earlier quoted context omitted.
Native apps means essentially building at least 5 distinct apps: windows, mac, iOS, linux, android. What a mess to work with and maintain. We already have cross-platfrom UI engines called browsers and they're very advanced and reasonably pleasant to work with these days. If you bundle the browser (electron) then you don't have to worry about differences between browsers. So electron makes plenty of sense to developer…
We also have Swing in Java which is mature, performant, and works across all our desktop stacks. Mobile UI is different enough that you need to write a different interface anyway.