Ofcourse but I am waiting for some important plugins to be fully compatible with it too. Some plugin vendors wait till things are set in stone to update their stuff... yeah I could hack something together on some cases but I'd rather spend time posting on Slashdot;-)
I dare you to make a "400 pounder" get down to the tropics for that longevity test:-D
And yup... I would not want to be too skinny up here in Canada... when it gets cold... its friggin COLD... and I am pretty far south... I wouldn't survive Edmonton for instance.
How do we really know that what we now deem a waste of "information" in the DNA truly is? We would need to do tests on these "non functional" parts on some baby and then clone it with the mutated variations and then after 50 years we could make a more complete judgement on what would be large changes (current functional ones) and minor ones (that we now write off because we have more important things to focus on.)
The duplication part I write off as a safety net and not part of what I was "harping" about.
My current thinking leans towards the DNA being akin to a "compressed stream" of traits. Meaning that looking at the individual GATACA's is like looking at the the individual characters in a gzip archive or something. Things MAY look very similar and especially if there is a lot of CRC elements sprinkled inside the stream for auto correction.
Thinking that evolution is better than our own brains leads me further to think that the compression algorithm is unbelievably good... nay... "perfect."
We would have very bad mutations much more often than we have otherwise.
"becuase they must set lower limits to avoid exhausting resources."
I would say that on a high traffic site the settings are hardly defaults. Maybe you remember one of the first pthread implementations on Linux that actually spawned things as if it was processes with shared memory. It wasn't a big deal then and it certainly isn't now that things are more hidden within one process space instead, if one looks at the threded model approach (I have done ample... and I mean AMPLE fork vs. thread testing scenarios throughout my coding ventures and I have come to realize that only some coders that seem to have drunk the Fiber cool-aid abject the idea of forking. At the end of the day it matters little because the generally bungle on race-contention instead.)
Granted a fork is heavier memory wise and uses semaphores rather than simple mutexes (but one only needs to use semaphores if sending data between processes) but with today's hardware and with the amount of memory it is less of a problem. Also the O(1) scheduler in Linux for instance would work quite effectively as well from that kind of resource scheduling point of view. I would rather have my internet banking done over a forked approach than inside of a threaded approach for security reasons, but I digress.
All this is a non issue... maybe it is an issue running Apache on Windows but I wouldn't do that in any case.
Now I have had far more forked apache's running than that on Solaris/Linux/Irix (I go way back... maybe not as much as I would like in this case BUT still more than most.)
What are you talking about? There is settings in IIS regarding max connections as well and presumably would be effected in the same manner if these are set too low. This has nothing to do with fork (process) or non forked (lightweight process) method of serving.... or are you telling me that IIS is currently completely on Fiber level instead of their "Threads" ?
Either way at some point you still need to do some poll on the master socket to peek if there is some requests coming your way so you can relegate it to one of the threads in the pool. Thread pool starvation and all that... you can't really fully escape this (there I even got a pun included.)
Just tested on www.microsoft.com and I sat there in the header negotiating part for over 3 minutes before the pipe broke on remote end (I didn't do anything.) Slight change in that slowloris makes IIS* vulnerable too.
Heck one could even make it so that the header requests go out at 8 bit/s or less and just whallop any server with a lot of these requests... and have the requests FULLY valid.
Its simple for an admin to block the IP so its not that big of an issue unless it is employed as a DDoS.
# # Timeout: The number of seconds before receives and sends time out. # Timeout 120
Unless of course this timeout is for after the header is received only... which I don't think it is... but as they say... assumption is the mother of all f*ckups.
There is a couple of languages that I know of that when calling a person bing or beng (dialect differences) implicates that that person is a complete and utter moronic idiot.
Note this is not Microsoft bashing this is just facts.
I for one will NEVER use a service called something like that.
not that I want to pee all over anybodies accomplishments BUT when I see a pure implementation of BSD sockets using pure LISP and IT beats the C version then and only then will I ACK that SYN statement.
I definitely have my pliers and blow torch ready. Where is teh critter? I am really in a bug stomping mood right now.
On a more serious side note: "I didn't even find Blade Runner that great..." should by default make his post "Super Flamebait"
I guess one had to be living in the early 80ies to fully realize the Deal with the movie... but then again maybe it is about maturity too... I wonder how many of the younger crowd appreciates Citizen Kane and The Trial by Orson Welles?
But then again I didn't "like" the Reboot of Star Trek... (it was entertaining BUT not too thought provoking) IMHO it should have been called "Star Trek Ultra Light"
The whole idea of reusing good and working code is what from a business point of view is deemed evil. It is imperative to milk all customers of as much money as possible without actually delivering any form of permanent solution but barely what the customer needs (not what they are asking for.)
This is not only endemic in Microsoft but any software house these days. What is worse is that this type of behaviour has now crept in the hardware realm as well. They all looked at how Microsoft et.al. do and how successful they are by doing exactly above that there is no option for any HW company than to do the same thing. Produce shoddy products so that users need to pay, pay, pay and pay some more. (Seagate I am looking at you kid and you need serious spankin')
Why would I? Better competition breeds better solutions that's all. What makes the "competition" stronger makes everybody stronger too if done correctly... This approach of thinking is prevalent in Japan and sooner or later it will catch on over here in North America as well.
Slashdot Mirror
Much obliged, thank you!
Ofcourse but I am waiting for some important plugins to be fully compatible with it too. Some plugin vendors wait till things are set in stone to update their stuff... yeah I could hack something together on some cases but I'd rather spend time posting on Slashdot ;-)
We are all like a bunch of jonzing pirates wanting FF 3.5... Like crack addicts we need our fix... like yesterday... or the day before.
We want it NOW!!!
I dare you to make a "400 pounder" get down to the tropics for that longevity test :-D
And yup... I would not want to be too skinny up here in Canada... when it gets cold... its friggin COLD... and I am pretty far south... I wouldn't survive Edmonton for instance.
Sorry this doesn't fly with me...
So they have been shuttling her around in a baby carriage and crib for 16 years without ANYONE else but their doctor noticing?
Sorry no friggin way.
So all this has been under wraps for 16 years?!?
I call all this bull and raise them a handful of shit.
How about not showing any starts at all?
Knowing the length of the password is half the battle.
Same issue as those old POS terminals that would beep on each key pressed. Luckily they weren't beeping in different frequencies like phones.
I guess Nielsen has nothing to protect and thus surmises incorrectly this perceived inconvenience of his.
How do we really know that what we now deem a waste of "information" in the DNA truly is? We would need to do tests on these "non functional" parts on some baby and then clone it with the mutated variations and then after 50 years we could make a more complete judgement on what would be large changes (current functional ones) and minor ones (that we now write off because we have more important things to focus on.)
The duplication part I write off as a safety net and not part of what I was "harping" about.
My current thinking leans towards the DNA being akin to a "compressed stream" of traits. Meaning that looking at the individual GATACA's is like looking at the the individual characters in a gzip archive or something. Things MAY look very similar and especially if there is a lot of CRC elements sprinkled inside the stream for auto correction.
Thinking that evolution is better than our own brains leads me further to think that the compression algorithm is unbelievably good... nay... "perfect."
We would have very bad mutations much more often than we have otherwise.
IAMAG & IAMAS
"becuase they must set lower limits to avoid exhausting resources."
I would say that on a high traffic site the settings are hardly defaults. Maybe you remember one of the first pthread implementations on Linux that actually spawned things as if it was processes with shared memory. It wasn't a big deal then and it certainly isn't now that things are more hidden within one process space instead, if one looks at the threded model approach (I have done ample... and I mean AMPLE fork vs. thread testing scenarios throughout my coding ventures and I have come to realize that only some coders that seem to have drunk the Fiber cool-aid abject the idea of forking. At the end of the day it matters little because the generally bungle on race-contention instead.)
Granted a fork is heavier memory wise and uses semaphores rather than simple mutexes (but one only needs to use semaphores if sending data between processes) but with today's hardware and with the amount of memory it is less of a problem. Also the O(1) scheduler in Linux for instance would work quite effectively as well from that kind of resource scheduling point of view. I would rather have my internet banking done over a forked approach than inside of a threaded approach for security reasons, but I digress.
All this is a non issue... maybe it is an issue running Apache on Windows but I wouldn't do that in any case.
BTW: By default the thread pool would be 2048:
http://msdn.microsoft.com/en-us/library/ms682453(VS.85).aspx
Now I have had far more forked apache's running than that on Solaris/Linux/Irix (I go way back... maybe not as much as I would like in this case BUT still more than most.)
What are you talking about? There is settings in IIS regarding max connections as well and presumably would be effected in the same manner if these are set too low. This has nothing to do with fork (process) or non forked (lightweight process) method of serving.... or are you telling me that IIS is currently completely on Fiber level instead of their "Threads" ?
Either way at some point you still need to do some poll on the master socket to peek if there is some requests coming your way so you can relegate it to one of the threads in the pool. Thread pool starvation and all that... you can't really fully escape this (there I even got a pun included.)
Just tested on www.microsoft.com and I sat there in the header negotiating part for over 3 minutes before the pipe broke on remote end (I didn't do anything.) Slight change in that slowloris makes IIS* vulnerable too.
Heck one could even make it so that the header requests go out at 8 bit/s or less and just whallop any server with a lot of these requests... and have the requests FULLY valid.
Its simple for an admin to block the IP so its not that big of an issue unless it is employed as a DDoS.
mitigate it somewhat:
In httpd.conf
#
# Timeout: The number of seconds before receives and sends time out.
#
Timeout 120
Unless of course this timeout is for after the header is received only... which I don't think it is... but as they say... assumption is the mother of all f*ckups.
Nice... I raise you some radio active versions
Denebium
Betelguezium
Solium
I agree the water seems to have the wrong viscosity (too low) making it too tense of a sound.
But I could be wrong and its the rendering that has a slight speed up.
so this is what is needed to run Windows 7. Good work Asus!
Additionally...
Romania:
http://en.wikipedia.org/wiki/Securitate
East Germany:
http://en.wikipedia.org/wiki/Stasi
Yugoslavia:
http://en.wikipedia.org/wiki/UDBA
WTF happend to USA and the rest of the west?
Is it "There is no freedom but what we make ourselves" ?
When will the thought police come? Or are we already there?
Dissidents repent!
On the word Bing?
There is a couple of languages that I know of that when calling a person bing or beng (dialect differences) implicates that that person is a complete and utter moronic idiot.
Note this is not Microsoft bashing this is just facts.
I for one will NEVER use a service called something like that.
not that I want to pee all over anybodies accomplishments BUT when I see a pure implementation of BSD sockets using pure LISP and IT beats the C version then and only then will I ACK that SYN statement.
I definitely have my pliers and blow torch ready. Where is teh critter? I am really in a bug stomping mood right now.
On a more serious side note: "I didn't even find Blade Runner that great..." should by default make his post "Super Flamebait"
I guess one had to be living in the early 80ies to fully realize the Deal with the movie... but then again maybe it is about maturity too... I wonder how many of the younger crowd appreciates Citizen Kane and The Trial by Orson Welles?
But then again I didn't "like" the Reboot of Star Trek... (it was entertaining BUT not too thought provoking) IMHO it should have been called "Star Trek Ultra Light"
I guess this would technically be a "Reverse Salami Slice" , money flowing the other way an all.
Would be interesting to see if they can pull it off and the amount of paper work needed will be epic!
Hey the interface took out my "sarcasm*cynicism" tags.
The whole idea of reusing good and working code is what from a business point of view is deemed evil. It is imperative to milk all customers of as much money as possible without actually delivering any form of permanent solution but barely what the customer needs (not what they are asking for.)
This is not only endemic in Microsoft but any software house these days. What is worse is that this type of behaviour has now crept in the hardware realm as well. They all looked at how Microsoft et.al. do and how successful they are by doing exactly above that there is no option for any HW company than to do the same thing. Produce shoddy products so that users need to pay, pay, pay and pay some more. (Seagate I am looking at you kid and you need serious spankin')
That may be so or more likely, the setup is plain wrong and is not using named pipe and instead TCP over localhost.
But sure maybe they jumped over to Oracle DB... that would indeed be a funny and ironic side effect.
Why would I? Better competition breeds better solutions that's all. What makes the "competition" stronger makes everybody stronger too if done correctly... This approach of thinking is prevalent in Japan and sooner or later it will catch on over here in North America as well.