The community and developers should decide on one single way and improve that to a state, that a second way would not be required.
My understanding this is the goal.
I hope not.
Designer have long time ago already pointed out that most systems (software or not) have typically 3 kind of interaces to do the same thing.
-
an interface for beginners:
this is for first time users or thing you don’t do very often.
(The later might be the closing of a year accountancy. In a personal accountancy you do this once a year, so you need a lot of guidance to not make mistakes, especially if the mistakes are costly, like with a wrong accountancy ending of the book year that you should not tough afterwords.
Giving in an invoice using a wizard might be another one in such system for first time users. -
A system that is for people who are mostly experts and do the task multiple times a day.
An accountant does not want a wizard, she want a kind of spreadsheet behaving page where she can freely swap between fields in fill in everything in the order she wants. -
A third system where third parties can use a kind of API.
In the same example if you sell stuff on a website, that all the sales get automatically in your accountancy system. (And invoices are generated and printed automatically)
Where the this one might not be needed, in general it is considered a good practise to have the first two interfaces as they serve a different audience. They are also less confusing for beginners, as they don’t have to bother with the more advance stuff that advanced users can use.
Having two different interfaces for something similar looks hard to do and maintain, in practise it’s the opposite, as they both have a very distinct audience.