Conversation

Notices

1. h@social.coop's status on Monday, 08-Jan-2018 06:51:34 UTC h

   • Vertigo

   @vertigo An appliance is physical, with hard constraints. The barriers between programs are conventions and tradition. Only in rare cases due to best practices.

   • Hallå Kitteh likes this.
   • Hallå Kitteh repeated this.
   • Vertigo (vertigo@mastodon.social)'s status on Monday, 08-Jan-2018 07:00:53 UTC Vertigo

     @h I don't think it was lack of vision; it was the vision of putting computers in the hands of untrained masses that drove the interfaces we have today. There inlies the problem: untrained.

     The untrained masses became either complacent, or worse, actively reveled in their ignorance. This is literally their point of view: "Why should I learn how to type these god-awful cryptic gobbledygook when I can just drag and drop these pretty pictures? Reading is hard! Let's go shopping!"

     Hallå Kitteh repeated this.
   • h@social.coop's status on Monday, 08-Jan-2018 07:19:20 UTC h

     • Vertigo

     @vertigo

     Try to:

     1. Write a program that has some struct
     2. Enable it to send this struct to another program.
     (Serialising and sending over sockets is cheating. There is no need to waste cycles in serialisation between two programs running in the same memory space, on the same architecture)

     3. Write a program that can receive that struct and print it.

     4. Make sure it compiles and runs on all major platforms.

     If you can achieve that effortlessly, then hard barriers don't exist.

     Hallå Kitteh repeated this.
   • Vertigo (vertigo@mastodon.social)'s status on Monday, 08-Jan-2018 07:52:54 UTC Vertigo

     @h When you think about it, IBM's System/360 was just like the Amiga when it was first introduced: a shared, single address space environment. They had 2KB quasi-pages which prevented one task from writing into another task's memory, but *nothing* stopped tasks from *reading* other tasks memory. Today, z/OS is fully memory protected.

     So, somehow, there must be a way to evolve an AmigaOS-like environment without breaking compatibility.

     Hallå Kitteh repeated this.
   • Vertigo (vertigo@mastodon.social)'s status on Monday, 08-Jan-2018 08:07:25 UTC Vertigo

     @h Kestrel-3.

     Since my current CPU lacks any MMU, the kernel would not support "safe" binaries. It'd be shared-memory, single address space, just like Kickstart 1.3.

     *After* I build the MMU for it (OR, after I switch the CPU out for a Rocket core), then I can upgrade the kernel to add support for "safe" binaries and implement the new system calls needed to make communicable regions of memory.

     Hallå Kitteh repeated this.