YUyuhong·Jul 24, 2016Submission
Change the license of Open Watcom
1 points · Open discussionopen-watcom
open-watcom-v2
C2016–2026
open-watcom / open-watcom-v2
open-watcom-v2
Open Watcom V2.0 - Source code repository, Wiki, Latest Binary build, Archived builds including all installers for download.
13Distinct people
19Mentions
1Explicit recommenders
1.3KGitHub stars
What to know before exploring
What it is
Open Watcom V2.0 - Source code repository, Wiki, Latest Binary build, Archived builds including all installers for download.
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
I do some light hacking in iDOS for fun as well. Might as well go straight to Borland C++ 3.1 [0] (the "professional" version) over Turbo C++ these days. When you eventually…
mezentius used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
- jwasm/jwasm · linked in 2 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 6:01:08 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year19 dated mentions
Observed mentions: 2016-07-24 16:45:09 UTC to 2026-10-01 00:29:08 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 2 | 1 | 1 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 3 | 0 | 3 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 3 | 0 | 3 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 3 | 0 | 3 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 3 | 0 | 3 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
2 sourcesOlder version of x86emu do not execute some 32-bit instructions properly such as LEA and CALL/RET, and gcc generates some of them. Open Watcom can generate true 16-bit only code that avoid these bugs. Unfortunately while the license is OSI-approved it is not FSF-free. This is interesting because it raises the question of which kind of "private use" restrictions disqualify the license from being "free software". But more importantly it is not DFSG-free either because of other reasons. This is why VirtualBox had to be moved to contrib. I have posted an GitHub issue about changing the license: https://github.com/open-watcom/open-watcom-v2/issues/271
In Emulate “leal” instruction to workaround x86emu bugs [2015]