OberonSystem VS inai

> gain a deep understanding of it .. generate smaller subsets of the system

You can use the OberonViewer for this purpose with the original source code, or the Oberon IDE with a version of the Project Oberon System which runs with SDL on all platforms, see https://github.com/rochus-keller/oberon/#binary-versions and https://github.com/rochus-keller/OberonSystem/tree/FFI

There is a version of the Oberon System compatible with the Oberon+ toolchain and IDE, see https://github.com/rochus-keller/OberonSystem

> that's just a compiler on other OSes, right?

It's possible to run an Oberon System with it (see https://github.com/rochus-keller/OberonSystem); it runs on all platforms and the generated C code could even made run as OS on an embedded system if need be; I currently also experiment with System 3 and alternative backends; but this is more for curiosity; from my humble point of view the OS topic is solved with Linux (which can also be configured for very low resource systems).

Thanks. It's not only Oberon, but Oberon+ as specified here: http://oberon-lang.ch. You can even mix the traditional and new syntax, as e.g. demonstrated here https://github.com/rochus-keller/OberonSystem/tree/FFI.

Yes, Oberon+ is on the direct hereditary line to Oberon 90, Oberon-2 and Oberon-07. Here is more information about the language: http://oberon-lang.ch. There are also implementations of the Oberon System compatible with my compiler and IDE (the LuaJIT version so far): https://github.com/rochus-keller/OberonSystem/.

Interesting article, but I would rather go for http://www.projectoberon.com/.

Oberon is a really nice and very well documented programming language and operating system to experiment with. Unfortunately not that much distributions are still available (most links seem to be dead).

If you're interested in the OS or the language, here is a platform independent, stand-alone version running on LuaJIT: https://github.com/rochus-keller/OberonSystem

There is also an integrated IDE with syntax coloring, semantic navigation, and a source level debugger.

The compiler supports small-case keywords and underscores in identifiers. I'm currently working on an extended version of the language.

This is useful! Thanks for writing this out. I find in-process REST intriguing as it stands a little in contrast with OOP techniques. One possibility I’ve with in-process REST is that it seems to make live patches feasible - more feasible than in erlang. I use the idea as the core of Inai - https://github.com/imaginea/inai ... so am curious to play with that aspect of ObjS.

A bit of a shameless plug, but really looking for feedback .. I've been experimenting with Inai [1][2], a framework that can help build modular microservice-like software with similar Dev team independence properties but can independently be built and deployed as a monolith or as separate services operationally. So far, I've had fun building an internal project at much higher speed than I've managed any similar project and had more fun doing it. I feel the idea (which is still nascent) has some merit, but would like to know what folks think.

[1] source - https://github.com/Imaginea/Inai

[2] blog post describing Inai - https://labs.imaginea.com/inai-rest-in-the-small/

At some point, this would be come close to the AppleScript protocol or Symbian OS.

> So the drawing part of an application would just be a process that sends the screen/compositor process a message describing the state of its window as a tree, and receives messages for events in response.

I've been toying with an interpretation of this here - https://github.com/Imaginea/inai - and kind of having fun with it .. and even built a prototype internal app using it. Super early stage and so stuff won't necessarily make sense at the outset .. or possibly ever. Thoughts welcome though.

> A big advantage is it makes the semantics of composing GUIs a lot more reasonable "replace this leaf of my tree with this other process' tree" ...

The "dom" service in Inai pretty much feels like that. I felt like an idiot to try and (for lack of a better expression) REST-ify the DOM, but it seemed to work to my surprise.

> An application could also "proxy" for a widget, including over a network link, so you get fairly simple network transparency this way too.

.. yeah due to the "REST" nature, this becomes pretty straightforward.