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.
>>74
Those quotes are not fixed from an aesthetic point of view, look at them.
Since you people obviously are unable to read common English I will capitalize everything in a naive hope that it will make things easier to understand, PLEASE PROPERLY FORMAT AND INDENT YOUR POSTS.
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.
>>74 THIS IS A MESSAGE FROM THE SUSSIX DEV TEAM (Me)
All function args and returns will be 64-bit. No plans for C++.
We here at the SUSSIX dev team (Me) see this as a major design flaw, SUSSIX is a variable byte OS. I am glad that you as our competitor have decided to make erroneous design decisions as to make our job even easier, now SUSSIX is even closer to taking over the world.
Due to my apparent personality disorder(s) we have one order of magnitude more users than you, 2011 is the year of the SUSSIX computing device1.
________ 1. Not applicable in or around the Vatican and, on, in or around East-Timor. Hardware2 sold separately. 2. Sussix hardware still only consists of rubber bands and some assorted t-shirts for your wearing pleasure.
>>83
Actually I am not happy, you should group related statements together, now you have equal spacing between a quote, your reply to that quote and the next quote. You should rather group a quote and your reply together as a single unit, your code must be horrible to look at (don't bother posting it, I won't look at it).
The focus is also all wrong, the emphasis should be on your reply not the quote, now they have equal emphasis, please use THE FORCED BULLETIN BOARDIFICATION OF CODE THREAD OVER to add emphasis to your replies.
This is similar to a programming prompt where the focus should be on output of commands not on the prompt or the users input, one would think someone on a programming text-board would figure that out themselves but here we are.
So please follow these simple guidelines and I will be happy, is that OK faggot?
10 i = i + 1
15 IF i > 99999 THEN PRINT ".";: i = 0
20 IF INKEY$ = "" THEN 10
30 PRINT "King James Bible, Line:", i
Line: 38533
which Solomon had made.
12:10 Instead of which king Rehoboam made shields of brass, and
committed them to the hands of the chief of the guard, that kept the
entrance of the king's house.
12:11 And when the king entered into the house of the LORD, the guard
came and fetched them, and brought them again into the guard chamber.
12:12 And when he humbled himself, the wrath of the LORD turned from
him, that he would not destroy him altogether: and also in Judah
things went well.
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.
Ring mode switching is poor performing(programmers always try to reduce ring switches) and outdated(lookup design of Multics) security model. A capability-based security rather then privilege levels should be employed.
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.
Paging is ineffective at managing memory. It is mainly a protection against poorly designed memory hogs, and disk access is always a huge performance drain.
3) LoseThos will always be for one platform -- x86_64 PC compatibles.
Your non-portable OS is next to useless.
86x64 is currently the market leader, and its only serious rival the ARM is unsuited for high-performance use while low-power atom cores slowly creep into tablet market. x86 will be relevant for very long time, and x64 rivals in this modern form will have to emulate x86 due huge amount of closed source and unportable software written for this platform.
4) LoseThos will never have networking.
Why not? He probably didn't design any infrastructure to support low-latency networking. I suppose he wants some common driver for all network cards.
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). The OS is using VGA as basic mode for rendering the interface. Obviously the apps could override that(there is low level access to hardware).
6) The LoseThos operating system will be free. I might sell applications, support, or, possibly, adware.
Adware is a bad thing. open source OSes can be altered to remove any adware(of course not that easy for casual users)
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. 64 architecture will not be superseded for along time, after which the OS will be long obsolete. The choice is to implement a simple, straightforward solution with minimal backward compatibility
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? ASCII is faster, takes less ram and is obviusly simpler to implement
25 At that time Jesus said, “I praise you, Father, Lord of heaven and earth, because you have hidden these things from the wise and learned, and revealed them to little children. 26 Yes, Father, for this is what you were pleased to do.
27 “All things have been committed to me by my Father. No one knows the Son except the Father, and no one knows the Father except the Son and those to whom the Son chooses to reveal him.
28 “Come to me, all you who are weary and burdened, and I will give you rest. 29 Take my yoke upon you and learn from me, for I am gentle and humble in heart, and you will find rest for your souls. 30 For my yoke is easy and my burden is light.”
------------------
What's God's favorite color and animal. He changes His favorite color, I found out.
Seriously, 120,000 (carefully closed source) lines of code for that utter shite? Hello, Minix has 6000 LoC!
This looks like very poor programming. And what with this bastardized``C+''? Cut the religious crap, you're simply a terrible programmer, that's why they fired you.