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.
>>7
Nobody cares about LoserTheOS or whatever it's called, not even that god that talks you when you stop taking your medications (and we know that you refuse to take them). Just go away. You aren't wanted here, not like that, not here nor anywhere else. We've all seen you come, troll and go from other forums in the past, just move on from this one to the next.
>>7
LoseThos might be great. It could be everything I ever wanted to see. But you're a piece of shit. The kind of guy who pay attention to not share the whole source, just in case.
When the word LoseThos is written on the Internet, we know it's you. Nobody ever tried your OS, who else would mention it? Who doesn't get his share of glory? Why are you spamming the Bible? Why are you such a douchebag? How do you post in /prog/ without a real OS?
Ok you're depressed, and that's your cover for being this whiny arrogant cunt... You had fun coding LoseThos, now enjoy it alone, and piss off.
>>11
I pity the first guy who would try to ask him for some simple help. He thinks nobody deserves to experiment with his great work, but still would love to be praised for it.
>>10
He's more than depressed, he seems schizophrenic, moreover one who isn't on treatment, which is a shame. Apart from the craziness and the actual, honest to his Markov Chain homophobia he is candid, humble guy, who has put all his remaining lucidity into a 7 year-long project.
It's just that we don't have to put up with his shit.
You guys follow me everywhere I go. You are CIA, said God. CIA is shit. They extort people. That's their game. If someone tempts you is probably the CIA. Don't do it, they are scum. I've been Godly and ignored their shit, but I see their shit.
CIA is scum--sucks dick.
God says...
C:\TEXT\PARADISE.TXT
still stood fixed to hear;
Then, as new waked, thus gratefully replied.
What thanks sufficient, or what recompence
Equal, have I to render thee, divine
Historian, who thus largely hast allayed
The thirst I had of knowledge, and vouchsafed
This friendly condescension to relate
Things, else by me unsearchable; now heard
With wonder, but delight, and, as is due,
With glory attributed to the high
Creator! Something yet of doubt remains,
Which only thy solution can resolve.
When I behold this goodl
>>16
Read the Bible. Actually, I haven't read the Bible, except in pieces. I could read SICP the same way. God is my tutor and tells me what I need to know.
10 i = i + 1
15 IF i > 99999 THEN PRINT ".";: i = 0
20 IF INKEY$ = "" THEN 10
30 PRINT "King James Bible, Line:", i
God says...
Line: 58831
the mirth of the land is gone.
24:12 In the city is left desolation, and the gate is smitten with
destruction.
24:13 When thus it shall be in the midst of the land among the people,
there shall be as the shaking of an olive tree, and as the gleaning
grapes when the vintage is done.
>>25
He mentions it alone. Anyhow OP is right, he never left a place by himself.
Name:
n3n7i2011-09-14 21:10
So, is it 'loSeth-OS'? (like 'joseph'?)
#2 is it very bad? ...i guess you have to start somewhere... Is it say worse than something like uh windows 3.1 or DOS? (..should take into consideration DOS/etc probably still had teams of people working on it..?)
#3 ...How well does he understand it? (possibly the most important part..?) // and How well can he explain it? ...
Those have aged slightly. I got rid of "cout". It was not worth the confusion and bad perception created by that sort of thing. Just recently I changed ESC/CTRL-Q for ESC/shift-ESC as save exit/abort.
...don't mean to sound nasty.. but are you familiar with the term:
'To tie one's own noose'?
Eg. >> an ideal environment for recreational programming
but
>> You'll have to work to walk-off with LoseThos code :-) I didn't do that on purpose, but I'm not going out-of-my-way to make it easy.
then...
>> don't mind if companies use LoseThos code with or without mentioning it. That's why it's public domain and not GPL.
>>I hope to make money with LoseThos in some way following the "dot com" model of releasing it freely to gain popularity and leveraging that down the road (?). I might sell advertisements, applications or support, but will stick to the
LoseThos Constitution.
>>I am a for profit company, not welcoming code contributions, but feedback is very welcome.
...I guess with those terms attached, the first thing anyone (who actually wants to develop it?) is going to do is grab the code and run a thousand miles from the name, and said terms/conditions/ownership..?
Name:
n3n7i2011-09-14 22:20
....Better to add more new features and less new conditions...? =)
I wanted to say that, if there is a single user who makes most of the posts under the n3n7i name, I actually appreciate the effort that you are making in having actual discussion on /prog/.
#1 not welcoming contributions == No support for 3rd party developments ? ...Anyone that wants to do you a favor thinks twice and goes somewhere else....
#2 Everything should be open source (as in free) == you / nor anyone else making a profit down the track (*insert clause where you can make money though adware/etc?)
>>33
It's a safe bet you can laugh at the people who obsess on their license -- they're delusional.
Just as game companies benefit from pirating in some circumstances, more publicity is a good thing. If I'm going to sell ads, I want it as widely known as possible. I might get a gig like Linus. Without several thousand users you can't do much.
Yeah,it would be difficult to do adware. I guess I'm stuck with site advertising. I thought I heard YouTube pays a penny a view. I got 74,000 views on my video. $740 in a year is not going to do me much good except hassle my tax filing.
Looks grim, quite honestly.
Everything points toward VMWare in the future and that really ruins everything. Makes OS just an app.
How about it anon? >> first to the reverse-engineering code =)
Build a program which first, identifies function declarations in a piece of code, secondly maps functions to their 'parent/caller function(s)?' and third outputs the overall structure in a readable fashion.... ?
I did an unassembler in addition to the compiler/assembler. Go have fun. It's 100% open source -- you sound confused. You want me to make hacking tools? It boots from a CD, can read/write hard drive blocks and has my unassembler. I don't want to gain notoriety--I'd rather you did harmless video games with it, but have fun. When I was a kid, I did that on my C64 -- that's how you learn. It's really nasty, today, for kids.
I have no respect for reverse engineers -- I had a job doing that once and viewed it as a humiliation. I'd rather be architect of a new OS.
It would be a non-harmful type hacking tool =)
...Operating on the (Open? / otherwise sourced..?) source-code rather than compiled / disassembling stuff...
Name:
n3n7i2011-09-15 0:25
=) heeheehee! ...
... I am a witty kid. heeheehee
... I smell like piss... =) heeheehee!
You are speaking of an uncompiler, I think they're called. that's in my realm of expertise, but not at all needed in LoseThos since it's 100% open source... and no code enters which hasn't been compiled by my compiler, in all likelyhood. You might entertain yourself by unassembling BIOSes, but my 16-bit unassembler quality is poor.
Why don't you try to be an engineer instead of reverse engineer? Go architect something.
10 i = i + 1
15 IF i > 99999 THEN PRINT ".";: i = 0
20 IF INKEY$ = "" THEN 10
30 PRINT "King James Bible, Line:", i
God says...
Line: 95035
righteousness which is in the law, blameless.
3:7 But what things were gain to me, those I counted loss for Christ.
3:8 Yea doubtless, and I count all things but loss for the excellency
of the knowledge of Christ Jesus my Lord: for whom I have suffered the
loss of all things, and do count them but dung, that I may win Christ,
3:9 And be found in him, not having mine own righteousness, which is
of the law, but that which is through the faith of Christ, the
righteousness which is of God by faith: 3:10 That I may know him, and
the power of his resurrection, and the fellowship of his sufferings,
being made conformable unto his death; 3:11 If by any means I might
attain unto the resurrection of the dead.
aul had
adjured the people, saying, Cursed be the man that eateth any food
until evening, that I may be avenged on mine enemies. So none of the
people tasted any food.
14:25 And all they of the land came to a wood; and there was honey
upon the ground.
14:26 And when the people were come into the wood, behold, the honey
dropped; but no man put his hand to his mouth: for the people feared
the oath.
14:27 But Jonathan heard not when his father charged the people with
the oath: wherefore he put
reverse-engineering might've been the wrong term...?
If you're given 100,000 lines of code, which you know very little about.... it's close enough to reverse engineering just to figure out what that code does.. is this illegal?
>>56
LoseThos is public domain -- no strings attached. The look-up feature brings you to source code where the header for functions might have some documentation. My thought was it's for programmers, so the code would explain many things. There is documentation and demo examples. There's a tour.
tdavis, please go to /g/. They all love your operating system and talk about it all the time. I am sure they would appreciate it if you made threads there.
Name:
Anonymous2011-09-16 8:16
terry, if LoseThos is opensource, why is half the source missing?
Why don't you release the source of your compiler?
Why don't you release the source as proper archive, zip or tar, as other people do?
Why do you insist that people could possibly give a fuck about your own archive implementation, when there are already perfectly fine archive implementations around, like zip and tar?
I wisely chose 640x480x4 because it's incredibly responsive. If you change the graphics resolution it will be a dog.
lol, tdavis is a complete idiot. How come any decent operating system can run 1080p and beyond without being 'a dog'? Enjoy your shit programming skills.
Name:
Anonymous2011-09-16 8:53
More shit from tdavis...
>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.
Name:
Anonymous2011-09-16 8:56
[fixed quotes]
More shit from tdavis...
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.
Amateur OS developers don't actually bother to write applications like flight simulators. They just putz around, maybe run Doom at 320x200
Name:
Anonymous2011-09-16 9:16
>>76
Did you know that 640x480x4 is no true limitation; you only think you are limited to it because you are too poor of a programmer to support a higher resolution? Did you know that there is a standard called "VESA" that allows you to write an essentially universal video driver that will drive monitors at higher resolutions and bit depths?
Name:
FrozenVoid2011-09-16 9:25
Unlimited Detail point-cloud engine will make the GPUs obsolete. Keep on working on the OS, terry, The graphics can be always fixed later, the OS itself isn't something which should satisfy every whim of game industry it always a conceptual creation with graphics serving as filler. If the OS gives direct access to hardware(and losethos at cursory glance allow very low-level interrupt/memory access), another renderer can be written and since its opensource everyone should stop whining and code their "1080p real-time" graphic engine.
>>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.