News for hackers. Stuff that matters.
Re:Project Oberon by pjmlp on Friday February 25, 2022 @09:27AM (#30467617)
The Oberon channel has several videos of Oberon in action,

https://www.youtube.com/results?search_query=The+Oberon+Chan...

While Oberon was quite cool, people should also learn about its Xerox influence,

"Eric Bier Demonstrates Cedar"

https://www.youtube.com/watch?v=z_dt7NG38V4

Also dive into what happened afterwards, Oberon-2, Active Oberon, Zonnon,...

Active Oberon could be considered quite modern, also makes the distinction between safe and unsafe pointers, which improves the experience for low level coding.

https://github.com/metacore/A2OS

One of the best things about these systems is proving what systems programming with automatic memory management were capable of.

Given Oberon-2's influence on Go, maybe improving Fyne (https://fyne.io/fynedesk/) with something like gRPC for the dynamic experience, could be a possible sucessor.

Re:Project Oberon by kragen on Friday February 25, 2022 @12:56PM (#30470039)
To be entirely meticulous about the genealogy, I think Wirth was at PARC in 01976, and what inspired him most there was Mesa; Lampson first described (Mesa's successor) Cedar in PARC TR CSL-83-15, Xerox Palo Alto Research Center, December 01983, and without rereading the report, I think Cedar's development began about 01981. So Cedar is Oberon's sibling, not its parent.

The connecting link at ETH between Mesa and Oberon was the Lilith workstation with its system software written in Wirth's Modula-2 (01977–01984).

As for Golang, the relationship is much more direct! The first public version of Golang is mostly a slightly modified version of Pike's Newsqueak, but at the point Golang became Golang, Pike was working with Griesemer and Thompson. IIRC Griesemer did his dissertation under Wirth at ETH on extending Oberon to parallel computers.

Re:Project Oberon by Rochus on Saturday February 26, 2022 @11:22AM (#30478885)
> was at PARC in 01976, and what inspired him most there was Mesa

Wirth was twice at PARC. In his HOPL3 paper he writes in section 4 "From Modula to Oberon":

"As my sabbatical year at Xerox in 1976/77 had inspired me to design the personal workstation Lilith in conjunction with Modula-2, my second stay in 1984/85 provided the necessary inspiration and motivation for the language and operating system Oberon [29, 30]. Xerox PARC ’s Cedar system for its extremely powerful Dorado computer was based on the windows concept developed also at PARC for Smalltalk. [...] Thus the idea was born of gaining first-hand experience by designing such a modern operating system on my own, with Cedar as the primary source of ideas."

> IIRC Griesemer did his dissertation under Wirth at ETH

His supervisor was actually Prof. Mössenböck, the author of Oberon-2 (from which Go inherited its type-bound procedure syntax), see https://www.research-collection.ethz.ch/bitstream/handle/20....

Re:Project Oberon by kragen on Sunday February 27, 2022 @02:05PM (#30491418)
Thank you very much for the corrections! I haven't read HOPL3 yet, but he probably said similar things in the Oberon book and I just misremembered it.

Apologies for misleading readers!

Re:Project Oberon by Rochus on Sunday February 27, 2022 @03:15PM (#30492055)
In fact, I'd be very interested to know what Wirth thinks about Smalltalk; I haven't read a statement from him about it anywhere, or heard anything from him about it in the many interviews; interestingly, Kay asked him a question at the Turing Price lecture and even introduced himself by name, and you didn't get the impression that Wirth knew him.

I also find it remarkable that while Wirth refers to the windows concept and Smalltalk in the HOPL paper, which was written as recently as 2005, Cedar does not use overlapping windows at all, but rather - like the Oberon system - a tiling window manager; the Oberon user interface looks very similar to Cedar and has little resemblance to the Smalltalk-80 user interface.

Re:Project Oberon by i_don_t_know on Monday February 28, 2022 @10:33AM (#30500899)
There's a hint of what he thinks about Smalltalk in his book "Programming with Oberon" (co-authored with Martin Reiser). See sections 12.6.1 and, in particular, 12.6.2 (pages 236-239): https://people.inf.ethz.ch/wirth/ProgInOberonWR.pdf
Re:Project Oberon by Rochus on Monday February 28, 2022 @07:23PM (#30507279)
Thanks for the reference; unfortunately we don't know who of the two authors has written the paragraph, and it is also not very specific. Meanwhile I found the following paragraph in Wirth's tutorial titled "Programming in Oberon" (of which a version can be downloaded from https://people.inf.ethz.ch/wirth/Oberon/PIO.pdf, and the first version of which apparently is from 2004); on page 57 we can read:

"The designers of Smalltalk clearly wished to present not only a new language, but also a new paradigm, a new approach to programming. To be effective and convincing in this endeavor, they provided also a new terminology to underscore a different quality of programming. In this effort, record-structured variables became objects, their associated procedures became methods, a data type became a class, and calling a procedure is now termed sending a message to an object. This is denoted as object.method(message)"

It is interesting to note that "object.method(message)" has nothing to do with Smalltalk syntax at all (which supports my assumption that he had little to no personal contact with it). In his 1988 papers Smalltalk is just referenced as one of many OO languages, next to Simula 67, ObjectPascal and C++.

Re:Project Oberon by kragen on Monday February 28, 2022 @03:53PM (#30504976)
§§12.6.1–2 are on pp. 253/338 to 256/338. Initially I went to the wrong pages. Definitely worth a read.

Interestingly his point (3) on p.219 (236/338) ("Within the text of a specific action procedure, a regional type guard is required to allow access to the state variables defined in the extension of the base type") was precisely Abadí and Cardelli's motivation for defining the ς-calculus. This limitation means that Oberon's type system is insufficient to statically guarantee the safety of object methods ("action procedures") and this is an obviously desirable thing. He mentions another similar limitation on the Oberon type system on p. 237 (254/338): "The fact that the compiler cannot check whether a message is ‘understood by the object’ may be an advantage or a disadvantage, depending on the type of the application."

Re:Project Oberon by scroot on Sunday February 27, 2022 @05:14PM (#30493228)
> In fact, I'd be very interested to know what Wirth thinks about Smalltalk; I haven't read a statement from him about it anywhere, or heard anything from him about it in the many interviews

I'd be interested to know as well. It might be worth writing him a physical letter asking about it. There is a mailing address for his department at ETH here (https://people.inf.ethz.ch/wirth/index.html) and I'm willing to bet they know how to forward him correspondence.

Re:Project Oberon by Rochus on Sunday February 27, 2022 @05:49PM (#30493591)
His home address and phone number are even in the phonebook, but I don't consider myself or the subject important enough to bother him with it. But maybe someone else here has insider information. That said, there's plenty of circumstantial evidence that he either didn't know Smalltalk in the nineties or didn't think it was worth mentioning. After all, Xerox themselves did not use Smalltalk in their products either, and even at PARC the other teams tended to work with BCPL or Mesa rather than Smalltalk. I read an interview with Larry Tesler where he describes that for a demonstration of a Smalltalk application they had to fast forward the movie so that the menus would pop up fast enough. Not surprisingly, Tesler then brought Object Pascal to life at Apple in collaboration with Wirth, instead of using Smalltalk as he had in his previous job (even though Apple had a license - that was used nota bene later for Squeak).
Re:Project Oberon by _fz_ on Friday February 25, 2022 @03:39PM (#30472089)
Here's a Project Oberon emulator in Go: https://github.com/fzipp/oberon

And a Go port of the RISC compiler: https://github.com/fzipp/oberon-compiler

Re:Project Oberon by elcapitan on Friday February 25, 2022 @07:36PM (#30474202)
Totally OT, but I was wondering why you are writing years in 5 digits? :D
Re:Project Oberon by iso8859-1 on Friday February 25, 2022 @09:15PM (#30474726)
Re:Project Oberon by kinjba11 on Friday February 25, 2022 @09:45PM (#30474852)
Perhaps OP should be writing 11976 not 01976

https://en.wikipedia.org/wiki/Holocene_calendar

Re:Project Oberon by renewedrebecca on Friday February 25, 2022 @09:29PM (#30474780)
Planning ahead.
Re:Project Oberon by LargoLasskhyfv on Friday February 25, 2022 @11:36PM (#30475242)
There was another sibling of the Lilith:

https://en.wikipedia.org/wiki/Kronos_(computer)

Re:Project Oberon by pjmlp on Friday February 25, 2022 @01:05PM (#30470179)
Yes, mostly correct.
Re:Project Oberon by kragen on Friday February 25, 2022 @01:09PM (#30470224)
I'd be delighted if you'd correct whatever isn't!
Re:Project Oberon by pjmlp on Friday February 25, 2022 @01:15PM (#30470299)
Go is mix of Limbo and Oberon-2.

I also remember reading somewhere that Wirth found Cedar too powerful, or complex, so Oberon was designed with the goal to be as capable as Cedar environment, while using a simpler language.

So not sure which kind of relation I would put them, besides being an inspiration.

Re:Project Oberon by kragen on Friday February 25, 2022 @06:29PM (#30473651)
Thank you!

What are the Oberon-2 features in Golang that aren't in Limbo?

I should have clarified the Squeak → Newsqueak → Alef → Limbo → Golang lineage, but from my point of view Newsqueak is already recognizably a version of Golang (and Squeak isn't.)

Re:Project Oberon by pjmlp on Saturday February 26, 2022 @02:17AM (#30475779)
The way methods are declared (Oberon-2 syntax), the unsafe package (SYSTEM in Oberon) and package initialisation blocks.
Re:Project Oberon by kragen on Sunday February 27, 2022 @02:05PM (#30491426)
Thank you!
Re:Project Oberon by badsectoracula on Friday February 25, 2022 @09:40AM (#30467747)
While these are called "Oberon", judging from the screenshots (i haven't watched the videos), they seem to be way beyond the minimalistic nature of the Oberon system shown in Project Oberon.

I think the emulator linked at the bottom left side is a better way to check out Oberon in action as you can easily (well, after you figure out how things get compiled, etc :-P) see it in practice and how a few individually simple (if not outright primitive) things can be combined to create something nice. For example i always found it amusing that the "menu bar" in each window is really just a regular text area and the commands shown are really methods that are called when you (IIRC) middle click them, like any other text in a window (so the main "GUI" for a program can really by just a text file with methods to click on - and of course since it is editable you can simply customize the GUI by editing the text file).

Re:Project Oberon by pjmlp on Friday February 25, 2022 @10:21AM (#30468182)
They are Oberon, the system that was described on the first edition of Project Oberon was the version 1.

ETHZ researchers and Niklaus Wirth then iterated further on the Oberon (the OS) and Oberon (the language).

The definitive Oberon (the OS) version that still uses the plain Oberon (the language) from original project was System 3, which is what those videos relate to.

In Active Oberon used to write AOS (BlueBottle OS), you can still relauch System 3 as a nested OS.

Re:Project Oberon by wrycoder on Friday February 25, 2022 @12:43PM (#30469879)
I consider Active Oberon and AOS to be forks, and I think Wirth does, also. I believe that he feels that Project Oberon is his final word on the subject.

Wirth created Oberon-7 largely by removing features[0]:

Revised Oberon (Oberon-07) is a revision of the original language Oberon as defined in 1988/1990. It is accepted by the compiler recently completed for the ARM processor. Most changes in the language might easily be called features of a dialect. However, there are a few that merit a stronger distinction, because they should be considered as permanent, and as corrections of unsatisfactory properties of the original Oberon. These are the elimination of the loop statement, function result specification, array assignments, constant parameters, and read- only import of variables. All changes were made in the interest of regularity, simplicity, completeness, and well-structuredness.

See also [3] for confirmation that Oberon-7 is the language of Project Oberon.

I'd recommend reading the papers on Wirth's personal site [2].

[0] https://people.inf.ethz.ch/wirth/Oberon/Oberon07.pdf (pdf) (15Jul2011 update)

[1] https://people.inf.ethz.ch/wirth/Oberon/OberonAtAGlance.pdf (pdf) (20Nov2013)

[2] https://people.inf.ethz.ch/wirth/Oberon/index.html

[3] https://people.inf.ethz.ch/wirth/ProjectOberon/PO.System.pdf (pdf) (2013)

Re:Project Oberon by pjmlp on Friday February 25, 2022 @01:11PM (#30470248)
Project Oberon cannot be his final word, given that it is only the first version, later upgraded up to System 3 version.

It is hard to consider them forks, when they originated on the same department and he also collaborated in some form.

Component Pascal and Zonnon, those are proper forks.

While I admire Wirth's work, his goal to pursue a minimalist Oberon with Oberon-07 is not so interesting to me.

My pocket phone is more powerful than any Xerox workstation, why should we keep searching for such minimalist endeavours, instead of the rich development experience provided by them.

Re:Project Oberon by kragen on Monday February 28, 2022 @06:14PM (#30506526)
Your pocket phone is more powerful than any Xerox workstation, but you and I are less powerful than Wirth, so if we want systems we can understand and restructure at will, they probably need to be simpler than what Wirth could handle, not more complex.
Re:Project Oberon by badsectoracula on Monday February 28, 2022 @06:45AM (#30498821)
> While I admire Wirth's work, his goal to pursue a minimalist Oberon with Oberon-07 is not so interesting to me.

While it may not be interesting to you, it is what the linked project is all about.

Re:Project Oberon by badsectoracula on Friday February 25, 2022 @10:37AM (#30468376)
Yes they are Oberon too but my point is that they've evolved and added a ton of stuff that go further than the minimalistic nature of the linked site. The "Project Oberon" in the site doesn't even have overlapping windows or color for example.
Re:Project Oberon by pjmlp on Friday February 25, 2022 @12:03PM (#30469411)
That is like evaluating what MS-DOS was capable of by looking at MS-DOS 1.0 instead of 6.22.

Oberon 1.0 isn't what was the daily driver at ETHZ, beyond its initial introduction.

Re:Project Oberon by badsectoracula on Monday February 28, 2022 @06:43AM (#30498807)
The point of the linked project isn't to evaluate what the most advanced version of Oberon is but to show a minimalistic system built from the ground up in a way that can be entirely understood by a single person. It is mentioned at the top of the page.