They should have started with the smallest possible dose and gradually increased it in successive trials.
But "smallest possible" is kind of arbitrary. According to Wikipedia: "It has been reported that the initial dose was one five-hundredth of that which the animal studies indicated was a maximum safe dose." That sounds pretty small, it's just that this particular drug had a differant threshold in humans. (Or, of course, the dosage in the trial get screwed up.)
And in the early stages they should also have administered the drug to only one subject or at least staggered the subjects many hours apart.
This is where they seem absolutely responsible for what happened.
This is kind of a silly attitude. The very fact that a human test is necessary indicates the possibility, however slighty, that a dangerous response is possible. From what I can tell from reading online, there was plenty of animal testing done, including exposing other primates to the substance, but it responded uniquely to human biology. (One possibility, apparantly, is that because the production of the drug involved human proteins, the safe dosage was much lower in humans. I have no idea if that actually makes any sense ^_^)
The negligence here seems to be the way this particular trial was run by Paraxel. Who didn't, by the way, design the drug. They're a testing company, not a pharmaceutical.
"The number of tones has a lot to do with the complexity of a work, since the most complex work will necessarily be that which doesn't use any tone until it has used the other eleven."
This is manifestly, mathematicly false on so many levels that it's not surprising you got modded troll. ^_^
As far as Tool's music, what you're perhaps missing is that all the complexity lies in the rythmic space, not the melodic or harmonic.
I'm kind of glad that taking four years of theory and composition classes didn't cripple my ability to enjoy rock music. And I'm not sure why you're so hung up on counting the number of tones used... hardly a measure of a piece of musics complexity or worth.
From reading about the project, one of the advantages they have is knowing the hardware specs in advance. Since every labtop will have exactly the same configuration, it'll make it much easier to build an operating system that is pretty solid.
And as it happens, it went down hill shortly after the takeover. (That whole, if you don't log in for a month you lose all settings and messages was pretty crap. Especially when you go on vacation w/o internet access for a month. ^_^ I moved first to yahoo and then to gmail.)
That might have been true at the time of the tests release. But since browsers can now target just those specific bugs revealed in ACID2, it's not such a good indication of what will happen "in the wild."
There's jabberzilla, which (of course) supported the jabber protocol. But it hasn't had any activity in a while.
I tried my hand at writing one myself, and got it to the point where I could talk to people and add contacts w/o any problems. It didn't do anything else and was super ugly, though. ^_^
Agreed, digg is useless if you're looking for commentary on the article. As bad as I used to find slashdot, digg made me realise how well the moderation system really works.
Even the guy who created it admits it was created too quickly. ^_^
JS, unlike Python, was a rushed little hack for Netscape 2 that was then frozen prematurely during the browser wars, and evolved significantly only once by ECMA. So its early flaws were never fixed, and worse, no virtuous cycle of fine-grained community feedback in the form of standard library code construction, and revision of the foundational parts of the language to better support the standard library and its common use-cases, ever occurred.
This is changing, finally. Great toolkits such as MochiKit and Dojo have been developed and disseminated (with docs and tests, even). I should also mention OpenJSAN.org as a welcome development. We can finally see the outlines of a standard JS library system. Of course, this space is young and necessarily fragmented. I will blog some concrete thoughts soon on how browsers can expedite the evolution of a proper standard library.
But what about the core JS language? It's not going to go away, or turn into Python. It needs to evolve, and to co-evolve with libraries that become standard. How can this all happen in relatively short order, and on the web?
As noted here before, I am working in ECMA TG1 with colleagues from Mozilla, Adobe, and Microsoft. Adobe's interest lies not only in ActionScript, but also in SpiderMonkey, which has been embedded in Acrobat for years.
I don't think that's ever a direct problem. Javascript could certainly be a nicer language to work in, but it never prevents you from reaching your goal. It's not the scripting language that constrains you, but the underlying components.
However, it is actually possible to write your own components, even in C++, and distribute them along with the rest of your code. Obviously you lose some of the advantage of XUL at this point, but if it's just one small feature your missing you can code your own.
And of course as people start to use XULRunner, specific needs will drive further development. Things that Firefox doesn't need to do, such as query SQL databases, will have components written for them.
Slashdot Mirror
From what I remember, most of those platformers were licensed dreck. (Anyone ever played the Barbie game for NES? ^_^)
They should have started with the smallest possible dose and gradually increased it in successive trials.
But "smallest possible" is kind of arbitrary. According to Wikipedia: "It has been reported that the initial dose was one five-hundredth of that which the animal studies indicated was a maximum safe dose." That sounds pretty small, it's just that this particular drug had a differant threshold in humans. (Or, of course, the dosage in the trial get screwed up.)
And in the early stages they should also have administered the drug to only one subject or at least staggered the subjects many hours apart.
This is where they seem absolutely responsible for what happened.
This is kind of a silly attitude. The very fact that a human test is necessary indicates the possibility, however slighty, that a dangerous response is possible. From what I can tell from reading online, there was plenty of animal testing done, including exposing other primates to the substance, but it responded uniquely to human biology. (One possibility, apparantly, is that because the production of the drug involved human proteins, the safe dosage was much lower in humans. I have no idea if that actually makes any sense ^_^)
The negligence here seems to be the way this particular trial was run by Paraxel. Who didn't, by the way, design the drug. They're a testing company, not a pharmaceutical.
Apparantly they got companies to donate processor time for the rendering, so not quite yet. ^_^
They could have been replaced by human actors as well, many of whom can act better than those paid $20 million.
Now I can finally become a Super-Saiyan!
You missed the point: that some companies were requiring these of their employees.
Also interesting is this thread in the mozillazine forums.
You do realise that, if this works, it isn't really leaked memory?
It's not clear that these statistics have anything to do with pagehits. Another poster mentioned filling out a survey...
"The number of tones has a lot to do with the complexity of a work, since the most complex work will necessarily be that which doesn't use any tone until it has used the other eleven."
This is manifestly, mathematicly false on so many levels that it's not surprising you got modded troll. ^_^
As far as Tool's music, what you're perhaps missing is that all the complexity lies in the rythmic space, not the melodic or harmonic.
I'm kind of glad that taking four years of theory and composition classes didn't cripple my ability to enjoy rock music. And I'm not sure why you're so hung up on counting the number of tones used... hardly a measure of a piece of musics complexity or worth.
"doesn't use all twelve tones of the chromatic scale as has been encouraged since Schoenberg"
But on the other hand, I actually enjoy listening to Tool.
From reading about the project, one of the advantages they have is knowing the hardware specs in advance. Since every labtop will have exactly the same configuration, it'll make it much easier to build an operating system that is pretty solid.
Exept, no. The equipment to measure their transmissions is a little hard to come by. (You should price radio telescopes sometime. ^_^)
Yes, it's a proven fact: Unlike the rest of humanity, liberals can never be manipulated. (Go us! ^_^)
And as it happens, it went down hill shortly after the takeover. (That whole, if you don't log in for a month you lose all settings and messages was pretty crap. Especially when you go on vacation w/o internet access for a month. ^_^ I moved first to yahoo and then to gmail.)
Are you suggesting that they give money to everyone who uses the software? ^_^ (Because I wouldn't be too opposed to that.
I have a pretty large compilation of old NES ROMS on my computer. And I can tell you that almost all of them suck. Many of them really, really suck.
There are also plenty of good games mixed among them, but Sturgeon's law holds true for video games. Both "back in the day" and now.
I'm not sure what you're getting at; an XMLHttpRequest isn't a DOM event, which I think is what the word normally means in this context.
If Opera can't handle asynchronos XMLHttpRequests that is a pretty big issue, though.
That might have been true at the time of the tests release. But since browsers can now target just those specific bugs revealed in ACID2, it's not such a good indication of what will happen "in the wild."
There's jabberzilla, which (of course) supported the jabber protocol. But it hasn't had any activity in a while.
I tried my hand at writing one myself, and got it to the point where I could talk to people and add contacts w/o any problems. It didn't do anything else and was super ugly, though. ^_^
Agreed, digg is useless if you're looking for commentary on the article. As bad as I used to find slashdot, digg made me realise how well the moderation system really works.
I don't think that's ever a direct problem. Javascript could certainly be a nicer language to work in, but it never prevents you from reaching your goal. It's not the scripting language that constrains you, but the underlying components.
However, it is actually possible to write your own components, even in C++, and distribute them along with the rest of your code. Obviously you lose some of the advantage of XUL at this point, but if it's just one small feature your missing you can code your own.
And of course as people start to use XULRunner, specific needs will drive further development. Things that Firefox doesn't need to do, such as query SQL databases, will have components written for them.