You mean "Free" software; "open source" defines a set which includes code you can put in your closed source project without "stealing" it; and yes, anyone should be able to do that.
If you disagree, you have your own special term to play with. That's why it's the FSF, not the OSF.
"Banning drugs serverely reduced the pressure they put on health services."
It did? Kindly cite figures and sources, any why it doesn't apply to tobacco and alcohol. Is it ok being a potentially harmful drug so long as you're insanely popular?
A better trick is to compile PHP using the FastCGI SAPI and Apache 2 with the perfectly fine mod_fastcgi. Lets you spread PHP across machines, lets you jail/chroot PHP seperate from Apache, lets you run fewer copies of PHP (which also reduces database connections), and lets you change webserver or language with minimal impact on the other.
And yes, mmcache and friends work fine in FastCGI mode.
Note that, while you can enable InnoDB to get a few features unsupported by MySQL's default storage engine (MyISAM), MySQL doesn't consider it an error for the table type you requested not to be supported. The really funny bit? MySQL doesn't consider it an error for you to attempt a transaction on a table type that doesn't support it either.
It's not even warning material, it just silently "OK"'s the transaction. The only time you get a warning is if you try to ROLLBACK and it helpfully mentions that it can't; your unwanted changes are commited.
Pretty well sums up how seriously MySQL takes data integrity.
Get two moderately priced cards, SLI them together and get much better performance than a single high end card for around the same price. Plenty of people pay that for a mere 10% performance difference, what makes you think they won't pay it for 70%+?
Not all geeks are poor, and not all poor geeks are beyond saving up and spending a large amount of their income on what interests them.
I read somewhere that the typical bit error rate for normal non-ECC memory is one flip every 3 months or so. Sounds reasonable given the stability of my non-ECC systems.
Certainly 90 minutes is a joke; an overnight memtest86 will easily show decent quality memory's a lot more stable than that.
Are there any proper Object-Relational database libraries for PHP yet? PEAR:DB, ADODB etc are all well and good, but they do little more than wrap the various PHP *sql*() functions and abstract away some minor database differences with various levels of success; I've not seen anything which I can point to a database, give it some hints on relationships, and have it generate the majority of my database interface code for me.
I switched to Ruby for much the same reason, except my previous language was PHP. Your theory works well for it too; it wasn't special as a language, it just happened to do what people wanted well enough to get popular, at a time when the alternatives weren't hard to beat for the average user.
I get paid for writing both, and increasingly I'm finding Ruby being my primary language, even for web development; this coming from someone who 18 months ago was a raging PHPhile, defending it from people like me;)
What features does PHP have which make it especially suited to form and database interfaces? Many languages have easy to use CGI/FCGI/Server API's; many have HTML-embedded versions and high quality template libraries; many have database libraries which easily rival and surpass those of PHP, and many have fancy dynamic form generation and processing libraries.
PHP's far from best-of-class in any of these respects in my experience; only pervasiveness is in it's favour, and running my own servers, that isn't much of a conern to me.
Give me an example of how easy it is to interface a form with a database, complete with validation and listing using PHP in ways other languages can't match. In fact, show *anything* which you can do more cleanly in PHP than any other language, and you'll be on your way to having a decent response to the grandparent poster.. and me;)
Probably because the Doom 3 engine may be more suited to slower paced single player gameplay, and Quake's traditionally been quite a fast paced multiplayer game. Multiplayer at 25FPS/800*600 doesn't sound so great to me.
I'd imagine the pin lengths are quite important at high speeds, and routing water around all those pins in a tiny little package, under a hsf...
This line of thinking's got me wondering about cooling both sides of a processor... maybe if you made one with the pins at one corner, like a little slot, pack heatsinks to both sides of it; with the right mounting gear and processor package you could effectively double your cooling area. Maybe one way of dealing with the heat of dual/quad core chips and lower surface areas as they get denser:)
"It would not take much to convince the enthusiasts that a new pin insert was needed whenever a cpu was upgraded to insure maximum performance"
Well, it would take some fairly repeatable benchmarks, at least. Maybe you could sell "higher quality" ones with gold plated pins and a heatspreader or something. Of course, you could always package them with the CPU...
"In some respects computer enthusiasts are as bad as audiophiles."
I resent that; I haven't spent more than a couple of quid on IDE and VGA cables!;)
Except IBM's are 80G/platter drives with up to 5 platters; Seagate are at 133G/platter, making their 400G version a 3 platter drive. That makes for quieter, faster and cooler \o/
One bit. Oh, you weren't talking ASCII?:-) Larry now uses "Perl" to
signify the language proper and "perl" the implementation of it, i.e.
the current interpreter. Hence Tom's quip that "Nothing but perl can
parse Perl." You may or may not choose to follow this usage. For
example, parallelism means "awk and perl" and "Python and Perl" look
OK, while "awk and Perl" and "Python and perl" do not. But never write
"PERL", because perl isn't really an acronym, apocryphal folklore and
post-facto expansions notwithstanding.
Bluetooth's range extends up to 100m; certainly enough to cover a few rooms away. Not all devices are designed for such feats, but my class 1 dongle and iPAQ seem to have similar range to my WiFi (signal strength drops about the same).
2; you only get 4 by a bit of extra hardware to virtualize one as two. Hyperthreading is just exploiting the already superscalar architecture a little more.
HTT has a transistor count overhead of ~5%; dual core is over 100%:)
Um, if you'd actually read my comment, you'd see I was referring to Apple creating their own closed lossless format because they want control over it as sounding "nasty", with them doing it to work around limitations in the iPod as sounding "less nasty". Comments about the quality/performance of the codec are purely based around it's compression ratio, speed and support.
As for converting to ALAC, the poor support kinda makes that difficult; it involves decoding to WAV, encoding in iTunes and retagging manually. I'd really rather just use a player which actually supports the formats I use.
Slashdot Mirror
Then you're fired for making a serious application full of magic numbers. DRY.
Generally, when you're writing an ellipsis in HTML you want to use … (—). — (…) is preferable to -- too.
Neither work with SlashCode of course. Quality software, that.
You mean "Free" software; "open source" defines a set which includes code you can put in your closed source project without "stealing" it; and yes, anyone should be able to do that.
If you disagree, you have your own special term to play with. That's why it's the FSF, not the OSF.
It did? Kindly cite figures and sources, any why it doesn't apply to tobacco and alcohol. Is it ok being a potentially harmful drug so long as you're insanely popular?
A better trick is to compile PHP using the FastCGI SAPI and Apache 2 with the perfectly fine mod_fastcgi. Lets you spread PHP across machines, lets you jail/chroot PHP seperate from Apache, lets you run fewer copies of PHP (which also reduces database connections), and lets you change webserver or language with minimal impact on the other.
And yes, mmcache and friends work fine in FastCGI mode.
Note that, while you can enable InnoDB to get a few features unsupported by MySQL's default storage engine (MyISAM), MySQL doesn't consider it an error for the table type you requested not to be supported. The really funny bit? MySQL doesn't consider it an error for you to attempt a transaction on a table type that doesn't support it either.
It's not even warning material, it just silently "OK"'s the transaction. The only time you get a warning is if you try to ROLLBACK and it helpfully mentions that it can't; your unwanted changes are commited.
Pretty well sums up how seriously MySQL takes data integrity.
Get two moderately priced cards, SLI them together and get much better performance than a single high end card for around the same price. Plenty of people pay that for a mere 10% performance difference, what makes you think they won't pay it for 70%+?
Not all geeks are poor, and not all poor geeks are beyond saving up and spending a large amount of their income on what interests them.
Sounds more like a graphics driver problem than anything CPU related. Pathetic, yes, but not (just) because of the CPU.
$0.567 for a lossless copy of the longest track -- about a third of the price of a 128kbps DRM crippled AAC from iTunes UK.
I read somewhere that the typical bit error rate for normal non-ECC memory is one flip every 3 months or so. Sounds reasonable given the stability of my non-ECC systems.
Certainly 90 minutes is a joke; an overnight memtest86 will easily show decent quality memory's a lot more stable than that.
Are there any proper Object-Relational database libraries for PHP yet? PEAR:DB, ADODB etc are all well and good, but they do little more than wrap the various PHP *sql*() functions and abstract away some minor database differences with various levels of success; I've not seen anything which I can point to a database, give it some hints on relationships, and have it generate the majority of my database interface code for me.
I switched to Ruby for much the same reason, except my previous language was PHP. Your theory works well for it too; it wasn't special as a language, it just happened to do what people wanted well enough to get popular, at a time when the alternatives weren't hard to beat for the average user.
;)
I get paid for writing both, and increasingly I'm finding Ruby being my primary language, even for web development; this coming from someone who 18 months ago was a raging PHPhile, defending it from people like me
What features does PHP have which make it especially suited to form and database interfaces? Many languages have easy to use CGI/FCGI/Server API's; many have HTML-embedded versions and high quality template libraries; many have database libraries which easily rival and surpass those of PHP, and many have fancy dynamic form generation and processing libraries.
;)
PHP's far from best-of-class in any of these respects in my experience; only pervasiveness is in it's favour, and running my own servers, that isn't much of a conern to me.
Give me an example of how easy it is to interface a form with a database, complete with validation and listing using PHP in ways other languages can't match. In fact, show *anything* which you can do more cleanly in PHP than any other language, and you'll be on your way to having a decent response to the grandparent poster.. and me
The greatgreatgrandparent poster presumably isn't planning an upgrade.. personally I'm eyeing up these new S939 AMD64's and PCI Express GFX cards ;)
Probably because the Doom 3 engine may be more suited to slower paced single player gameplay, and Quake's traditionally been quite a fast paced multiplayer game. Multiplayer at 25FPS/800*600 doesn't sound so great to me.
I prefer lftp over ncftp. It's job control, protocol support and general usability seem much better.
centericq's another good one; nice multi-protocol console IM client.
I'd imagine the pin lengths are quite important at high speeds, and routing water around all those pins in a tiny little package, under a hsf...
:)
;)
This line of thinking's got me wondering about cooling both sides of a processor... maybe if you made one with the pins at one corner, like a little slot, pack heatsinks to both sides of it; with the right mounting gear and processor package you could effectively double your cooling area. Maybe one way of dealing with the heat of dual/quad core chips and lower surface areas as they get denser
Patent!
Well, it would take some fairly repeatable benchmarks, at least. Maybe you could sell "higher quality" ones with gold plated pins and a heatspreader or something. Of course, you could always package them with the CPU...
I resent that; I haven't spent more than a couple of quid on IDE and VGA cables!
Isn't TCQ supposed to make write cache safe?
25-60% failure rate? Sounds like you need to find a better supplier for your disks :/
Except IBM's are 80G/platter drives with up to 5 platters; Seagate are at 133G/platter, making their 400G version a 3 platter drive. That makes for quieter, faster and cooler \o/
Bluetooth's range extends up to 100m; certainly enough to cover a few rooms away. Not all devices are designed for such feats, but my class 1 dongle and iPAQ seem to have similar range to my WiFi (signal strength drops about the same).
2; you only get 4 by a bit of extra hardware to virtualize one as two. Hyperthreading is just exploiting the already superscalar architecture a little more.
:)
HTT has a transistor count overhead of ~5%; dual core is over 100%
Um, if you'd actually read my comment, you'd see I was referring to Apple creating their own closed lossless format because they want control over it as sounding "nasty", with them doing it to work around limitations in the iPod as sounding "less nasty". Comments about the quality/performance of the codec are purely based around it's compression ratio, speed and support.
As for converting to ALAC, the poor support kinda makes that difficult; it involves decoding to WAV, encoding in iTunes and retagging manually. I'd really rather just use a player which actually supports the formats I use.