2 ms·
I had once tried rebuilding an Oberon compiler and the standard library using itself - all from the sources. I will never forget this - it only took 0.15 second
by Koshkin 9y ago
I had once tried rebuilding an Oberon compiler and the standard library using itself - all from the sources. I will never forget this - it only took 0.15 seconds.
Having said that, the language goes a bit too far trying to be "as simple as possible but not too simple", at least to my taste -- in a way that Go seems to be, only much more so. It also looks verbose - especially compared to C. So, while I marvel at the language and have a feel for its weird beauty, I don't think I'd be comfortable using it in my day to day activity - I guess, C and C++ have spoiled me...
- MaysonL 9y agoI used to develop in Oberon, and used a lot of keyboard macros - the verbosity of the language disappears when one keystroke turns ProcName into Procedure Procname (); VAR BEGIN END Procname;
- fiddlerwoaroof 9y agoI think if you look at it in context of the entire Oberon operating environment, it makes a certain amount of sense. While everything is written in Oberon, it seems to me that the average user would essentially be using oberon for roughly what shell scripts and AppleScript is used for: I.e. for writing little commandlets that automate frequently used functionality.
- pjmlp 9y agoIt was great, Oberon had a kind of REPL. Basically modules are loaded dynamically and any procedure that obeys to a specific signature could be called from the UI, via keyboard and mouse like the ACME editor on Plan 9. The way they get their input, depends on the signature. It could be like command line parameters, clipboard, or any selected UI element in another application.
- deleted 9y ago[deleted]