For you and I, JimBob and JoeBlow, a good fast 32-bit system will kick much 64-bit arse.
This isn't valid. x86-64 systems can run 32-bit apps at full speed, so they'd be kicking their own arse.
Also note that x86-64 corrects some of the weaknesses of the x86 architecture, so x86-64 apps are automatically faster. Counter-strike was 30% faster, clock-for-clock.
I've used an Aver external box, and found that there were problems VGA image quality. The pass-through added some funny interference patterns to the standard display.
I returned it. I currently use an Aver bt848-based card under Linux.
You're limiting the definition of "unlimited". If a plan is described as simply "unlimited", people expect the only limits to be physical ones, like hardware limitations or the limits of human anatomy. After all, you can't surf the web 24/8.
So while the instantanous bandwidth is limited by hardware capacity, the download capacity should only be limited by the instantaneous bandwidth.
Another possible reason for NVidia keeping their source closed would be if there was something they'd be ashamed of in there. Remember the recent NVidia Futuremark fiasco? What other dirty secrets might they have? (He queried, while using a GForce3 card.)
Download is actually the transfer of data from another computer to the one you are using.
"Network"s aren't required-- you can do it with modems and zmodem. It's not "your machine" because you may own both computers, or perhaps neither, or you may be using someone else's machine to upload a file to yours.
Actually, SOCAN is involved with many Canadian songwriters. Not that Avril or Celine write all of their own songs.
But many songwriters register their copyrights with SOCAN, including Gordon Lightfoot and Avril Lavigne. SOCAN takes care of collecting royalties from radio stations and distributing them to the songwriters in question. And they have agreements with their counterparts in other countries, so membership with SOCAN covers your music around the world.
So SOCAN's not entirely evil, not entirely useless. But many songwriters aren't technologically astute or aware of this issue. That's why no one's managed to stop its RIAA-like behaviour.
I've made my own efforts to raise awareness among songwriters, but it's hard to know whether songwriters have enough power over SOCAN to make them stop.
FYI: JPEG are bad for screenshots. Use PNG or GIF.:-)
It depends what the screenshot is, but most apps have lots of areas of flat colour, which makes them compress well with PNG & GIF. They also have lots of crisp edges (fonts, widget lines, etc.), which look really ugly with JPEG compression.
What Goo.cc did wrong was using the wrong palette in the GIF and using dithering. Proper palette selection and no dithering would improve these screenshots immensely.
While it's possible to change the kernel on the fly, it's very hard to get right. Using the built-in modules functionality is the only easy way to achieve that.
And why would you want to recompile build tools, build dependencies and such every time you start up, when you could do it once and be done with it?
It's nonsensical to install it from scratch on system startup. The alternative (copy a file from a read-only NTFS then remount) is faster and easier.
a. Knoppix doesn't use RPM. b. Applying the kernel changes needs to happen before the CD image is created, but copying the file needs to happen during system startup.
It's true that this would wreak havok with existing DNS servers. But others have been twisting DNS to their own purposes before this, and it's caused no harm.
DNS spam blacklists don't interfere with DNS, because they don't connect to the global DNS system. Hands up if you want to run a bittorrent DNS root server. Anyone? No one?
You are aware that 2.6 is the same branch as 2.5, right? That it was called 2.5 until Linus started releasing 2.6-test versions? And no, I'm not using 2.5 or 2.6 at the moment.
It's true that JavaScript and Java have little in common. The name was a marketing ploy. (It was originally called LiveScript.) But JavaScript does have types-- in fact, it's an oo language.
Both. In the early days of 2.5, it seemed more common to port from 2.4 to 2.5, but lately the trend has been in the opposite direction. Just my perceptions, though.
I'm not religious either, but given the choice I'd prefer a text format to be human readable. I don't think the costs are significant.
When it's readable, it's reausable. You can specify your own Slashdot stylesheet. You can parse the xhtml and reformat it into something else.
Of course, given valid XML, you can run it through some automatic prettifier. But human-chosen whitespace will always make more sense than autogenerated whitespace. And as someone else noted, the comments wouldn't necessarily be valid XML.
So instead of view|source, you're now doing file|save, then tidy -i, then viewing that. Which is fine if you don't have to do it repeatedly.
Slashdot Mirror
For you and I, JimBob and JoeBlow, a good fast 32-bit system will kick much 64-bit arse.
This isn't valid. x86-64 systems can run 32-bit apps at full speed, so they'd be kicking their own arse.
Also note that x86-64 corrects some of the weaknesses of the x86 architecture, so x86-64 apps are automatically faster. Counter-strike was 30% faster, clock-for-clock.
I've used an Aver external box, and found that there were problems VGA image quality. The pass-through added some funny interference patterns to the standard display.
I returned it. I currently use an Aver bt848-based card under Linux.
Get black people to stop using that word, then we'll talk. The notion that only certain people can use that word is racist too.
No, it always works. 10 frames per second means .1 seconds per frame. No exceptions. Ever.
If units are the inverse of each other, measurements on those units are the inverse of each other.
Dear Glonoinha,
You can convert between units per second and seconds per unit using this special formula:
1 / unitspersecond = secondsperunit
I hope this helps.
What about the HAEBUS anti-spam haikus?
8086? Really? I remember those existed-- the 8088 was was a stripped down version, but it was the standard in PCs until the 80286 came out.
For the QBasic case, the argument would be made on the basis of possible future problems.
Do they have the source? (QuickBasic could build stand-alone apps)
Can they find someone who can fix a sophisticated QBasic app if they find a bug?
Do they want to add new features?
Are there modern apps with the features they want?
Do they want to integrate it with more modern software?
Yes, QBasic is dead. And people who continue to use it may be running silly risks
Bought it for my daughter for Christmas. . .
I hope she doesn't read Slashdot!
I pity the fool who's read the whole thing.
You're limiting the definition of "unlimited". If a plan is described as simply "unlimited", people expect the only limits to be physical ones, like hardware limitations or the limits of human anatomy. After all, you can't surf the web 24/8.
So while the instantanous bandwidth is limited by hardware capacity, the download capacity should only be limited by the instantaneous bandwidth.
It's trickier than that. Some libraries contain inline functions. In fact, some libraries use hardly any "out-of-line" functions.
So your compiled binary can include a bunch of code copyrighted by someone else. Isn't that a derived work?
Another possible reason for NVidia keeping their source closed would be if there was something they'd be ashamed of in there. Remember the recent NVidia Futuremark fiasco? What other dirty secrets might they have? (He queried, while using a GForce3 card.)
Download is actually the transfer of data from another computer to the one you are using.
"Network"s aren't required-- you can do it with modems and zmodem. It's not "your machine" because you may own both computers, or perhaps neither, or you may be using someone else's machine to upload a file to yours.
Actually, SOCAN is involved with many Canadian songwriters. Not that Avril or Celine write all of their own songs.
But many songwriters register their copyrights with SOCAN, including Gordon Lightfoot and Avril Lavigne. SOCAN takes care of collecting royalties from radio stations and distributing them to the songwriters in question. And they have agreements with their counterparts in other countries, so membership with SOCAN covers your music around the world.
So SOCAN's not entirely evil, not entirely useless. But many songwriters aren't technologically astute or aware of this issue. That's why no one's managed to stop its RIAA-like behaviour.
I've made my own efforts to raise awareness among songwriters, but it's hard to know whether songwriters have enough power over SOCAN to make them stop.
FYI: JPEG are bad for screenshots. Use PNG or GIF. :-)
It depends what the screenshot is, but most apps have lots of areas of flat colour, which makes them compress well with PNG & GIF. They also have lots of crisp edges (fonts, widget lines, etc.), which look really ugly with JPEG compression.
What Goo.cc did wrong was using the wrong palette in the GIF and using dithering. Proper palette selection and no dithering would improve these screenshots immensely.
While it's possible to change the kernel on the fly, it's very hard to get right. Using the built-in modules functionality is the only easy way to achieve that.
And why would you want to recompile build tools, build dependencies and such every time you start up, when you could do it once and be done with it?
It's nonsensical to install it from scratch on system startup. The alternative (copy a file from a read-only NTFS then remount) is faster and easier.
a. Knoppix doesn't use RPM.
b. Applying the kernel changes needs to happen before the CD image is created, but copying the file needs to happen during system startup.
It's true that this would wreak havok with existing DNS servers. But others have been twisting DNS to their own purposes before this, and it's caused no harm.
DNS spam blacklists don't interfere with DNS, because they don't connect to the global DNS system. Hands up if you want to run a bittorrent DNS root server. Anyone? No one?
You are aware that 2.6 is the same branch as 2.5, right? That it was called 2.5 until Linus started releasing 2.6-test versions? And no, I'm not using 2.5 or 2.6 at the moment.
Hey, buffer overflows mean that the functionality provided is limited only by your imagination!
It's true that JavaScript and Java have little in common. The name was a marketing ploy. (It was originally called LiveScript.) But JavaScript does have types-- in fact, it's an oo language.
It's just weakly typed.
Both. In the early days of 2.5, it seemed more common to port from 2.4 to 2.5, but lately the trend has been in the opposite direction. Just my perceptions, though.
Agreed that "mess" is purely aesthetic.
I'm not religious either, but given the choice I'd prefer a text format to be human readable. I don't think the costs are significant.
When it's readable, it's reausable. You can specify your own Slashdot stylesheet. You can parse the xhtml and reformat it into something else.
Of course, given valid XML, you can run it through some automatic prettifier. But human-chosen whitespace will always make more sense than autogenerated whitespace. And as someone else noted, the comments wouldn't necessarily be valid XML.
So instead of view|source, you're now doing file|save, then tidy -i, then viewing that. Which is fine if you don't have to do it repeatedly.
You mean when Slashdot links to a site, they should first code up an XHTML+CSS version, then hack into the web server and upload it?