HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
rochus-keller
Oberon
C++2019–2026
rochus-keller / Oberon

Oberon

Oberon parser, code model & browser, compiler and IDE with debugger, and an implementation of the Oberon+ programming language

9Distinct people
71Mentions
0Explicit recommenders
557GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Oberon parser, code model & browser, compiler and IDE with debugger, and an implementation of the Oberon+ programming language

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 4:43:50 AM UTC.

Show HN: Micron – Oberon with the Power of C direct repository linkFavorable

The discussion highlights appreciation for the Micron language as a modern, practical evolution of Oberon that successfully integrates C-like power with rigorous type safety and single-pass compilation heritage. While users praise the comprehensive examples and clear textbook, a substantive debate emerges regarding whether prioritizing simple, fast compilers restricts access to advanced features like dependent typing compared to more complex modern systems.

24 readable replies · Supporting reply 1 · Supporting reply 2

Mentions over time

HN mentions by year71 dated mentions

Observed mentions: 2019-10-30 16:57:11 UTC to 2026-09-25 15:02:32 UTC.

0510152019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 10 mentions; 1 submissions, 9 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 14 mentions; 8 submissions, 6 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 11 mentions; 3 submissions, 8 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 8 mentions; 0 submissions, 8 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 9 mentions; 0 submissions, 9 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 11 mentions; 0 submissions, 11 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 7 mentions; 0 submissions, 7 comments. Incomplete calendar period.2026*

* 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
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC101
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC1019
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC1486
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC1138
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC808
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC909
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC11011
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC707

What Hacker News says

8 sources
> Regardless, which one is more likely to be ported to a different architecture in the future? Not sure I understand the question. I'm talking about CPU architectures. The current implementation is in x86 assembler. So if you want to run it on AMD64 or ARM, then you have to replace all assembler files, in the present case probable the full source code. > what are the comparative performance benchmarks of the low-level language versus the high-level language? I don't have any measurements. But consider that many operating systems are implemented in C (e.g. Linux) with only isolated parts in assembler, so it is easier to port to other architectures. Linux apparently is fast enough and available for nearly every CPU. Oberon in contrast to C is garbage collected, which also affects performance. I have measurements comparing the same benchmark
Read the rest
suite implemented in C++ and in Oberon, where the former is about 22% faster (see https://github.com/rochus-keller/Oberon/blob/master/testcase...).
In KolibriOS on Single Floppy Disk
> annoying aspects was requiring the .NET runtime ... OpenJDK is a blessed implementation in a way that Mono never was Which is unjustified, because Mono CLR is just a single executable less than 5 MB which you can download and run without a complicated installation process (see e.g. https://github.com/rochus-keller/Oberon/#binary-versions ). AOT compilation on the other hand is a huge and complex installation depending on a lot of stuff including LLVM, and the resulting executables are not really smaller than the CLR + mscorlib + app.
In Native AOT Overview
That's interesting indeed, but just one algorithm is barely representative for an overall performance comparison of programming language implementations. If we look e.g. at the results of the Are-we-fast-yet benchmark suite (see e.g. https://github.com/rochus-keller/Oberon/blob/master/testcase...) we see that there are significant differences per implementation and benchmark; so if we just pick a single benchmark, we might be in a sweet or sour spot of an implementation just by coincidence. If we would e.g. just look at the Mandelbrot benchmark in the referenced report we would conclude that LuaJIT is six times faster than Node.js 12 or Mono 5; but this conclusion turns out to be wrong if we look at the geomean over all benchmarks (micro and macro), where LuaJIT is only half as fast as the other two. A well-designed suite covers as wide a
Read the rest
range of different implementation challenges as possible and includes strict rules on how the benchmarks must be implemented in the different languages to allow comparison with as low an error rate as possible.
In Top Fastest Programming Languages: Rust, C++, Swift, Java, and 90 more compared

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.