That said, anything closer to VS Code will likely be perceived well.
That said, anything closer to VS Code will likely be perceived well.
Citation needed
Personally I have the opposite reaction to people cloning the VS Code UI: I find VS Code's model absolutely awful for most things, and even assuming someone _does_ find it useful, most attempts I've seen to clone its UI don't even come close to matching up to the quality of the original.
I'm not sure why someone would ever have positive perceptions of an application trying to shoehorn itself into a competitor's UI to capitalize on another project's popularity.
If you insist on redoing the UI/UX because you think a different design is "better", then you should keep the old UI/UX as an option. But you're almost always better off not redoing it.
For software that doesn't have an existing UI/UX, the best UI/UX is one that your potential users are already familiar with. Specifically, one that resembles whatever other programs on your target platform do. The reason for this is because your users are already using those other programs and are familiar with how they work so doing something different for the sake of being different will confuse them (this is why its good that gaming controllers and control schemes in games are largely standardized these days). If you're emacs or vim, it makes sense to stick with your archaic shortcuts because your users expect them and would be confused if you changed them but new programs should stick to ctrl+s for save, ctrl+x for cut, ctrl+c for copy, ctrl+v for paste, etc.
It's the same with MS Teams. A bad, sluggish program full of bugs and weird behavior that is only the most used conferencing software because it is included in the Enterprise Office subscription anyways.
This might be true. I wouldn't stop using it because I dislike it though. Only that if I'm going to give money, I'd rather do it to pretty much any company that's not Microsoft. I would probably pay for JetBrains stuff at that point, even though I could never get used to their products.
> It's the same with MS Teams. A bad, sluggish program full of bugs and weird behavior
Teams is the worst. VS Code OTOH is not bad (subjective, of course), definitely not sluggish (it's faster than emacs on my laptop, except when opening it the first time - which happens at most once a day) or full of bugs (at least none that get in the way of me doing my job efficiently).
Although to be honest I kind of pay for it more for the git integration than the editor (especially as the non-official Elixir plugin is not that great) and I guess they won't change that.
Even AWS console goes through changes.