2 ms·
I don't think it's messy. Year-Month based version scheme is most recognizable one. What's bad for Windows (or Microsoft) is that they think the version shouldn
by fomine3 5y ago
I don't think it's messy. Year-Month based version scheme is most recognizable one. What's bad for Windows (or Microsoft) is that they think the version shouldn't duplicated to previous product (like Windows Embedded POSReady 2009 or Office 2010) so they changed to 20H2. Such duplication should be expected from the beginning.