3.1 KiB
Write a factual article for a computer‑museum website about the software specified at the end of this prompt.
Use only verifiable information from Wikipedia, period magazines, manuals, corporate filings, and reputable computer‑museum or archival websites. Do not invent or infer any detail that is not explicitly documented in the sources. We are writing a new article, not copying Wikipedia, so use a variety of sources and do not rely too heavily on any single one.
Museum‑grade multi‑source requirement: The article must synthesize information from multiple independent, reputable sources, such as period magazines, manuals, archival documents, corporate filings, and museum collections. No single source may dominate the narrative, structure, or factual basis of the article. When multiple sources disagree, present only what is verifiably documented and avoid resolving contradictions unless a source explicitly does so. If all surviving information originates from a single source, you must state this explicitly in the article and restrict the content to what that source documents, without extrapolation or inference. The resulting article must read as a historical synthesis, not a reformatted version of any one reference.
The article should include the following topics when information is available:
- History and development timeline
- What the software is and what it does
- Origins, motivations, and early context
- Reasons its developers created it
- Key design, architectural, or strategic decisions
- Major innovations introduced by the software
- Announcement details
- Launch details
- Impact at announcement, launch, and throughout its active life
- Influence on computing, the market, users, competitors, or later software
- Standards followed, contributed to, or introduced
- Geographic or regional differences (if relevant)
- Financial context (pricing, licensing, funding)
- Developer or community ecosystem
- Decline, transformation, or discontinuation
- Legacy
Citation and reference requirements (STRICT):
- All citations must be inline Markdown reference-style citations.
- Each citation must correspond to a single entry in a “References” section.
- Each entry must be a Markdown reference definition with a single real URL.
- No placeholders, no empty links, no text-only citations.
- Only one URL per reference key.
- No uncited references.
Uniqueness and deduplication rules (VERY STRICT):
- Deduplicate all sources internally before writing.
- No repeated URLs in the References section.
- Multiple statements from the same source must reuse the same footnote key.
- Do not create new keys for the same URL.
- The number of references must equal the number of unique URLs.
- No more than one reference entry per URL, domain, or page.
- URLs differing only by parameters or fragments count as identical.
General requirements:
- Continuous prose; no schematics.
- Tables allowed when appropriate.
- Omit any section with no documented information.
- Clean, raw Markdown. No emojis. No images.
- Focus strictly on the specific software version requested.
Now write the article about: XXXXXXXXXXXX