Yes HIV's infective nature is troublesome. Still this research is evidence of serious scientific progress.
More at that, progress towards a direction I personally agree with. So I will be 100% positive about it. Obviously this isn't a de facto cure for cancer but it is the most promising thing being done in that sense. Give them a couple of years and probably they will have sterilized the viral carrier so effectively that it will be completely safe.
Because you don't write blogs in lisp and you don't setup HFT machines in Shockwave's lingo.
I don't really see this as an argument, I have used a great variety of languages over my professional career and at no time have I found myself getting into trouble because of the language I selected. A good programmer will take the time to evaluate the weaknesses of his tools and act upon that knowledge. We are talking about PHP. PHP doesn't have weaknesses because of magic quotes it has weaknesses because of the misuse of magic quotes.
Hopefully it doesn't make the various worldwide retirement systems go bankrupt (though some will anyway because citizens allow governments to erect Ponzi schemes).
Medical evolution without making politicians and money brokers look stupid is infeasible. So yes, that will happen. But look at the bright side. Maybe political and macro economic interests won't allow such a treatment to be legalized:-)
1. Correct. 2. Correct, though from the only tests I heard of in the past none damaged the patient in an unexpected way. 3. Yes but that will take time and I believe even if there is a 100% chance of that happening, your future will still look brighter with the treatment rather with small cell lung cancer.
I just hope that all those experimental results will also be approved. Even if the treatment is completely dependable, You know how those pharmaceuticals like to bitch..
Come on Raven, this isn't even an argument. The two settings you talk about had a reason to be there, they provided functionality. Sure it is common sense now that this type of functionality has way too many drawbacks and this is why it is being iterated out of the language. All I see being talked about in this whole thread is features of languages that when used by some half informed programmer can have a bad effect.
Dear everybody: Please, get over it. Every language will bite you in the ass if you are going to create a big enough program in it. Every C writer in history has at some point written a buffer overflow, every code monkey an SQL injection, every rails genius a mass assignment vulnerability and don't even get me started on MicrosoftLand...
The fact of the matter is this: "It's not the language it is the DEADBEEF in front of the keyboard."
Which is something that affects every single computation ever done, from meta programming to processor microcode to pen and paper multiplication. So, yes it is true but also irrelevant. As is the question of the AC that spawned this debate.
As is the story really (in my very honest opinion). I don't care where the language I program comes from as long as it behaves as I want it to. today languages are designed instead of being engineered. Ok, I'm pretty sure that when some mega corp or institute finds itself in dire need of creating a language, to solve all their computational problems, they will engineer one or design one depending on their needs. Compiler creation guidelines flow freely on the net and are available in books as well, Why wouldn't someone create a new language if he felt like it? And why wouldn't other people adopt it if they felt like it.
Whoever thinks that all technological progress should come out of universities is fooling himself, nothing bad is happening here.
Packet TTL will show just how much time the sending router gave the packet to be Delivered to its destination. The latency should be the time= output, since that describes the time it took for the packet to actually arrive and be acknowledged of the destination server.
No, really I have seen many chrome implementations (especially win XP & 7) where basic stuff like the location object is badly corrupt. It usually tracks down to malware or cracked software, but is easily fixed with a reinstall (that's remove -> install. not upgrade)
My idea exactly. Are they going to open up the code for this? But from where I'm sitting I can't see how this is different from a Terminal emulator running on you own host over https. I had setup one of those once, there are a number of terminal emus as js standalones. You just wire it up to a script that evals the input onto the linux https server and returns the output.
Why wouldn't the signal carry information over the 20khz mark? That fact that you cannot directly hear it doesn't make the information disappear. The fact is that to allow the hardware to correctly reproduce the intended soundwave you will need a lot more resolution than the one you can perceive. Now add to that the resolution you loose through processing (anti aliasing, to analog conversion) and you will end up needing a hell of a lot more resolution than the 44.1khz will give you. 48khz and you get a good approximation 96 on 24bit range is usually a good enough sample to do some good work. Now if you want to do some weird post processing like removing some difficult artifacts you could find higher sampling rates useful.
My opinion is that studio grade samples should be stored at the highest possible resolution while personal playback can very well be lower. Most audiophiles I know see no merit to files higher than 96khz/24bit and even a 48khz/24bit recording will reproduce a very similar track.
Now all this is relevant to the signal of the recording. If the hardware used couldn't go farther than 48khz then there is obviously no reason to oversample.
My point exactly. Storage is not a factor so when you have the choice in a studio setting why not keep the best resolution you can? Now for playback you obviously wouldn't want to log 2GB files for a 3min hiphop song, in that case you can just downsample to flac/48khz or even 256kbps mp3. Hell, most consumers are happy with the crappy 112/128kbps rips they get extracted from youtube videos.
Slashdot Mirror
All the kids will be running around with their stupid laser pointers hacking into WoW!
Why is this moderated Funny? Sad and insightful yes, but funny?!
I though it went:
I. build a mouse trap
II. sue everyone for having round corners
Especially if you are color blind!
Yes HIV's infective nature is troublesome. Still this research is evidence of
serious scientific progress.
More at that, progress towards a direction I personally agree with. So I will be
100% positive about it. Obviously this isn't a de facto cure for cancer but it
is the most promising thing being done in that sense. Give them a couple of
years and probably they will have sterilized the viral carrier so effectively that
it will be completely safe.
Because you don't write blogs in lisp and you don't setup HFT machines in Shockwave's lingo.
I don't really see this as an argument, I have used a great variety of languages over my
professional career and at no time have I found myself getting into trouble because of the
language I selected. A good programmer will take the time to evaluate the weaknesses of his
tools and act upon that knowledge. We are talking about PHP. PHP doesn't have weaknesses
because of magic quotes it has weaknesses because of the misuse of magic quotes.
Pharmaceutical company happy now?
Hopefully it doesn't make the various worldwide retirement systems go bankrupt (though some will anyway because citizens allow governments to erect Ponzi schemes).
Medical evolution without making politicians and money brokers look stupid is infeasible. So yes, that will happen. But look at the bright side. Maybe political and macro economic interests won't allow such a treatment to be legalized :-)
1. Correct.
2. Correct, though from the only tests I heard of in the past none damaged the patient in an unexpected way.
3. Yes but that will take time and I believe even if there is a 100% chance of that happening, your future will still look brighter with the treatment rather with small cell lung cancer.
I just hope that all those experimental results will also be approved. Even if the treatment is completely dependable, You know how those pharmaceuticals like to bitch..
Yes!
Note: In case of zombie breakout, call Jill Valentine.
Hilarious articles, the English is a bit off though.
Come on Raven, this isn't even an argument. The two settings you talk about had a reason to be there, they provided functionality. Sure it is common sense now that this type of functionality has way too many drawbacks and this is why it is being iterated out of the language. All I see being talked about in this whole thread is features of languages that when used by some half informed programmer can have a bad effect.
Dear everybody: Please, get over it. Every language will bite you in the ass if you are going to create a big enough program in it. Every C writer in history has at some point written a buffer overflow, every code monkey an SQL injection, every rails genius a mass assignment vulnerability and don't even get me started on MicrosoftLand...
The fact of the matter is this: "It's not the language it is the DEADBEEF in front of the keyboard."
Which is something that affects every single computation ever done, from meta programming to processor microcode to pen and paper multiplication.
So, yes it is true but also irrelevant.
As is the question of the AC that spawned this debate.
As is the story really (in my very honest opinion). I don't care where the language I program comes from as long as it behaves as I want it to. today languages are designed instead of being engineered. Ok, I'm pretty sure that when some mega corp or institute finds itself in dire need of creating a language, to solve all their computational problems, they will engineer one or design one depending on their needs. Compiler creation guidelines flow freely on the net and are available in books as well, Why wouldn't someone create a new language if he felt like it? And why wouldn't other people adopt it if they felt like it.
Whoever thinks that all technological progress should come out of universities is fooling himself, nothing bad is happening here.
Packet TTL will show just how much time the sending router gave the packet to be Delivered to its destination.
The latency should be the time= output, since that describes the time it took for the packet to actually arrive
and be acknowledged of the destination server.
that + since it is (or will be?) open source it will be quite easy to design and implement plugins for the js application.
Well, it could be that your chrome is broken :-)
No, really I have seen many chrome implementations (especially win XP & 7) where basic stuff like the location object is badly corrupt.
It usually tracks down to malware or cracked software, but is easily fixed with a reinstall (that's remove -> install. not upgrade)
My idea exactly. Are they going to open up the code for this?
But from where I'm sitting I can't see how this is different from a Terminal emulator running on you own host over https.
I had setup one of those once, there are a number of terminal emus as js standalones. You just wire it up to a script that
evals the input onto the linux https server and returns the output.
I have an XP laptop since 2003 and it hasn't had one (1!) Kernel panic in the last five (5!!!) years.
I haven't used it since 2006 but who cares?
Why wouldn't the signal carry information over the 20khz mark? That fact that you cannot directly hear it doesn't make the information disappear.
The fact is that to allow the hardware to correctly reproduce the intended soundwave you will need a lot more resolution than the one you can
perceive. Now add to that the resolution you loose through processing (anti aliasing, to analog conversion) and you will end up needing a hell
of a lot more resolution than the 44.1khz will give you. 48khz and you get a good approximation 96 on 24bit range is usually a good enough
sample to do some good work. Now if you want to do some weird post processing like removing some difficult artifacts you could find higher
sampling rates useful.
My opinion is that studio grade samples should be stored at the highest possible resolution while personal playback can very well be lower.
Most audiophiles I know see no merit to files higher than 96khz/24bit and even a 48khz/24bit recording will reproduce a very similar track.
Now all this is relevant to the signal of the recording. If the hardware used couldn't go farther than 48khz then there is obviously no reason to oversample.
My point exactly. Storage is not a factor so when you have the choice in a studio setting why not keep the best resolution you can?
Now for playback you obviously wouldn't want to log 2GB files for a 3min hiphop song, in that case you can just downsample to
flac/48khz or even 256kbps mp3. Hell, most consumers are happy with the crappy 112/128kbps rips they get extracted from youtube videos.
What? Dogs can't enjoy music now?
Yep, indeed. Kudos to Matt and his insight.
Ohh, I'm sure AMD will want you to believe that :-)
lectrolytes yo stoopid duh!