Maybe I'm nitpicking, but why are you comparing the price of a processor made at 90nm (Windsor - AMD gives codenames to all of the cores of each cpu they produce) with one at 65nm (Brisbane)? There is more to a processor than just clocked speed. It's a lot harder to make a higher density chip, so a 65nm chip clocked at 4400+ is going to cost more than a 90nm one at 4600+. Benchmarks show that aside from situation where Brisbane's slightly higher cache latency causes a negligible difference, they perform identically. 4400+ Brisbane and 4600+ Windsor have the same amount of L1/L2 cache, same almost everything because Brisbane is simply a 65nm shrink of Windsor. So performance wise it's still apples to apples - higher rating really does mean faster, at least in this case anyway.
As far as I can tell there isn't even a Brisbane 4600+, but for a drop in "200" mhz, you'll be consuming a less power to run the Brisbane 4400+. Less power means less heat, which means longer life at those clocked speeds. That's why I linked to an EE version of the 4600+. Same 65 watt thermal design power.
Not a good idea to do a price/performance comparison when prices and lineup are about to change.
Intel will be releasing a few new CPUs and cutting prices on April 22. The E6320 and E6420 for example, identical to their 6x00 counterparts except with 4mb of L2 cache. They'll go for $163 and $183 respectively.
Even now the prices Techreport lists are outdated! The Athlon X2 4600+ dropped to $122 a week ago - faster and cheaper than the $170 4400+ techreport tested (which is actually more like $159).
Imagine you've released 3 groups of people into a room. Babies, 10 year olds, and professional basketball players. If you graph height vs how many people are that height, you'll see 3 humps. One about 2 feet, the second about 4 feet, and the third other 6 feet. But very few at 3 and 5 feet.
That's what the graph in Jurassic Park was supposed to look like, because the dinos were released in batches. Instead they saw one big hump. So to continue the analogy, where did so many 3 foot and 5 foot high people come from? That's how Ian knew they must be breeding.
Re:Let's run this through bullshit filter
on
ReactOS 0.3.1 Released
·
· Score: 2, Insightful
I've written a boot sector and a hello world kernel, so I can begin to appreciate how much work it is to get an OS to the point where you can port Wine to it. I'm shocked at the way you make it sound trivial.
ReactOS already works with many Windows drivers, like nVidia's graphics drivers, and runs about as many apps as Wine, including Firefox. You can't seriously call that "not do[ing] anything real in a VM".
Either you don't know what you're talking about, you're a troll, you jumped to conclusions before getting any info about ReactOS, or all of the above.
That's an exaggeration. Almost everyone here has a rough idea of how far a meter is, even if they approximate it as about a yard. And we're familiar with liters thanks to 1 & 2 liter bottles of soda pop - not everything is in gallons.
1. Must be able to disable garbage collection and manage allocation explicitly You can explicitly disable the garbage collector with a function call. The C standard library is exposed, and malloc/free work fine in D. I think there's even an unofficial no garbage collector version of the D standard library you could use.
2. Must be able to allocate classes on the stack Just declare the class as a struct. You can still put public/private/etc member functions in it (like a class) but it will go on the stack.
3. Must minimize use of exceptions in the standard library (in other words, exceptions must only be used for exceptional cases) Yeah... there is at least one alternative standard library, you don't have to use phobos.
* built-in dynamic and associative arrays, array slicing
Not exactly a recommendation that the core language apparently is so weak that these can't be put into libraries. Show me a C implementation and I'm show you a D inplementation - the syntax is almost identical sans preprocessor. It certainly wasn't done that way for any core language weakness.
* versioning (no preprocessor madness)
I'm guessing he meant variants here, the preprocessor is often used for variants, rarely for versioning. Nope, no variants. There's actually a version keyword, for "versioning" (conditional compilation).
I agree that people should respect laws and contracts better than that, and I see how not doing so hurts all the honest ones, but what are those embargoes good for, anyway?
Is it just nVidia's PR department trying to coordinate press coverage for maximum effect? What's in it for the reporters? What does it accomplish?
Same here. Maybe it's the stable branch that's messed up.
Gentoo seems to have been steadily improving in a way that I'm satisfied with, and what few problems I've encountered have been easily resolved by a simple forum search. I don't understand what everybody's complaining about.
but what I'd like to see is a dual-core-optimized dialect of QBasic that will handle obscenely large arrays without kvetching.
FreeBASIC. http://www.freebasic.net/
It's no more optimized for dual-core than C is, but it runs as fast as the equivalent C code compiled with -O0 (it doesn't optimize yet). Compiles to asm like C does (no bytecode, no VM) and usually beats other BASICs in benchmarks. It handles arrays as large as C can. And of all the modern BASICs it's the closest to QBasic, able to run many nontrivial (including graphical) QBasic programs unmodified.
but what I'd like to see is a dual-core-optimized dialect of QBasic that will handle obscenely large arrays without kvetching.
FreeBASIC. http://www.freebasic.net/
It's no more optimized for dual-core than C is, but it runs as fast as the equivalent C code compiled with -O0 (it doesn't optimize yet). Compiles to asm like C does (no bytecode, no VM) and usually beats other BASICs in benchmarks. It handles arrays as large as C can. And of all the modern BASICs it's the closest to QBasic, able to run many nontrivial (including graphical) QBasic programs unmodified.
Here's an IDE for it if you're interested: http://fbide.freebasic.net/
They're the borg of PC gaming, assimilating uniqueness into uniformity. After they bought Westwood, C&C became a modern warfare themed WarCraft. Yet another WarCraft clone with builder units and war factories you have to scroll to and click on to use (classic C&C had a centralized build queue with an always on-screen remote control).
I imagine FPS gamers appreciate variety as much as RTS gamers do. I sure don't want too many games pumped through the same risk-averse cookie cutter.
If you're imagining a grey blob, don't. Remember conservation of mass - it won't get bigger/heavier than what it eats. Instead image grey mold growing on all the plants outside. Spreading more like a disease than a blob.
Even if it could convert biomatter to nanobots with the fantastically unlikely efficiency needed to build up an actual sea or even just a blob of them, I sure wouldn't be so stupid as to program them to clump together into an easy target if it were me.
A sea/blob won't happen by accident either, or else some strain of mold or bacteria would have done it by now.
Unless you mean to sterilize an entire area as a last resort, a mirror would be useless. It won't be a big localized thing you can just shoot at.
glibc is *L*GPL, but that's different. It requires modifications to glibc itself to be published, but allows the program using glibc to be closed source.
As I understand it (I'm not a lawyer), the GPL dictates the terms/conditions by which you may COPY the work. Meaning: if you publish your modified kernel (as a binary or whatever) the GPL kicks in and requires you to publish source code too. If your modifications stay internal, private, on-site (i.e. no COPYING occurs) you're at no obligation whatsoever.
I don't think you're exaggerating. The Earth could be a paradise and the rest of the universe much worse, and it wouldn't matter. That's what the parable was supposed to illustrate.
You are comparing the safety of the Earth to the safety of the moon, when you should be comparing the safety of the Earth with the safety of being on both. The odds of something killing everybody on both the Earth and the moon MUST be lower than the odd of something killing everybody on just the Earth.
So you're telling me if you had two baskets one crappy and one good, you wouldn't even put one egg in the lousy basket, you'd put ALL of your eggs in the nicer one?
Unless it is big enough to literally fracture the earth itself, there are certainly going to be lots of room on the earth that are still a lot nicer than the moon.
True. And if you drop the nice basket and all the eggs break, at least the basket itself will still be nicer than the lousy one.
Slashdot Mirror
Not a good idea to do a price/performance comparison when prices and lineup are about to change.
2 duo-e6420.html
Intel will be releasing a few new CPUs and cutting prices on April 22. The E6320 and E6420 for example, identical to their 6x00 counterparts except with 4mb of L2 cache. They'll go for $163 and $183 respectively.
Benchmarks for next month's processors with price list:
http://www.xbitlabs.com/articles/cpu/display/core
A 20-30% price cut is expected from AMD on April 9.
Even now the prices Techreport lists are outdated! The Athlon X2 4600+ dropped to $122 a week ago - faster and cheaper than the $170 4400+ techreport tested (which is actually more like $159).
I'm not a biologist, but I can explain it.
Imagine you've released 3 groups of people into a room. Babies, 10 year olds, and professional basketball players. If you graph height vs how many people are that height, you'll see 3 humps. One about 2 feet, the second about 4 feet, and the third other 6 feet. But very few at 3 and 5 feet.
That's what the graph in Jurassic Park was supposed to look like, because the dinos were released in batches. Instead they saw one big hump. So to continue the analogy, where did so many 3 foot and 5 foot high people come from? That's how Ian knew they must be breeding.
I've written a boot sector and a hello world kernel, so I can begin to appreciate how much work it is to get an OS to the point where you can port Wine to it. I'm shocked at the way you make it sound trivial.
ReactOS already works with many Windows drivers, like nVidia's graphics drivers, and runs about as many apps as Wine, including Firefox. You can't seriously call that "not do[ing] anything real in a VM".
Either you don't know what you're talking about, you're a troll, you jumped to conclusions before getting any info about ReactOS, or all of the above.
Those machines are probably using different types of ram...
There's always BurnAtOnce: http://www.burnatonce.com/
Suppose a small weather system had an airliner fly through one of its clouds. Probably as much of an effect as that.
That's an exaggeration. Almost everyone here has a rough idea of how far a meter is, even if they approximate it as about a yard. And we're familiar with liters thanks to 1 & 2 liter bottles of soda pop - not everything is in gallons.
Not exactly a recommendation that the core language apparently is so weak that these can't be put into libraries. Show me a C implementation and I'm show you a D inplementation - the syntax is almost identical sans preprocessor. It certainly wasn't done that way for any core language weakness.
* versioning (no preprocessor madness)
I'm guessing he meant variants here, the preprocessor is often used for variants, rarely for versioning. Nope, no variants. There's actually a version keyword, for "versioning" (conditional compilation).
If you use a dchar when you foreach over a char array it will parse UTF8 for you. Most of the string functions support unicode.
But you do get the absolute value if you square something, then take the square root. I think that's what he was confusing it with.
I agree that people should respect laws and contracts better than that, and I see how not doing so hurts all the honest ones, but what are those embargoes good for, anyway?
Is it just nVidia's PR department trying to coordinate press coverage for maximum effect? What's in it for the reporters? What does it accomplish?
That version seems to have come out of beta 3 days ago:7 8188. 0-9626.html
http://www.nvnews.net/vbulletin/showthread.php?t=
http://www.nvidia.com/object/linux_display_ia32_1
Why are you ragging on nVidia's drivers so loudly and repetitively when you know they work fine for most people?
BTW: your history page is weird. All 2s. You always get modded up, but always only once. You must have a secret admirer or a second account.
It's perfectly stable here - no crashes ever. Driver version 9625, Xorg 7.1, kernel 2.6.18, Gentoo, GeForce FX 5700.
f =14
Some nVidia Linux driver devs hang out here, try searching and asking about your problem:
http://www.nvnews.net/vbulletin/forumdisplay.php?
Same here. Maybe it's the stable branch that's messed up.
Gentoo seems to have been steadily improving in a way that I'm satisfied with, and what few problems I've encountered have been easily resolved by a simple forum search. I don't understand what everybody's complaining about.
Ooops, with
's this time:
but what I'd like to see is a dual-core-optimized dialect of QBasic that will handle obscenely large arrays without kvetching.
FreeBASIC. http://www.freebasic.net/
It's no more optimized for dual-core than C is, but it runs as fast as the equivalent C code compiled with -O0 (it doesn't optimize yet). Compiles to asm like C does (no bytecode, no VM) and usually beats other BASICs in benchmarks. It handles arrays as large as C can. And of all the modern BASICs it's the closest to QBasic, able to run many nontrivial (including graphical) QBasic programs unmodified.
Here's an IDE for it if you're interested: http://fbide.freebasic.net/
but what I'd like to see is a dual-core-optimized dialect of QBasic that will handle obscenely large arrays without kvetching.
FreeBASIC. http://www.freebasic.net/ It's no more optimized for dual-core than C is, but it runs as fast as the equivalent C code compiled with -O0 (it doesn't optimize yet). Compiles to asm like C does (no bytecode, no VM) and usually beats other BASICs in benchmarks. It handles arrays as large as C can. And of all the modern BASICs it's the closest to QBasic, able to run many nontrivial (including graphical) QBasic programs unmodified. Here's an IDE for it if you're interested: http://fbide.freebasic.net/
They're the borg of PC gaming, assimilating uniqueness into uniformity. After they bought Westwood, C&C became a modern warfare themed WarCraft. Yet another WarCraft clone with builder units and war factories you have to scroll to and click on to use (classic C&C had a centralized build queue with an always on-screen remote control).
I imagine FPS gamers appreciate variety as much as RTS gamers do. I sure don't want too many games pumped through the same risk-averse cookie cutter.
If you're imagining a grey blob, don't. Remember conservation of mass - it won't get bigger/heavier than what it eats. Instead image grey mold growing on all the plants outside. Spreading more like a disease than a blob.
Even if it could convert biomatter to nanobots with the fantastically unlikely efficiency needed to build up an actual sea or even just a blob of them, I sure wouldn't be so stupid as to program them to clump together into an easy target if it were me.
A sea/blob won't happen by accident either, or else some strain of mold or bacteria would have done it by now.
Unless you mean to sterilize an entire area as a last resort, a mirror would be useless. It won't be a big localized thing you can just shoot at.
The FSF says GCC's output doesn't have to be GPL:t
http://www.gnu.org/licenses/gpl-faq.html#GPLOutpu
glibc is *L*GPL, but that's different. It requires modifications to glibc itself to be published, but allows the program using glibc to be closed source.
(I'm not a lawyer, this is not legal advice)
The GPL doesn't do that.
As I understand it (I'm not a lawyer), the GPL dictates the terms/conditions by which you may COPY the work. Meaning: if you publish your modified kernel (as a binary or whatever) the GPL kicks in and requires you to publish source code too. If your modifications stay internal, private, on-site (i.e. no COPYING occurs) you're at no obligation whatsoever.
I don't think you're exaggerating. The Earth could be a paradise and the rest of the universe much worse, and it wouldn't matter. That's what the parable was supposed to illustrate.
You are comparing the safety of the Earth to the safety of the moon, when you should be comparing the safety of the Earth with the safety of being on both. The odds of something killing everybody on both the Earth and the moon MUST be lower than the odd of something killing everybody on just the Earth.
So you're telling me if you had two baskets one crappy and one good, you wouldn't even put one egg in the lousy basket, you'd put ALL of your eggs in the nicer one?
Unless it is big enough to literally fracture the earth itself, there are certainly going to be lots of room on the earth that are still a lot nicer than the moon.
True. And if you drop the nice basket and all the eggs break, at least the basket itself will still be nicer than the lousy one.