...that's called "vendor lock-in". Vendor lock-in is when a proprietary format means you're stuck without requiring a great deal of time/effort/money to switch. I once used a new scheduling program and wanted to switch to another. I learned the vendor had gone out of business in the meantime and the export data function was "unimplemented" when I tried to use it. The format the data was saved in was also unreadable and proprietary. I had to run a new system and old system side by side for three months until I didn't need the data in the old one anymore; the only alternative would have been manual re-entry of it all. That's vendor lock-in.
MS has fought standards forever. Internal documents revealed at one trial against it declared that anytime a programmer developed for their de facto standards they "won" and anytime they coded for an open standard MS "lost" in their mind. They also wrote about co-opting standards; this is what the industry dubbed "embrace, extend, extinguish". For example: MS loved HTML... so much, in fact, they added their own custom extensions to the standard and encouraged developers to use them. What happened? A lot of websites that would only work correctly with Internet Explorer 6, which naturally people like you blamed on Netscape and switched to IE 6. MS tried doing this with Java, implementing a VM for Windows and then adding their own extensions here too. This broke the "write once, run anywhere" promise of Java and Sun successfully sued them over it. It's evil and pernicious and it's a symptom of a desperate need by MS to avoid ever having to compete. It's the reason Gates' biggest fear at MS was that other OSes would come into existence and MS did many things to kill of nascent mobile OSes, including breaking an NDA and announcing their own handheld (that didn't exist) to convince other software makers to hold off backing a startup's PDA and see what MS planned to offer, which ultimately killed off the start-up.
Linux didn't exist until the 1990's, so I don't know why it's stuck in the 1970s in your mind. In fact, Linux constantly evolves (new kernel releases about every six months, major distro and desktop releases every 6-9 months) so it's actually leading rather than being stuck. That's why Windows users have had to wait until the imminent release of Windows 8 to finally get native USB 3 drivers unlike Linux users, with Linux being the first OS to incorporate them. (Think it's not a problem? Try installing Windows on a set top box or thin client with only two USB 2 ports. Since the install disk doesn't have USB 3 drivers, you can only have a keyboard OR mouse during install since you need one port for the external drive and need to keep switching.)
Standards evolve all the time... HTML1-5, USB 1-3, ODF (open document format) 1.1 and 1.2, etc. Standards are ALWAYS a reasoned choice. As I illustrated above, not using them can leave you stuck. In fact, it's been suggested it's like nuclear power plants. When budgeting for them, the power company needs to incorporate the end-of-life cost of the plant: decommissioning, disposing of radioactive material, cleaning the site, etc. Sooner or later you're going to need to replace any piece of software. If it's proprietary, you similarly should include the cost of switching away from it in your total cost of ownership projections (rather than in the cost of any new software). Now if you do that, the proprietary app often becomes much more expensive than using an app with an open standard or open source in the first place. It's simply best practices to use official standards wherever possible, and my mind boggles at anyone who thinks it's faith. If you were buying a house, would you be ok with the outlets being custom-shaped and only able to connect to the appliances that came with the house, only available from one (aging) vendor? That's vendor lock-in, and that's what you're championing. I'll take standard outlets and USB connectors over proprietary ones any day.