> Then again, one probably doesn't pick Oberon if one enjoys working with the current weird OOP/FP/FRP morass.
I am passionate about Oberon, collect all Wirth related papers and enjoyed using Native Oberon back in the day, when the OS was made available on the PCs, around 1996 or so.
He is one of my "idols" in history of computing and I even had the opportunity to meet him once, as he gave an Oberon conference at CERN.
However, I have learned many paradigms and languages since those days, to be happy just doing plain Oberon on the job.
Nowadays any JVM or .NET language is more my kind of thing for it, the only thing missing is standard AOT compilation as part of their canonical toolchains, but that is slowly being taken care of.
At least some of his ideas regarding safe OS architectures seem to live on those runtimes, and MSR work.
I read my previous post again and just wanted to make clear that this "morass" was referring specifically to the JavaScript "landscape", not the paradigms in general...
And yeah, I remember Native Oberon, too. In the mid-90s it seemed much more open about what OS was taking over. Win95 just came out, OS/2 was still an alternative (Warp), Linux was making the rounds, and then some oddballs like Oberon or QNX...
Marrying Oberon with the browse feels a bit weird, though. The ETHZ workstations were rather reductionist, and hosting that on a modern browser stack...
(For a double whammy, one could write the backend in Go, the mirror universe Oberon)
I am passionate about Oberon, collect all Wirth related papers and enjoyed using Native Oberon back in the day, when the OS was made available on the PCs, around 1996 or so.
He is one of my "idols" in history of computing and I even had the opportunity to meet him once, as he gave an Oberon conference at CERN.
However, I have learned many paradigms and languages since those days, to be happy just doing plain Oberon on the job.
Nowadays any JVM or .NET language is more my kind of thing for it, the only thing missing is standard AOT compilation as part of their canonical toolchains, but that is slowly being taken care of.
At least some of his ideas regarding safe OS architectures seem to live on those runtimes, and MSR work.