This operating system looks pretty much like Plan9. I do not know if there is any relation between those two.
The main thing it shares with Plan 9 is in the Acme editor which was inspired by Oberon. https://news.ycombinator.com/item?id=32606415
Oberon (2009)
121–130 of 149 posts
Re: Oberon (2009)
#122Re: Oberon (2009)
#123I am interested in alternative GUI tech. If you find this interesting you might find my declarative frontend idea interesting called additive-guis https://GitHub.com/samsquire/additive-guis The idea is you define how the GUI should appear by describing it. The GUI changes in real time based on what you describe. And I also designed a GUI primitive I called GUI thunking, inspired by Haskell. The idea is you can chain…
That's how Oberon Gadgets were working. Later the same idea was used in Blackbox Component Builder.
Re: Oberon (2009)
#124As I described it to some folks recently, Go can be simply characterised as a slightly stripped version of the Oberon-2 (or Component Pascal) language, recast in a C like syntax, and with a number of small additions. Removed from Oberon-2: Sets, Type Extension (classful OO scheme) Added by Go: Maps, Slices, Strings, Interfaces, Channels, Coroutines. Such that I suggested it is well worth reading the Oberon-2 language…
> Go can be simply characterised as a slightly stripped version of the Oberon-2 Well, not really; there are not much similarities between Oberon and Go besides the receiver syntax of Oberon-2 bound procedures (which was invented by Mössenböck btw) and the fact that both are garbage collected. In your list "removed from Oberon" you should add type inclusion (Go doesn't even have implicit coercion); there is an interse…
Re: Oberon (2009)
#125Earlier quoted context omitted.
The main thing it shares with Plan 9 is in the Acme editor which was inspired by Oberon. https://news.ycombinator.com/item?id=32606415
Thanks
But in Oberon everything worked in the same address space.
Re: Oberon (2009)
#126Earlier quoted context omitted.
> ...all memory accesses are indirect ... module-data is position independent and may be moved in case memory should fail due to radiation damage. I once used a debugger that shipped with a rather snarky easter egg command: "find my bug". One of its more useful suggestions was "Maybe a cosmic ray error? Use smaller chips!".
Wouldn't smaller chips make the problem worse?
Re: Oberon (2009)
#127Earlier quoted context omitted.
> Go can be simply characterised as a slightly stripped version of the Oberon-2 Well, not really; there are not much similarities between Oberon and Go besides the receiver syntax of Oberon-2 bound procedures (which was invented by Mössenböck btw) and the fact that both are garbage collected. In your list "removed from Oberon" you should add type inclusion (Go doesn't even have implicit coercion); there is an interse…
coroutines module comes with Oberon S3 system. also Ulm's Oberon compiler has coroutines module.
Re: Oberon (2009)
#128Not only have I heard of Oberon, I've written code for it! The Oberon programming language is a nicer-than-average descendant of Pascal and Modula-2. The compiler was reasonably fast even in the 90s. The UI was strange enough to feel really interesting. As the article mentions, you could type a command anywhere and click it. And the older version I used had tiling windows, although this seems to have changed. But one…
Also the whole OS was a 1.44' bootable floppy disk which booted in 10 seconds on a 486
Re: Oberon (2009)
#129Interesting to learn about this! It's not as drastically different as expected from the initial write-up. The zoom-to-switch-context reminds me of Figma (a design tool) -- personally I like the metaphor of managing hierarchy with scale while mapping spatial relationships to functional ones. The idea of mixing "data" and "code" is intriguing. I might have to play with an install locally!
Re: Oberon (2009)
#130The Oberon book (by Wirth, updated in 2013) is excellent in that it describes the entire Oberon system, from the processor on up in a single volume. https://people.inf.ethz.ch/wirth/ProjectOberon/PO.System.pdf
For whatever reason, that PDF is incomplete. The ToC goes through Chapter 16, but the text includes only up to Chapter 9. Part 2 is: https://people.inf.ethz.ch/wirth/ProjectOberon/PO.Applicatio... Part 3 is: https://people.inf.ethz.ch/wirth/ProjectOberon/PO.Computer.p... A fun point about the 3rd part. If you've ever been flummoxed by the basics of floating point math, part 3 discusses the fundamentals in 2 pages wit…