its a feature not a bug. calling that drama is disingenuous. They are protecting their own instance from trolls that they don't have the tools / resources to handle. Don't like that they de federated? then join a different instance.
teams is already a slow buggy mess that crashes multiple times a day for me with many features not working, this is before I even get into the poor UI design. Moving to react is just going to make things worse. Really trying to convince my manager to stop forcing us to use it.
right trusting microsoft sounds like a great idea, just like when they bought github. last time i heard them say that the app actually boots up faster and is faster on average but anytime I need to send a file or do a screenshare or join a meeting it crashes if I'm unlucky, if I'm lucky it will just slow down and everything lags. It's not just me either, everyone on my team and even our client who joins in on our teams meeting runs into the same issue. Our solution for them is to actually join meetings via browser.
How is it objectively "better"? This depends on context. I am sure Dart is worse given a specific condition. I'm not bashing dart, but you cannot say that "A is better than B" without any sort of context to the statement. It's like saying "apples are better than oranges".
Dart is better in most respects. The standard library is light years ahead of JS's, the Dart tooling is fantastic, it has sound typing.
There are a couple of features that I miss from Typescript: the biggest by far is tagged unions.
But I would still pick Typescript for a web project for two reasons:
* The community is like 1000x bigger. Even though a lot of it produces extremely low quality code, there's still a lot more solid JS libraries than Dart ones.
* Debugging is slightly easier since the compiled JS code is essentially identical to you TS code. Chrome has pretty great support for Dart, but if you ever have to delve into the generated JS it is quite painful.
much less overhead setting it up, it can be both interpreted and compiled. Troubleshooting errors in dart is a much more pleasant experience compared to Typescript. Transpiled languages like Typescript has given me so much trouble over the years at work.
Not that TypeScript doesn't have it's pain points but having tried Dart on an Android application recently, there are so many things I dislike about the language and it's ecosystem compared to modern TS/JS. I feel like it would have been a lot better than JS when it came out but now it's painful to use in comparison.
Definitely my preferred route for building mobile apps now though.
I now actually prefer Dart for services and glue code on the backend. I'm so tired of dependabot yelling at me about my hobby projects every week that have yet another vulerability in one of their million dependancies. In Dart I make do with just a handful of deps, then build a binary and call it a day. I tried using Deno with TS, but binaries it generated where absurdly big, 70-100MB depending on the target platform. Also, Deno's --allow-X thing becomes tedious after a while.
Yes it's Object oriented, it was supposed to replace JS long time ago, but google kinda dropped the ball on that. I wish it replaced JS. Dart was almost dead for a long time but flutter kinda saved it. Developing on flutter for cross platform applications has been a joy to work with even though there are still a lot of drawbacks to flutter right now.
you can find their blog here where they talk about future releases and planned features https://medium.com/dartlang
that's like saying VHS vs betamax is subjective. VHS won but wasn't better. Or Minidiscs vs CD's. It's mostly due to marketing fails and people hopping onto marketing bandwagons and pre-estalbished products.
TS is more popular due to combination of google dropping the ball in defining the standards and getting others onboard with them cause they overestimated the leverage they have, failure at marketing it and how everyone is already bought into Javascript.
