Remove localization

[greeeen-dev]

Localized support may be removed from Unifier pending an internal discussion among the team and feedback from the community.

Current state of localization

Unifier is ready to be localized, however progress on this has pretty much been little to none recently. Our localization team's current leader doesn't seem to be actively working on this much either, so unless someone is willing to take over as the leader and prove to us that localization is worth keeping, there's no reason to keep this.

Added complexity

Localization just adds more complexity and makes things much harder to work on and debug. Before we added localization support we could just hard code strings, but now we have to put them on a separate JSON file then write some method that fetches the string from that file.

Lack of demand

From what we're seeing, localization doesn't seem to be a highly requested feature. In fact, nobody in our Discord server ever requested it except for the localization team's leader (yes, the same person). So we're unsure if it's really worth maintaining a high complexity but low demand feature when we can put our resources towards other things.

---

Like with a lot of things we do with Unifier, we will consult the community before we decide to go ahead with this. It can have quite the impact, so I want to be sure we're making the right choice here.