(what if) you used a joystick for steering, acceleration, and braking? It'd work (and probably better than what we've already got), but it'd sure as hell confuse him, wouldn't it?
If you grew up playing racing games, you'd only be confused as to why people yell at you when you hit them, and why you're driving a POS instead of a 'vette...
Example: I've been using Linux for a few weeks now. I still can't figure out how to use Gnome to install software via.rpm (need to be root). Is that something I can remedy by reading man pages or usenet?
Had a guy at work with the same problem. I didn't play with the gnome package tool long enough to get a feel for it. My first impression (as with many things, so no real slam here) was that it sucked. Your best bet is the command line.
rpm -Uvh (your-package-here).rpm
If it can't find the package file ("no such file or directory") try cd'ing to the directory the package is contained in.
If you're not root, either log in as root or use the "su" command. It should prompt you for a root password.
This is honestly your long-term best bet as any rpm-based system will have the 'rpm' command. There is also a man page for rpm. Have fun.
The number of non-geek people I know that have even HEARD of Linux, let alone use it, is ZERO.
Must disagree on the 'heard of' part. But yeah, I only see at-least-semi geeks using it.
The licence dispute was just an excuse to start up a KDE competitor that every man and his dog could jump in and try his own pet ideas however loopy.
That's a bit harsh. Some people (myself included) believe there were Real Problems with the kde 1 licensing scheme. Combine this with architectural disagreements and a strong anti-c++ (plus moc) sentiment (to be fair, g++ sucked a lot worse in.. 98? than it does now) and you get Gnome. Personally I would have worked on getting Harmony (qt clone) up to snuff. But, I didn't. At least Miguel got off his ass and did something.
All I can derive from the kde-gnome wars is that it's better to get something out and make incremental improvements than to reach for perfection (and talk a lot) and never ship a stable release. Sortof reminds me of konq vs. mozilla actually. Cripes, better cut this short before I start drifting on-topic...
Youd be suprised what Linus could actually get away with in reality.
Maybe. My personal guess is he would have to throw away the networking layer, memory management (which sucked anyway:) and almost all the drivers, including all the filesystems (except minix. ext2 was mostly remy card's work) These are "substantial contributions". He'd probably end up with what berkeley had after the at&t lawsuit, core bits of a kernel that would take several years to make functional again.
If you expose an API, and particularly, unrestricted driver source for a chip, it makes it considerably easier for other companies to reverse-engineer and "clone" a knockoff.
Example: look at all the tulip (network card) chipset clones out there. Last I checked they don't win on being better than the tulip, most of them are actually
crappier; they win on being cheaper parts that (basically) work with already-written software.
And apparently it's not that hard. Quoting a coward from an early soundblaster article (only the most reliable sources here!), "weitek reverse engineered one of Sun's graphics chipsets because they got hold of a single.h with the register specs".
However it seems to me this strategy is only of any use when you're a big player with a popular chipset, trying to keep the little players down. My perception is that Trident is neither, so why they are doing this is beyond me.
In fact, aside from Ada 95, C++ is the ONLY programming language I know of that doesn't have garbage collection.
Misleading. ada95 rm, 4.8 "allocators" note 15: "Implementations are permitted, but not required, to provide garbage collection".. Granted, no vendor I know ever implemented this, but I've only had experience with two implementations.
C++ will be dead within 5-10 years. It would be shameful to try to develop a large-scale project like a GUI-based OS on such a broken language and tout it as a next generation OS.
That's ironic as I'm writing this from a KDE desktop. c++ will be dead? Ignoring your statement's trollish nature, provided you only use the good features (not that anybody can agree on what those are), I believe it's a fairly powerful superset to c. I particularly miss constructors, destructors, and multiple inheritance when coding in straight c.
Some os's do stupid things in the name of "convenience" that could be taken maliciously.
Most people installing windows wouldn't know what the hell a bootsector even is. And I doubt you could explain it to them. "Detected an unknown bootsector. Maybe it's garbage. Or maybe it belongs to another operating system that needs it to boot. On the
other hand we need it too. Abort, Ignore?"
94% will be confused; of these 5% will flood tech support asking about "unknown operating systems". 4% (smart linux/bsd users) will know what you're talking about but the question is useless to them, since they have to work around it anyway. The last 2% (stupid linux/bsd users) will ignorantly click-thru, blow away their other os, and sue anyway.
BTW, I know this will seem incredibly petty and shallow, but IMHO the real reason BeOS didn't take off was C++.
Only shallow in the sense that you didn't explain yourself. The obvious question (at least to me) is, "Because c++ is 'too slow'? Or 'nobody knows c++'? Or we need compatibility w/legacy code? Or some other reason?"
(yes all the 'reasons' above are debatable in themselves; I just want to know why he said that.)
Face it, most people can't articulate themselves very well and prefer to use boilerplate letters.
Perhaps; but if you're going to be going for theboilerplate solution (read: "less work") it's better to sign a petition than to potentially misrepresent an opinion as entirely your own. It's practically plagarism.
It doesn't make their opinions any less valid.
But it does, simply by the fact that they put less (actually, no) consideration into it. Judging by the number of people who were "misled", how are we even supposed to know what their opinions really are?
some of jupiter's moon's have atmospheres, so it is possible
No Jupiter moon I know of has an atmosphere more substancial than that of Mercury (ie practically none at all). You may be thinking of Titan, which orbits around Saturn.
Gamers don't care which (graphics) API a game uses.
Err... unless the card they're using has a great d3d driver and a crap opengl driver, or vice versa. I want to point out matrox as a historical example, but I'm not sure about that (please educate me), and my matrox card works fine under linux.
Been there. Crappy dos game. Polled the clock until it fell over. The clock precision was crap so I had a slight hitch. Also wasn't taking into account the execution time of the *real* code so when I moved to a 386 (from an XT) I was like.. "damn this is fast"
The better approach for your problem is to use the OS's delay function, if you can. (under unix, try nanosleep() or select() with all the fds fields cleared. Sleep() should work on windows.) You free up the processor for other tasks, you don't have to do that speed-estimating crap, and uh you don't hit yer bug.
I would assume you figured this out but you said your other friend who was smarter than you wrote the code:-).. nice story.
1) I guess it's all relative but I've played quake3 on my g200 at home.. and *liked* it. *sobs*
2) As another poster pointed out, linux quake3 was chiefly an id port. Loki's primary responsibility was making sure I couldn't buy an in-store copy until three months after the christmas season apparently because they felt it had to ship in a tin box.
Getting pedantic on your butt, that's SDL (Simple DirectMedia Layer -- thank another Sam for that). Loki also developed an open-source installer and OpenAL. Check out Loki's development page for a complete list.
3. The developers mostly cannot have the same fun playing the game as others (again, as in 1. there are exceptions), this makes participating for "scratching an itch" impossible.
I believe the exception is the rule. I wrote a crappy tron clone and a crappy chess game back in the olden days. I sure wouldn't have written them if I couldn't have fun playing them.
I read once that id had trouble getting Doom out
due to too much "play-testing".
Most of the rest of your points are spot-on. Nice post.
An email saying "I really enjoy your software a lot, and I'd like to thank you for it -- are there any charities you particularly feel kindly for?" alleviates any possibilities that people would be offended by a cheque
Actually I might be offended if you *didn't* offer to just give the money to me as well. I might think you were haughty-taughty. I might not have any special charities. Or I might tell you my favorite charity was the KKK.
So there are plenty of reasons to just send a cheque.
Stupid kid??? Sounds to me like you have something against young, black people.
Ummm... where did you pull that from dude?
They pulled us out of the car, searched us, and ound our stuff. They laid it on the roof of the vehicle, and turned us around to talk to the officer questioning us. We turned around, and all the "stuff" was gone. The police officer watching the roof of the car let out an assenine remark. He said, I guess the wind got it.
Then you should politely ask "got what?" (and maybe thank him properly). Kindof hard to convict you of a crime if the evidence is missing right?
Why the f*ck is that police officer what he is? He should be pushing burgers down the block from me at the McDonalds.
Well he should be in jail, but whatever. Not having your experience under my belt (interesting story, thx) I'm still going to optimistically assume that most cops aren't that corrupt. (unless of course I'm in L.A.)
Re:I wonder if gcc/g++ 3.0 will make kde3.0 faster
on
KDE 2.2 Tagged
·
· Score: 5, Informative
I just think the fsf version of it really sucks
Well, like, that's just your opinion, man:) could you elaborate on which parts (in gcc 3.0?)
I noticed some code really runs fast on Visual c++ and runs slower and is more bloated on linux with gcc.
gcc's prime advantage over compilers like vc++ is retargetability/portability and (nowadays) standards compliance, not speed (tho it tries).
Anyway I would love to see faster load times on kde3.0.
That's actually a run-time linker (not compiler) issue. (read the dot or the kde mailing lists for more).. "kdeinit" is at least partly a hack to get the load times down. They're still working for more improvements on the kde end, but the last word will be when the binutils guys get their linker more optimized for c++ code.
Do any of you know if the new compiler can help make kde3.0 run better?
Not yet. gcc3.0 has some bugs (again, they're working on it) that causes it to miscompile parts of kde. These issues ought to be resolved by kde3.0 time.
Slashdot Mirror
If you grew up playing racing games, you'd only be confused as to why people yell at you when you hit them, and why you're driving a POS instead of a 'vette...
Had a guy at work with the same problem. I didn't play with the gnome package tool long enough to get a feel for it. My first impression (as with many things, so no real slam here) was that it sucked. Your best bet is the command line.
rpm -Uvh (your-package-here).rpm
If it can't find the package file ("no such file or directory") try cd'ing to the directory the package is contained in.
If you're not root, either log in as root or use the "su" command. It should prompt you for a root password.
This is honestly your long-term best bet as any rpm-based system will have the 'rpm' command. There is also a man page for rpm. Have fun.
The number of non-geek people I know that have even HEARD of Linux, let alone use it, is ZERO.
Must disagree on the 'heard of' part. But yeah, I only see at-least-semi geeks using it.
do you live in australia?
2) Just because you sometimes get more than you pay for, doesn't mean you should expect it.
Especially on /.
Try walking around in the sunshine a little. (my excuse: it's night)
That's a bit harsh. Some people (myself included) believe there were Real Problems with the kde 1 licensing scheme. Combine this with architectural disagreements and a strong anti-c++ (plus moc) sentiment (to be fair, g++ sucked a lot worse in
All I can derive from the kde-gnome wars is that it's better to get something out and make incremental improvements than to reach for perfection (and talk a lot) and never ship a stable release. Sortof reminds me of konq vs. mozilla actually. Cripes, better cut this short before I start drifting on-topic...
Maybe. My personal guess is he would have to throw away the networking layer, memory management (which sucked anyway :) and almost all the drivers, including all the filesystems (except minix. ext2 was mostly remy card's work) These are "substantial contributions". He'd probably end up with what berkeley had after the at&t lawsuit, core bits of a kernel that would take several years to make functional again.
Example: look at all the tulip (network card) chipset clones out there. Last I checked they don't win on being better than the tulip, most of them are actually crappier; they win on being cheaper parts that (basically) work with already-written software.
And apparently it's not that hard. Quoting a coward from an early soundblaster article (only the most reliable sources here!), "weitek reverse engineered one of Sun's graphics chipsets because they got hold of a single .h with the register specs".
However it seems to me this strategy is only of any use when you're a big player with a popular chipset, trying to keep the little players down. My perception is that Trident is neither, so why they are doing this is beyond me.
Misleading. ada95 rm, 4.8 "allocators" note 15: "Implementations are permitted, but not required, to provide garbage collection" .. Granted, no vendor I know ever implemented this, but I've only had experience with two implementations.
C++ will be dead within 5-10 years. It would be shameful to try to develop a large-scale project like a GUI-based OS on such a broken language and tout it as a next generation OS.
That's ironic as I'm writing this from a KDE desktop. c++ will be dead? Ignoring your statement's trollish nature, provided you only use the good features (not that anybody can agree on what those are), I believe it's a fairly powerful superset to c. I particularly miss constructors, destructors, and multiple inheritance when coding in straight c.
Most people installing windows wouldn't know what the hell a bootsector even is. And I doubt you could explain it to them. "Detected an unknown bootsector. Maybe it's garbage. Or maybe it belongs to another operating system that needs it to boot. On the other hand we need it too. Abort, Ignore?"
94% will be confused; of these 5% will flood tech support asking about "unknown operating systems". 4% (smart linux/bsd users) will know what you're talking about but the question is useless to them, since they have to work around it anyway. The last 2% (stupid linux/bsd users) will ignorantly click-thru, blow away their other os, and sue anyway.
Only shallow in the sense that you didn't explain yourself. The obvious question (at least to me) is, "Because c++ is 'too slow'? Or 'nobody knows c++'? Or we need compatibility w/legacy code? Or some other reason?"
(yes all the 'reasons' above are debatable in themselves; I just want to know why he said that.)
Perhaps; but if you're going to be going for theboilerplate solution (read: "less work") it's better to sign a petition than to potentially misrepresent an opinion as entirely your own. It's practically plagarism.
It doesn't make their opinions any less valid.
But it does, simply by the fact that they put less (actually, no) consideration into it. Judging by the number of people who were "misled", how are we even supposed to know what their opinions really are?
Sounds like they don't need a DDOS then. They have problems enough.
so they won't be able to answer any tickets at all -- it's no big loss, 'cause that's how they ALREADY are!
Sounds like they don't need a DDOS then. They have problems enough.
CI Hosting is using Pokemon graphics and characters illegally and in infringement of Nintendo's copyright
Sounds like they don't need a DDOS then. They have problems enough.
Why don't you sic a BSA audit on them and turn them all into free software converts while you're trolling. Do something constructive.
Oh, no. Not with my handwriting.
For the surrealism of it, I'd give out crayons instead.
No Jupiter moon I know of has an atmosphere more substancial than that of Mercury (ie practically none at all). You may be thinking of Titan, which orbits around Saturn.
Err... unless the card they're using has a great d3d driver and a crap opengl driver, or vice versa. I want to point out matrox as a historical example, but I'm not sure about that (please educate me), and my matrox card works fine under linux.
The better approach for your problem is to use the OS's delay function, if you can. (under unix, try nanosleep() or select() with all the fds fields cleared. Sleep() should work on windows.) You free up the processor for other tasks, you don't have to do that speed-estimating crap, and uh you don't hit yer bug.
I would assume you figured this out but you said your other friend who was smarter than you wrote the code :-) .. nice story.
2) As another poster pointed out, linux quake3 was chiefly an id port. Loki's primary responsibility was making sure I couldn't buy an in-store copy until three months after the christmas season apparently because they felt it had to ship in a tin box.
Getting pedantic on your butt, that's SDL (Simple DirectMedia Layer -- thank another Sam for that). Loki also developed an open-source installer and OpenAL. Check out Loki's development page for a complete list.
3. The developers mostly cannot have the same fun playing the game as others (again, as in 1. there are exceptions), this makes participating for "scratching an itch" impossible.
I believe the exception is the rule. I wrote a crappy tron clone and a crappy chess game back in the olden days. I sure wouldn't have written them if I couldn't have fun playing them.
I read once that id had trouble getting Doom out due to too much "play-testing".
Most of the rest of your points are spot-on. Nice post.
Actually I might be offended if you *didn't* offer to just give the money to me as well. I might think you were haughty-taughty. I might not have any special charities. Or I might tell you my favorite charity was the KKK.
So there are plenty of reasons to just send a cheque.
Would you be offended if if money was specifically offered to you for making a certain feature the donor needs?
Just in case you didn't make the distinction (tho I think you did), it's the difference between
1) sending money as a result of implementing a feature
2) sending money with no restrictions, and later expecting a feature to be implemented.
You're talking about 1); your parent is talking about 2).
C'mon, I think leo screaming "I'm the King of the Dead!" would be kindof cute, don't you think?
Ummm... where did you pull that from dude?
They pulled us out of the car, searched us, and ound our stuff. They laid it on the roof of the vehicle, and turned us around to talk to the officer questioning us. We turned around, and all the "stuff" was gone. The police officer watching the roof of the car let out an assenine remark. He said, I guess the wind got it.
Then you should politely ask "got what?" (and maybe thank him properly). Kindof hard to convict you of a crime if the evidence is missing right?
Why the f*ck is that police officer what he is? He should be pushing burgers down the block from me at the McDonalds.
Well he should be in jail, but whatever. Not having your experience under my belt (interesting story, thx) I'm still going to optimistically assume that most cops aren't that corrupt. (unless of course I'm in L.A.)
Well, like, that's just your opinion, man :) could you elaborate on which parts (in gcc 3.0?)
I noticed some code really runs fast on Visual c++ and runs slower and is more bloated on linux with gcc.
gcc's prime advantage over compilers like vc++ is retargetability/portability and (nowadays) standards compliance, not speed (tho it tries).
Anyway I would love to see faster load times on kde3.0.
That's actually a run-time linker (not compiler) issue. (read the dot or the kde mailing lists for more) .. "kdeinit" is at least partly a hack to get the load times down. They're still working for more improvements on the kde end, but the last word will be when the binutils guys get their linker more optimized for c++ code.
Do any of you know if the new compiler can help make kde3.0 run better?
Not yet. gcc3.0 has some bugs (again, they're working on it) that causes it to miscompile parts of kde. These issues ought to be resolved by kde3.0 time.
Sorry for misunderstanding you. Mod parent down.