And just for comparison, the BeOS app_server takes up ~44 MB of ram with a modest number of apps running. ~10 MB of that is resident. The framebuffer of my 16 meg voodoo3 doesn't appear to be part of that. (lots of shared libs & unused stack space (~60 threads))
There isn't one aspect of computing that BeOS excels at.
You name an aspect, and I'll name five other modern
operating systems which do the same thing better, and
have and established userbase and software market to boot.
Ok, I'm game. Show me an OS (or five as you suggest) that's as easy to develop for as BeOS, and I'll videotape myself reformatting my hard disk. (Don't forget the part about the replacement(s) having an established userbase and software market) This means it would have to meet or exceed the ease of multithreaded programming - among other things - on BeOS.
Still with me? An ideal system would allow me to reimplement this app: Jeepers Elvis!
I should be able to meet or exceed the abilities I already get from the BeOS implementation in two weeks or less. (that's how long the actual coding took) I've got the design on paper, so reimplementation wouldn't be any hairier than the API I use to implement it.
(Sorry for the blantant plug, but this is the key reason I use BeOS. (and the reason I will continue to))
They don't bother with the piss test in most companies in the valley. I've seen nerf fights, pool, hacky sack and maybe some go carting with the office push cart and every get while beer and wine drinking but not a hole lot of drugs. You can go into my office at almost any hour and some one sitting there hacking away. They aren't wacked out on drugs to stay running they are just keeping up with the schedule they like. They enjoy what their doing. Weird hours are for creativity.
Remember kids, just read/. when you're stoned. Never post!
The 'environment' for Mac apps was actually just MacOS (for the most part) running as an A/UX process.
There were also choices for running X11R4 or plain 'console' which was a fun little text only mode.
I'm quite glad Apple dropped A/UX. It's the worst unix I've ever dealt with. NeXTSTEP, on the other hand, is the nicest unix-like OS that I've ever used.
And the obvious answer is "why didn't you read the page that was linked?". It states there that they are providing it for Intel and Macintosh hardware.
The whole problem with directory windows not staying synced with what's actually on disk is not a problem on BeOS. The Tracker uses a special feature of the file system called node monitoring. This means that if your monitoring a node (which can be a directory), then you will get a message whenever something happens. No polling involved. Very smooth.
many universities state very clearly that they will periodically monitor traffic on their networks. By using the network, it is assumed that you are aware of this.
Just because Apple won't hand hold them through desiging their OS, the Be engineers are a bit peeved.
Talk about total flamebait. Ok, so I'm biting. Shame on me. I'd just like to say that Be was whining about Apple being totally uninterested in helping them run on newer mac hardware. Hey, they can do whatever the hell they want to. As for Be needing help designing thier OS, give me a fucking break. No one could make it that far without knowing anything about OS design.
Ah yes, the dark practices of the "Church" of Scientology. My high school German teacher had a great story about scientology. Back in his younger days, he angered the church enough that they declared him officially dead. So somewhere in the churches files, there is record of my teacher's death, even though he is quite alive to this day. (apparently he was supposed to die after they declared him dead... don't ask)
I dunno, people like that freak me out. The German govt. is right to be suspicious of them even if their measures may seem extreme at times.
What makes a graphics card so different from any other card in your machine? Nobody said you had to stuff the X server into the kernel. All you really need is the code that talks to the hardware.
I spent a good chunk of my summer writing perl code and making good money at it. You know what? I don't miss the money one bit.. cause I don't have to look at perl ever again if I don't want to. More time for python/c/c++:)
Well, two avis, but you're got a point. Perhaps some info about the two movies. They are 29 fps with sound and Indeo5 encoding. Be's Indeo decoder is most likely straight c or c++, so of course it's a bit slower than it could be.
The previous reply is right too. Unused cpus are wasted cash.. but then, that's what rc5 is for right?:)
Ports are message queues. Areas are chunks of virtual memory. The servers are kinda like daemons, app_server is the windowing system, net_server the networking, etc.
Another stumbling block in a linux compatibilty could be the difference in threading. On BeOS, all threads are kernel threads. There are no pthreads. The BeOS equivilent of a unix process would be a team, and a team is a bunch of threads sharing the same virtual address space. Kind of nice when you're calling functions that might block for a noticeable amount of time.
Is it just me, or did Number 2 look like he was laughing his ass off when Dr. Evil was throwing the big globe in his face ?
Re:Whatever happened to 64 bits?
on
K7 Info
·
· Score: 1
BFS can handle files larger than 18 terabytes. I'm not going to put down a number, because then I would be the third person that gave a wrong number in this thread:) If you really must know what BFS can handle, go to Barnes and Noble and thumb through Dominic G's filesystem book.
As for Genki, chill out... It's so close you can almost taste it. Barring nuclear war you should have it installed RSN.
Slashdot Mirror
And just for comparison, the BeOS app_server takes up ~44 MB of ram with a modest number of apps running. ~10 MB of that is resident. The framebuffer of my 16 meg voodoo3 doesn't appear to be part of that. (lots of shared libs & unused stack space (~60 threads))
:P
That still doesn't make X not suck.
Still with me? An ideal system would allow me to reimplement this app:
Jeepers Elvis!
I should be able to meet or exceed the abilities I already get from the BeOS implementation in two weeks or less. (that's how long the actual coding took) I've got the design on paper, so reimplementation wouldn't be any hairier than the API I use to implement it.
(Sorry for the blantant plug, but this is the key reason I use BeOS. (and the reason I will continue to))
One troll to another....
Cheers
- John Wiggins
for those of you who haven't seen it, here's a link:
link
In other news, a link was posted in a slashdot comment today that wasn't to goatse.cx...
I was about to say the same thing...
There was almost a point to the post if you realize that not everyone is familiar with the basics of astronomy.
Just because I'm a worthless pedant...
It's one thing if you learn mycology and go out and collect peyote buttons
Mycology refers to mushrooms, not cacti.
Remember kids, just read
- prok
The 'environment' for Mac apps was actually just MacOS (for the most part) running as an A/UX process.
There were also choices for running X11R4 or plain 'console' which was a fun little text only mode.
I'm quite glad Apple dropped A/UX. It's the worst unix I've ever dealt with. NeXTSTEP, on the other hand, is the nicest unix-like OS that I've ever used.
And the obvious answer is "why didn't you read the page that was linked?". It states there that they are providing it for Intel and Macintosh hardware.
RTFL!
The whole problem with directory windows not staying synced with what's actually on disk is not a problem on BeOS. The Tracker uses a special feature of the file system called node monitoring. This means that if your monitoring a node (which can be a directory), then you will get a message whenever something happens. No polling involved. Very smooth.
many universities state very clearly that they will periodically monitor traffic on their networks. By using the network, it is assumed that you are aware of this.
Is it really that hard to figure out what a girl might like about a python? (or 'python' in this case)
Get you mind in the gutter soldier!
Just because Apple won't hand hold them through desiging their OS, the Be engineers are a bit peeved.
Talk about total flamebait. Ok, so I'm biting. Shame on me. I'd just like to say that Be was whining about Apple being totally uninterested in helping them run on newer mac hardware. Hey, they can do whatever the hell they want to. As for Be needing help designing thier OS, give me a fucking break. No one could make it that far without knowing anything about OS design.
I'll register the domain right now... :P
Actually, I'd expect users who deal with X to be far more comfortable using their middle finger when using the computer...
http://members.tripod.com/~random___boy/nephew.jpg
:)
The poor kid was born on x-mas day, he deserves this much.
Ah yes, the dark practices of the "Church" of Scientology. My high school German teacher had a great story about scientology. Back in his younger days, he angered the church enough that they declared him officially dead. So somewhere in the churches files, there is record of my teacher's death, even though he is quite alive to this day. (apparently he was supposed to die after they declared him dead... don't ask)
I dunno, people like that freak me out. The German govt. is right to be suspicious of them even if their measures may seem extreme at times.
All you gotta do is write it in perl...
What makes a graphics card so different from any other card in your machine? Nobody said you had to stuff the X server into the kernel. All you really need is the code that talks to the hardware.
This is a quick hack, but the output looks just fine...
------------BEGIN UGLY C PROGRAM-----------
#include
unsigned char bin2asc(char *string);
int main(int argc, const char **argv)
{
FILE *in;
char line[512];
if ((in = fopen("nitrobin", "r")) != NULL)
{
char binary[9];
int count=0;
while (fscanf(in, "%s", binary) != EOF)
{
printf("%c", bin2asc(binary));
count++;
if(count == 48)
puts("");
}
}
puts("");
return 0;
}
unsigned char bin2asc(char *string)
{
unsigned char ret = 0;
ret |= (string[0] == '1') ? 0x80 : 0;
ret |= (string[1] == '1') ? 0x40 : 0;
ret |= (string[2] == '1') ? 0x20 : 0;
ret |= (string[3] == '1') ? 0x10 : 0;
ret |= (string[4] == '1') ? 0x08 : 0;
ret |= (string[5] == '1') ? 0x04 : 0;
ret |= (string[6] == '1') ? 0x02 : 0;
ret |= (string[7] == '1') ? 0x01 : 0;
return ret;
}
I spent a good chunk of my summer writing perl code and making good money at it. You know what? I don't miss the money one bit.. cause I don't have to look at perl ever again if I don't want to. More time for python/c/c++ :)
Well, two avis, but you're got a point. Perhaps some info about the two movies. They are 29 fps with sound and Indeo5 encoding. Be's Indeo decoder is most likely straight c or c++, so of course it's a bit slower than it could be.
:)
The previous reply is right too. Unused cpus are wasted cash.. but then, that's what rc5 is for right?
Ports are message queues. Areas are chunks of virtual memory. The servers are kinda like daemons, app_server is the windowing system, net_server the networking, etc.
Another stumbling block in a linux compatibilty could be the difference in threading. On BeOS, all threads are kernel threads. There are no pthreads. The BeOS equivilent of a unix process would be a team, and a team is a bunch of threads sharing the same virtual address space. Kind of nice when you're calling functions that might block for a noticeable amount of time.
Is it just me, or did Number 2 look like he was laughing his ass off when Dr. Evil was throwing the big globe in his face ?
BFS can handle files larger than 18 terabytes. I'm not going to put down a number, because then I would be the third person that gave a wrong number in this thread :) If you really must know what BFS can handle, go to Barnes and Noble and thumb through Dominic G's filesystem book.
As for Genki, chill out... It's so close you can almost taste it. Barring nuclear war you should have it installed RSN.