aliases (long future) - A smooth way to propagate changes of unfortunate choices/decisions of the past

[GHNewbiee]

On the occasion of the views you have expressed in the last paragraph of the recent release 1.9.3 let me make the following humble remarks:

• Really, no one likes breaking changes, and first of all me!
• A change is worthwhile and must be made when it improves and corrects unfortunate choices/decisions of the past "whatever the cost is". The new users will find a friendlier syntactic framework. Aggregating small "problems" is like a virus. You will always carry it on you.
• The art is to find a way to make the change without setting it as breaking one and letting the time to play its role.
• I have found the implementation of future and experimental flags in this easy and approachable way a very good idea. At least, it is absolutely honest!

So, if you really want to correct any small imperfection of the past you could adopt another flag. For example: aliases or synonyms. This will assign old classes to new ones for long time in the future. For example:

tailwind.config.js

...
aliases: [
  {
    leading: lh,
    both: true
  }
  ...
]

By this way, there is not a breaking change; and let the people to use easier syntactic and memorable classes.

You could also give the option for both of them to exist at the same time, instead only the new one. So, you keep also backward compatibility! It is clearer than using configure to make permanent changes like w-1/5 to w-1_5 or w-1of5.

Just give the freedom to the project's clients/fans/users to choose how they want to work!