One thing I have found in the past with editors focusing on collaboration and connectivity is that they are very frustrating to use when network connectivity is bad or non-existent. They throw error after error about not being able to check for plugin updates and not being able to sync files and not being able to open chat and whatever else. The more connected the editor is the more frustrating it tends to be to use in local only mode when the circumstances call for it.
In order to be truly robust, I think all the run time features that rely on/expect/check for network connectivity should respond to some sort of run time flag (CLI flag or ENV var) that sets an offline status. This would not only suppress errors and warnings but not even try to make connections for any reason.
One thing I have found in the past with editors focusing on collaboration and connectivity is that they are very frustrating to use when network connectivity is bad or non-existent. They throw error after error about not being able to check for plugin updates and not being able to sync files and not being able to open chat and whatever else. The more connected the editor is the more frustrating it tends to be to use in local only mode when the circumstances call for it.
In order to be truly robust, I think all the run time features that rely on/expect/check for network connectivity should respond to some sort of run time flag (CLI flag or ENV var) that sets an offline status. This would not only suppress errors and warnings but not even try to make connections for any reason.