It’s a way of thinking common with some engineers: the problems are supposed to simplify themselves to fit in their nice and neat solutions. It’s very, very common here. It’s almost cute to see it resurfacing every single time the opportunity arises. You can be certain that at some point, someone will advocate for a neat sexagesimal or hexadecimal system because division.
The world is what it is.
The world could be better.
The world still is what it is.
Your software not handling Roman numerals won't stop people from using them.
There are times when making a futile stand against It, which will neither stop It nor slow It down, is necessary for your own psychological well-being. If you draw that line at the existence of Roman numerals, well, go in peace. However, saying that Roman numerals are pointless and shouldn't exist and therefore your software won't support them is really only screwing over the people who rely on that software because you insist on trying to derive Is from Ought.
Yes, but it will make my software easier to write, grok and maintain, all things that are beneficial to handling the 99.999% of the problem space that doesn't include an ancient way of writing numbers.
People stopped using the þ and ȝ in English because the technology at the time couldn't handle it. People adopting new practices and habits to make it easier for technology is as old as technology.
There are few people who can read MCMXCVI fluently. It's not accessible for the majority of the population, with or without screen reader. Just don't use Roman numerals if you want your number to be widely understood.
There's always going to be a painful tail of slow adapters with standards.
No, but I do compare the amount and importance of occurrences in a problem space, with the amount of work and fallout the solutions to accomodate these occurrences will cause.