| ▲ | turtleyacht 4 hours ago |
| The next language ought to ensure memory-safe conditions across the network. |
|
| ▲ | yvdriess 3 hours ago | parent | next [-] |
| AmbientTalk did this. I used it for a demo where I dragged a mp3 player's UI button to another machine, where pressing play would play it back on the originator's speakers. Proper actor programming in the veins of E and Erlang. https://soft.vub.ac.be/amop/ |
|
| ▲ | csrse 3 hours ago | parent | prev | next [-] |
| Already exists since way back: https://github.com/mozart/mozart2
(for example) |
| |
|
| ▲ | gostsamo 3 hours ago | parent | prev | next [-] |
| the article states that the language can have extensions for different domains, so it is also an option. |
|
| ▲ | 3 hours ago | parent | prev | next [-] |
| [deleted] |
|
| ▲ | derleyici 3 hours ago | parent | prev [-] |
| And the answer is… Rust. |
| |
| ▲ | anthk 3 hours ago | parent [-] | | Or Algol 68, which is doing a comeback. | | |
| ▲ | pjmlp 3 hours ago | parent [-] | | Or even ESPOL and its evolution, NEWP, never went away, only available to Unisys customers that care about security as top deployment priority. | | |
| ▲ | EvanAnderson 2 hours ago | parent [-] | | I wish more people knew about the Burroughs Large Systems[0] machines. I haven't written any code for them, but I got turned-on to them by a financial Customer who ran a ClearPath Series A MCP system (and later one of the NT-based Clearpath machines with the SCAMP processor on a card) back in the late 90s, and later by a fellow contractor who did ALGOL programming for Unisys in the mid-70s and early 80s. It seems like an architecture with an uncompromising attitude toward security, and an utterly parallel universe to what the rest of the industry is (except for, perhaps, the IBM AS/400, at least in the sense of being uncompromising on design ideals). [0] https://en.wikipedia.org/wiki/Burroughs_Large_Systems | | |
|
|
|
