Since you were borth in the US in the 60's you were probably circumcised. Since that is a very painful event for an infant and quite traumatic -- surely you remember that as well. What was that like?
This is incomplete information.. You aren't just paying the $0.40 per share -- you are also LIABLE for the stock's future price should it actually RISE. This means that if UBS were to go to $55, you would have to fork over additional dough to cover the put (probably something like $9.60 per share!!).
Although you have to throw only like 1% of the price of the stock in as an investment and can potentially make huge amounts, if the stock's price rises you are pretty much fsck'ed and there is no limit to how much money you can theoretically LOSE! (This is unlike regular trades where the amount you can lose is bounded by the price of the stock when you bought it).
Unless you are a hick.. it ain't SolAIRis!
on
Review: Solaris
·
· Score: 1
people from the southern region of the US are the only people justified in pronouncing it solAIRis.. unless you are one of them you are pronouncing it wrong.
Well he's either a troll or a Karma whore. He makes a retarded argument. Basically you are correct. In java you can either ignore the exception and get a reasonable error message with zero effort from you.. or you can have a big try statement wherever you want to and catch (OutOfMemoryException e).
The alternative in C is ugly. A million if() statements for every malloc that basically do the explicit checking. Big whoop.
Actually the java approach is superior in the sense that at least the vm tells you "Out of memory" with zero work from you as a programmer. With C you have the extra "printf("Out of memory\n"); exit(ENOMEM);" code after every malloc. In fact the Exceptional approach to memory is way better IMHO.
Java can never be as fast as C or C++. I don't know what 'your benchmarks' are, but have you published them? I think you are outright lying if you have ever been able to get Java to perform faster than any native binary in a sufficiently _fair_ test. It defies logic. Every Java 'instruction' in the bytecode translates to tens if not hundreds of actual machine instructions. Its slow and bloated.
There are, however, skewed tests which make Java look faster by making the C++ code used in the test do things the "dumb way" by passing around a lot of object copies rather than references.. this type of thing makes Java look almost as fast as C++ _on a very limited subset of problems_ (even with all the object coping). Java programmers claim this is a fair test because everything except (for the most basic types) is a reference in Java. The Java pundits like to point this out and say "yeah Java is faster because all objects are references". This can be true if you are a dumb C++ programmer with no sense of efficiency.. but just a little extra effort can get you as a programmer to think in terms of what is more efficient and use references when you can and thus you leave Java in the dust. Native binaries are several orders of magnitude faster than Java's interpreted bytecode. It's a pure fact. Anything else is FUD.
They write papers, and show imperical evidence on these subjects all the time, there is mass peer review going on right now (and in the last several years) about OO. Please don't just shrug it off as a trend.
Just what empirical evidence is there that OO is 'better' than functional programming or declarative programming? When it comes to programming, it's a matter of style and relative conceptual convenience rather than 'empirical evidence'.
Actually most Computer Scientists tend to sing the praises of Lisp and Scheme and maybe SML rather than C++, Java, or whatever.
This was a bug on some AMD K6 CPU's. The hlt instruction is used in an idle loop to tell the CPU that nothing's happening. The CPU can then reduce its power consumption and generally cool itself off if it gets a bunch of these instructions in a row.
This instruction is used as a power management technique, and also helps cool the cpu down.
Anyway the hlt instruction should work, but for some reason was broken on some AMD K6 cpu's. The solution was to pass a special kernel parameter (I think) to get linux to not use that instruction. Either that or compile without APM support.. I forget now...
Re:offtopic linux (debian) question
on
Going Up?
·
· Score: 1
Why debian tho? Debina is crap.. it doesn't get updated nearly enough. They are always like months behind the other distros in terms of software newness.
Get gentoo if you feel like compiling everything and you have an internet connection.. otherwise go with something else like mandrake or redhat... they have floppy installers I think.
Great. More time wasted installing in Linux
on
Doom3 and OpenGL2.0
·
· Score: 3, Funny
GREAT. Just when I managed to FINALLY get OpenGL 1.2 working in Linux, I have to now struggle with getting OpenGL 2.0 working. Can you say: sleepless nights and/or much frustration?
Also, I hope the card manufacturers get off their derriers and actually release OpenGL 2.0 drivers and libraries faster than like 2 years after they do it for Windows. Stupid MS loving bastardos!!
Hey, you remember the arcade game in the 80's called Beat Street II - Electric Boogaloo? Or was it a movie? Oh yeah I think it was a movie about breakdancing. Or was it a game?
Because J. Random Moron doesn't have the wherewithall to figure out how to traverse his filesystem and double-click on these funny things called.EXE's. He also has no clue about how to delete files. Instead he knows how to double click on little pictures and sometimes, if he's really clever, he'll figure out how to get to the start menu and 'uninstall' software.
So at the very least, software needs to register itself with the windows add/remove programs thing, and it probably needs to put a few icons on the desktop and in the control panel. Just those actions alone constitute an installation process.:)
Amen to that, only incompetents are out of work.
on
The Laid-off Techie
·
· Score: 0, Flamebait
I think that only the fluff jobs are in short demand.
People who are _actually_ useful (such as programmers and other true techies as you mention) can still find a job these days. Maybe they won't be at a place that lets them come in at noon and play foosball in their slippers, but they will still be able to find a job.
Heh porting anything from Qt2 to Qt3 is pretty trivial. Somehow i doubt that they would add a major version number to KDE just because of that. I think you may be mistaken on what KDE 3 was originally 'supposed' to be.
I am not familiar with the kernel mechanisms for allocating GARTs, but it sounds like all you need to do is have the agpgart.o module, when it's creating a GART, somehow tell the kernel memory allocator and the page table handling code not to set up this region as cacheable.
The problem is that probably none of the page table code cares to distinguish between cacheable and non-cacheable pages. But anyway it shouldn't be too bad to set up such a distinction.
Anyway I haven't looked at the kernel code that relates to this yet so I am not sure if I am over-simplifying things... but I trust that someone will have a hack to fix this soon (a hack that doesn't cost anything in performance, unlike that mem=nopentium option), and a proper patch that is more beautiful would probably come out a few days after that....
However, since NVIDIA's stupid bloated drivers contain their *own* agp GART code, we would also have to coordinate with that vendor to get them to change their GART code to behave properly. Either that or you can try using the linux kernel's agpgart.o with NVdriver, but in my experience Very Bad Things happen why you do that!:)
Mod the guy that posted this thing above me up. He knows what the hell he is talking about. I was about to post exactly what he just said but I see he said it and said it eloquently.
We make our own reality. Right now we think windows is the true reality and Linux is the way reality ought to be. If everyone used Linux, it would be reality and Windows would be on the garbage heap of history, where it belongs. The point about users needing an expert around to help them with their random computer troubles is really good.
And the thing with Linux is, when you actually have computer problems, there are always ways to fix them. Most of the way that things work in Windows' internals are obfuscated and non-obvious, and very poorly documented even if you dig deep into the bowels of the MS site. Best case you find some stupid KB article that kind of relates to your problem, and you get a step-by-step on how to fix it. A lot of it seems like voodoo rather than actual trouble-shooting.
With Linux, you ALWAYS have the source code. You ALWAYS know what is going on. If enough people ran linux, the overall intelligence level of computer users would rise. It's kind of a trickle-down effect. Sort of made possible by the six degrees of separation.
You are absolutely right, brother. I agree with you wholeheartedly. Linux is a great desktop OS. I began teaching my doctor friends how to use it and they picked it up quick (granted, they probably have above average IQs) and they are computer-illiterate. Many of them really like the eye-candy of Gnome with Enlightenment and really like the idea that they are working on unix machines. (some of them associate unix with high-profile computational research stuff that they used to do back in academia).
In fact, RT guy *regularly* slams anything that doesn't have adequate RT support, so I am left to assume that he deems to have a set of RT capabilities which is more than adequate.:)
I recently attended a talk in which a NIST (National Institute of Science and Technology) guy spoke about his criteria for evaluating a realtime OS. He basically said that he's tested and evaluated every realtime OS under the sun and to him, RTAI (another realtime linux variant similar to the RT-Linux implementation Yodaiken worked on) is one of the best real-time OS's one can get on intel hardware. The worst-case numbers just about proved this to him. Really it was quite an interesting talk.. a lot of fancy statistical gymnastics goes into evaluating a realtime OS, and RTAI came out ahead.
And it has fast interprocess communication that's not a bolt-on to UNIX.
Huh?
And it's a real ROMable microkernel.
Huh? The Linux kernel is also ROMable. If you want a microkernel (something I think is a bit wasteful in something like an embedded system), go back up to that fiasco link I put up on top.
Slashdot Mirror
Who cares about this ugly machine?
Since you were borth in the US in the 60's you were probably circumcised. Since that is a very painful event for an infant and quite traumatic -- surely you remember that as well. What was that like?
Just curious.
This is incomplete information.. You aren't just paying the $0.40 per share -- you are also LIABLE for the stock's future price should it actually RISE. This means that if UBS were to go to $55, you would have to fork over additional dough to cover the put (probably something like $9.60 per share!!).
Although you have to throw only like 1% of the price of the stock in as an investment and can potentially make huge amounts, if the stock's price rises you are pretty much fsck'ed and there is no limit to how much money you can theoretically LOSE! (This is unlike regular trades where the amount you can lose is bounded by the price of the stock when you bought it).
people from the southern region of the US are the only people justified in pronouncing it solAIRis.. unless you are one of them you are pronouncing it wrong.
Well he's either a troll or a Karma whore. He makes a retarded argument. Basically you are correct. In java you can either ignore the exception and get a reasonable error message with zero effort from you.. or you can have a big try statement wherever you want to and catch (OutOfMemoryException e).
The alternative in C is ugly. A million if() statements for every malloc that basically do the explicit checking. Big whoop.
Actually the java approach is superior in the sense that at least the vm tells you "Out of memory" with zero work from you as a programmer. With C you have the extra "printf("Out of memory\n"); exit(ENOMEM);" code after every malloc. In fact the Exceptional approach to memory is way better IMHO.
Java can never be as fast as C or C++. I don't know what 'your benchmarks' are, but have you published them? I think you are outright lying if you have ever been able to get Java to perform faster than any native binary in a sufficiently _fair_ test. It defies logic. Every Java 'instruction' in the bytecode translates to tens if not hundreds of actual machine instructions. Its slow and bloated.
There are, however, skewed tests which make Java look faster by making the C++ code used in the test do things the "dumb way" by passing around a lot of object copies rather than references.. this type of thing makes Java look almost as fast as C++ _on a very limited subset of problems_ (even with all the object coping). Java programmers claim this is a fair test because everything except (for the most basic types) is a reference in Java. The Java pundits like to point this out and say "yeah Java is faster because all objects are references". This can be true if you are a dumb C++ programmer with no sense of efficiency.. but just a little extra effort can get you as a programmer to think in terms of what is more efficient and use references when you can and thus you leave Java in the dust. Native binaries are several orders of magnitude faster than Java's interpreted bytecode. It's a pure fact. Anything else is FUD.
Remember the South Park episode where the dwarves are stealing people's underwear for profit?
Their plan was:
1. Steal Underwear
2. ?
3. Profit!
"Why use FreeBSD when Linux seems to work better, and have greater support at the same time? "
1.Ports
2.Packages
3.easy update (make buildworld etc..)
4.The Devil not that fat fucking penguin
Gentoo linux takes care of 1-3. Yeah the penguin is a fag.. I agree.
Just what empirical evidence is there that OO is 'better' than functional programming or declarative programming? When it comes to programming, it's a matter of style and relative conceptual convenience rather than 'empirical evidence'.
Actually most Computer Scientists tend to sing the praises of Lisp and Scheme and maybe SML rather than C++, Java, or whatever.
This was a bug on some AMD K6 CPU's. The hlt instruction is used in an idle loop to tell the CPU that nothing's happening. The CPU can then reduce its power consumption and generally cool itself off if it gets a bunch of these instructions in a row.
This instruction is used as a power management technique, and also helps cool the cpu down.
Anyway the hlt instruction should work, but for some reason was broken on some AMD K6 cpu's. The solution was to pass a special kernel parameter (I think) to get linux to not use that instruction. Either that or compile without APM support.. I forget now...
Why debian tho? Debina is crap.. it doesn't get updated nearly enough. They are always like months behind the other distros in terms of software newness.
Get gentoo if you feel like compiling everything and you have an internet connection.. otherwise go with something else like mandrake or redhat... they have floppy installers I think.
Also, I hope the card manufacturers get off their derriers and actually release OpenGL 2.0 drivers and libraries faster than like 2 years after they do it for Windows. Stupid MS loving bastardos!!
Hey, you remember the arcade game in the 80's called Beat Street II - Electric Boogaloo? Or was it a movie? Oh yeah I think it was a movie about breakdancing. Or was it a game?
Help!
It had better games, also had 16 colors, and had a great 3-channel music synthesizer. It also tended to be better with sprite animation.
It also came out like 3 years before the Pcjr.
Because J. Random Moron doesn't have the wherewithall to figure out how to traverse his filesystem and double-click on these funny things called .EXE's. He also has no clue about how to delete files. Instead he knows how to double click on little pictures and sometimes, if he's really clever, he'll figure out how to get to the start menu and 'uninstall' software.
:)
So at the very least, software needs to register itself with the windows add/remove programs thing, and it probably needs to put a few icons on the desktop and in the control panel. Just those actions alone constitute an installation process.
I think that only the fluff jobs are in short demand.
People who are _actually_ useful (such as programmers and other true techies as you mention) can still find a job these days. Maybe they won't be at a place that lets them come in at noon and play foosball in their slippers, but they will still be able to find a job.
Heh porting anything from Qt2 to Qt3 is pretty trivial. Somehow i doubt that they would add a major version number to KDE just because of that. I think you may be mistaken on what KDE 3 was originally 'supposed' to be.
I am not familiar with the kernel mechanisms for allocating GARTs, but it sounds like all you need to do is have the agpgart.o module, when it's creating a GART, somehow tell the kernel memory allocator and the page table handling code not to set up this region as cacheable.
:)
The problem is that probably none of the page table code cares to distinguish between cacheable and non-cacheable pages. But anyway it shouldn't be too bad to set up such a distinction.
Anyway I haven't looked at the kernel code that relates to this yet so I am not sure if I am over-simplifying things... but I trust that someone will have a hack to fix this soon (a hack that doesn't cost anything in performance, unlike that mem=nopentium option), and a proper patch that is more beautiful would probably come out a few days after that....
However, since NVIDIA's stupid bloated drivers contain their *own* agp GART code, we would also have to coordinate with that vendor to get them to change their GART code to behave properly. Either that or you can try using the linux kernel's agpgart.o with NVdriver, but in my experience Very Bad Things happen why you do that!
-Calin
Yes, that's true. I speak with my voice though, since I am a programmer. But point well taken.
We make our own reality. Right now we think windows is the true reality and Linux is the way reality ought to be. If everyone used Linux, it would be reality and Windows would be on the garbage heap of history, where it belongs. The point about users needing an expert around to help them with their random computer troubles is really good.
And the thing with Linux is, when you actually have computer problems, there are always ways to fix them. Most of the way that things work in Windows' internals are obfuscated and non-obvious, and very poorly documented even if you dig deep into the bowels of the MS site. Best case you find some stupid KB article that kind of relates to your problem, and you get a step-by-step on how to fix it. A lot of it seems like voodoo rather than actual trouble-shooting.
With Linux, you ALWAYS have the source code. You ALWAYS know what is going on. If enough people ran linux, the overall intelligence level of computer users would rise. It's kind of a trickle-down effect. Sort of made possible by the six degrees of separation.
You are absolutely right, brother. I agree with you wholeheartedly. Linux is a great desktop OS. I began teaching my doctor friends how to use it and they picked it up quick (granted, they probably have above average IQs) and they are computer-illiterate. Many of them really like the eye-candy of Gnome with Enlightenment and really like the idea that they are working on unix machines. (some of them associate unix with high-profile computational research stuff that they used to do back in academia).
Man you are hilarious. Brilliantly funny!
That java will die guy was pretty free of any technical content.
I recently attended a talk in which a NIST (National Institute of Science and Technology) guy spoke about his criteria for evaluating a realtime OS. He basically said that he's tested and evaluated every realtime OS under the sun and to him, RTAI (another realtime linux variant similar to the RT-Linux implementation Yodaiken worked on) is one of the best real-time OS's one can get on intel hardware. The worst-case numbers just about proved this to him. Really it was quite an interesting talk.. a lot of fancy statistical gymnastics goes into evaluating a realtime OS, and RTAI came out ahead.
So does an implementation of realtime linux:
http://os.inf.tu-dresden.de/drops
http://os.inf.tu-dresden.de/fiasco
http://os.inf.tu-dresden.de/LinuxOnL4
So does the DWCS scheduler for Linux Systems:
http://www.cc.gatech.edu/~west/dwcs.html
Huh?
Huh? The Linux kernel is also ROMable. If you want a microkernel (something I think is a bit wasteful in something like an embedded system), go back up to that fiasco link I put up on top.