decoration decoration
Stories

GROKLAW
When you want to know more...
decoration
For layout only
Home
Archives
Site Map
Search
About Groklaw
Awards
Legal Research
Timelines
ApplevSamsung
ApplevSamsung p.2
ArchiveExplorer
Autozone
Bilski
Cases
Cast: Lawyers
Comes v. MS
Contracts/Documents
Courts
DRM
Gordon v MS
GPL
Grokdoc
HTML How To
IPI v RH
IV v. Google
Legal Docs
Lodsys
MS Litigations
MSvB&N
News Picks
Novell v. MS
Novell-MS Deal
ODF/OOXML
OOXML Appeals
OraclevGoogle
Patents
ProjectMonterey
Psystar
Quote Database
Red Hat v SCO
Salus Book
SCEA v Hotz
SCO Appeals
SCO Bankruptcy
SCO Financials
SCO Overview
SCO v IBM
SCO v Novell
SCO:Soup2Nuts
SCOsource
Sean Daly
Software Patents
Switch to Linux
Transcripts
Unix Books

Gear

Groklaw Gear

Click here to send an email to the editor of this weblog.


You won't find me on Facebook


Donate

Donate Paypal


No Legal Advice

The information on Groklaw is not intended to constitute legal advice. While Mark is a lawyer and he has asked other lawyers and law students to contribute articles, all of these articles are offered to help educate, not to provide specific legal advice. They are not your lawyers.

Here's Groklaw's comments policy.


What's New

STORIES
No new stories

COMMENTS last 48 hrs
No new comments


Sponsors

Hosting:
hosted by ibiblio

On servers donated to ibiblio by AMD.

Webmaster
"Fairly well known to go to absurd lengths to [maintain backward compatibility]" | 86 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
"Fairly well known to go to absurd lengths to [maintain backward compatibility]"
Authored by: Anonymous on Friday, August 17 2012 @ 12:09 PM EDT

An example of that is:

    Allowing an application to run in unprotected mode!
Granted: it's mostly games that "demand" that. And that's a feature that's been around since very early DOS.

But MS is also fairly well known for breaking compatibility even between two immediate versions. MS Access is an example that has experienced that in a number of places a few times.

I wonder if anyone has done any stats that one could point to and say something like:

    80% of the time backwards compatibility is covered, 20% of the time it is not, in 100% of the cases, backwards compatibility of some type fails.
That would be a rather good amount of research and testing involved, which probably breaches MS' EULA unless you get their permission to disclose the data. And I certainly wouldn't rely on any stats generated from survey's. Human memory being what it is, most people will fall into one of the two following groups:
    Dislike of MS backwards compatibility (BC) and therefore fails to mention where the BC actually works.
or
    Like of MS and therefore fails to mention where the BC actually fails.
In short - memory recall will mostly be tainted by which side of that particular fence one falls on. Disclaimer: I fall on the dislike side.

So with that taint in mind:

My humble opinion based on experience I remember: When you're talking specifically of MS Word, going back two versions to properly and fully read in the document is iffy at best and three versions is pretty much expected to fail in at least a few ways.

RAS

[ Reply to This | Parent | # ]

Groklaw © Copyright 2003-2013 Pamela Jones.
All trademarks and copyrights on this page are owned by their respective owners.
Comments are owned by the individual posters.

PJ's articles are licensed under a Creative Commons License. ( Details )