What is the Legacy version of Matlab ?

I want to know legacy version of Matlab !

[Aquatris]

any version that is not the latest version is a legacy version?

[Star Strider]

MATLAB goes back probably >40 years. It inittially existed on mainframes (my first exposure to it was the mainframe version in 1990), and the first PC versions were in the early 1990s. (I first installed it on my PC in 1993, when it was distributed on a stack of 9 mm mini-floppies.) The documentattion was initially a large single softcover book, and a few years later a library with volumes for each Toolbox.

[Steven Lord]

What do you mean when you say "legacy version"?

Do you mean what versions of MATLAB are no longer supported?

Do you mean what versions of MATLAB can you get for free? [The answer to this question is none of them, though MATLAB Online (basic) does give you free access for a limited amount of time per month.]

If you have some other meaning in mind for "legacy" please clarify.

[John D'Errico]

I recall a version I got on a Mac floppy, in 1984, I think. At the time, it was still very much in a devlopment stage. I felt it to be less capable at the time than some of the alternatives. I did not start to use it at all seriously until around 1989-ish, which would have been roughly version 3. By then it was becoming quite capable, though still very limited. Things like sparse matrices (of huge value to me) were not introduced for some years yet.

Regardless, the word "legacy" could rightly be considered to be anything before the current one, but I have a feeling a better description is this one I found online:

"A legacy system is outdated computing software and/or hardware that is still in use. The system still meets the needs it was originally designed for, but doesn't allow for growth. What a legacy system does now for the company is all it will ever do. A legacy system’s older technology won’t allow it to interact with newer systems."

https://www.talend.com/resources/what-is-legacy-system/#:~:text=A%20legacy%20system%20is%20outdated,all%20it%20will%20ever%20do.

[dpb]

By that complete definition the old plant performance application still in use at a large generating utility running on a storehoused supply of old '386 machines under either OS/2 Warp or Windows NT isn't a legacy system. While it will never be updated in functionality, it still could be and could interact with other newer systems albeit mayhaps not everything.

[John D'Errico]

I would guess there are degrees of legacy-ness, but I'd suggest a legacy version is one a company no longer supports in any substantial way. If a bug is found impacting that legacy release, but has been fixed in more recent releases, then you just need to get a current release.

[dpb]

"...I'd suggest a legacy version is one a company no longer supports in any substantial way"

I think that's a much more better definition.

The version running under NT4 is dependent upon the old [D]CVFortran compiler. I kept an old 32-bit machine for 20+ years for the express purpose if the client ever did want to make model changes to match plant upgrades; the last plant-specific modifications I've made were somewhere in about the 2010 timeframe after a plant upgrade to a new FW reheater the existing model couldn't handle. Whether there have been other model changes after I completely quit the consulting gig I don't know, but I'd doubt it; not much going on in the fossil plant business any more excepting shutting down baseload generation in favor of unreliable sources.

On reflection, I guess the OS/2 version is definitely now a legacy version as I no longer have a compiler for it--but those plants could swap over to the NT version as the data files are identical.