this discussion that asks for complete removal, it seems that most people would actually not want to see them removed at all, but instead they would like to see the editors disabled by default.
Read-only archive: https://petitions.classicpress.net/posts/93/theme-plugin-editors-disable-by-default
Author: Pieter Bos
Vote count: 52
My was a follow up from other discussion, if we want to keep compatibility in wordpress we need to have the same system and people disable the stuff that are already available. So better not disable by default but leave to the people to disable it.
~ posted by Daniele Scasciafratte
I wonder if it would be useful to have a way to include the deactivation of this and other features during migration, as a previous step? We could then inform the user of the option about to be made, and give him/her the opportunity to decide. That is, if the “decisions, no options” bs is not kept in ClassicPress.
~ posted by Alvaro Gois dos Santos
I agree disabling by default with an option in Settings --> Advanced tab or something. Once enabled, I would like to see a lot more editor and coding tools so a developer can edit Themes and Plugin files. Once an edit is made, a flag should be set so that this appears in WordPress Themes or Plugins Update warning that a theme or plugin file has been modified.
~ posted by Damian Baker
This petition would be a good candidate for the “core plugins” approach we’re adopting for ClassicPress v2. The idea is that we’d move all the code for the theme and plugin editors out into a plugin that is shipped with v2 and enabled by default, but the plugin can be removed or deleted as users wish.
More details about this approach:
Whether we are able to modify this specific feature for v2 will be a question of available time. If this is something you’d like to see done, be sure to leave your vote on this petition. If you’re available to help with this, get in touch with us on the forums, Slack or GitHub.
~ posted by James Nylen