Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon. Entire thread

The tdavis must go.

Name: Anonymous 2011-09-13 15:41

I know everyone is just barely tolerating tdavis and his LoseThos ramblings, hoping that he will get bored and go away, but do I have some news for you! No, he won't leave through boredom. He'll keep on making his crackpot posts until you, me, and the Sussman have gone mad. He must be motivated to leave. He must chained behind the back of a pickup truck and dragged through the proverbial streets. His body needs to be dismembered, his remains torched with gasoline, and his ashes scattered into the dust of the Universe before he'll stop.

Name: Anonymous 2011-09-16 9:30

>>81

1) LoseThos will always run everything in kernel mode, ring 0.  All programs will have full access to memory, I/O ports, instructions, etc.
Enjoy your no security.

2) LoseThos will always "identity map" virtual memory.  (Virtual addresses are set equal to physical addresses with a single map for all tasks on all cores.) It's as though paging is not used.
That is very primitive.

3) LoseThos will always be for one platform -- x86_64 PC compatibles.
Your non-portable OS is next to useless.

4) LoseThos will never have networking.
Why not?

5) LoseThos will always have one video mode, 640x480 by 16 colors, unless this mode becomes unavailable on computers in the future.  See LoseThos Graphics.
And this is evidently only because you're incapable of writing a video driver that is decent at a higher resolution (see my last post).

6) The LoseThos operating system will be free.  I might sell applications, support, or, possibly, adware.
Adware is a bad thing.

7) LoseThos will be 100% open source with all source included, unless device drivers or something can only be included with non-disclosure agreements.
Who cares? No one will want to use this shitty OS anyway.

8) All function args and returns will be 64-bit.  No plans for C++.
Why would you return a 64-bit value, if, for example, you know you're dealing with bytes in a certain situation? Forcing yourself to always deal in 64-bit quantities is utterly stupid.

9) LoseThos documents are not for printing.  They're dynamic and intended for the screen.  There will always be just one font, a fixed-width font.  No Unicode, just ASCII.
No Unicode? Why the fuck not?

10) LoseThos is not for multimedia.  Games will be created by programmers, not artists.  Sounds and images will be, primarily, calculated in real-time, not fetched.
Who says you can tell us how we will use your OS? Of course, we won't, but nevertheless my point still stands.

11) All functions, variables and class members will be accessible.  There are no C++ public/private protections and all functions, even secondary ones in the kernel, can be called.
Enjoy your no security.

12) Backward compatibility is NOT guaranteed.  You are safest working with JIT compilation instead of AOT static binaries because I can add members to classes, reorder members in classes, add default args to existing functions, change #define values, etc. all without breaking compatibility.
Enjoy going against principles defined in computer science for the last two decades.

Are you fucking happy now?

Newer Posts
Don't change these.
Name: Email:
Entire Thread Thread List