This is actually untrue, you want to do as much as possible in the renderer process. The main NodeJS process is responsible for all user interaction, including mouse clicks and keyboard input. If you block the main process, the entire app will become unresponsive
For what my anecdote is worth, I have seen sentiment like this across lots of social media, and it has gotten louder since the protests in June. I have even seen echoes of it on Facebook Workplace, where there has been a clear and strong encouragement to become more 'antiracist'. I do not think that this is hyperbole.
I have one of these for work and it's the first Macbook I have used
I have never experienced this behavior on any other laptop I have ever used. When I ran into this for the first time, I was completely appalled, it is a horrible user experience
Unfortunately, the org as a whole has completely collapsed as the result of the GitHub acquisition. I wouldn't be surprised to see ADO be deprecated in 2-3 years in favor of GH
You navigate to the remote server in your browser to test your changes. You just need to save and refresh the page and the updated code is magically deployed to the page.
Same thing could be said for Microsoft, where employees were upset they were providing O365 and Azure to ICE, but there is no similar outrage directed towards the special China cloud they run
Not really sure what you are implying with the 'Big Brother' comment. The remote development servers are only used for writing/debugging code and not for other daily tasks. Even if they are tracking what tools/functions I am using on the server, what does that matter?
Personally, I have found remote development awesome because it enables engineers to start contributing to a huge product in the very first hour. No need to wait for the repository to clone, the dependencies to install, and the code to build before you can become productive.
I guess one area where I see custom styling as important is visual consistency between browsers. These updates only apply to Chromium browsers, so a sufficiently visually complicated UI might look good in Chrome, but bad in Firefox for instance.
I don't feel super strongly either way, but I think it is important to call out
I'd argue that the correct solution then is to have better support to style native components if designers are going to do it anyway.
Additionally, it is not terribly difficult to make a custom checkbox , for instance, accessible. It may require JS and ugly DOM, but I wouldn't say it's difficult.