Re: EuOS and DOS
- Posted by Ralf Nieuwenhuijsen <nieuwen at XS4ALL.NL> Oct 11, 1998
- 616 views
>My thoughts on this are incomplete so perhaps some of you out there can >come up with some more ideas. >I guess people are starting to wonder why they need a 400MHz CPU, 64MB RAM >and 2+GB HDD to do even the most basic things and no doubt getting tired of >the "Blue screen of death". WinDoze is OK for some non-critical things but >I can't help feeling that WinDoze is not quite the right direction to go >in. Sometimes it's nessasary to take a couple of steps back in order to go >forward. Interesting remark. May I say, that windhoos (eh.. windows .. dutch joke) 98, with the right tools, the right programs, and the right usage, can be a quick efficient platform. But sometimes, I get annoyed when I use photo-shop 5, which can handle almost any type of picture, but my webbrowser cant. And if it could, it would have 2 or more copies of that code, optimized of safe 486. Not a special MMX version, or P2 Version. Would it be cool, if we could say, send the input of that.. to the decompressor .. to that program. First of all. How do we manage things, we have special machine dependent routines, different ones for handeling I/O, Memory, Ports, etc. In my point of view, the whole system should be one gigantic database, where the fact that a certain 'item' (.. ring a bell ?) is stored in the memory, swap file, on disk, on disk compressed, in my internet cache, an I/O port or whatever is merely an attribute you can *if* you want, lookup. However, no structures, no oop, etc. We have 'items' and they all have attributes. They can determine the attributes themselves. An attribute is an for item: 'a' >> b = c (read: for item a, b is equal to c, if you ask item a, it will tell you b equals c) Every attribute of one item, should be another legal item. So all items are connected in a space. And the link between one item and another, (sometimes it takes a lot of steps, from item to item, to get to the desired item) can be different upon what attribute you are calling. So, all items are in a sort of 'space', and all are directly connect to some other items and indirectly to all items. This has as effect, that we only call/calculate things when we use them Consider me making this statement: a = b * 3 b = 4 ? a -- 12 b = 6 ? a -- 18 So, if im not seeing a window, it is not being drawn. Only the things that have to be done right away are done. For example, a 3D shooter, we need to draw the screen, so we need to draw the enemy, so we need to lookup his location, so we need to perform the AI. All code/items are high level. And no actual programming occurs. You have a few basic items that provide the tools (say, expression and evaluation items). And based upon those items, come new layers of items, each very small. And every item, only defines a number of 'streams'. The OS, would link it all together in real-time. Making short-cuts, whenever it finds the item, the other item is asking for. Information is streaming from one item to another. And that stream never ends. And how it streams and through what items (even an item to sum up values, simerlar to the '+' expression command in Euphoria). Every item, just declares how it would stream. And in the end, when the 'path' is completely found, it ends of being information streaming from the keyboard or another I/O to and from memory, to and from other hardware, being proccesed inbetween. All the code is divided upon little fragments, and such things, can look a lot alike. Also you can easily, let information from one place, stream into another. Just connect them. Consider this: a = c + 1 a = b * 3 b = a /2 c = 7 -- Now item a is receiving the value '6', item b the value '2', item a *then* receives the value '2', item c the value '1' and item 'b' the value 2/3, etc. etc. This would go on for ever, however, the *next* value is only calculated when asked upon. > I will write some more on this later. Please do. Whatever you think of the above item/streaming concept, you people must admit, in these days, with these advanced data-based capabilities our file and I/O system is way too old, and can be much improved. Ralf