i do have horror stories to share. do you need to hear them?
more importantly, i have very positive stories to share about very positive things. none of them include claims by the manufacturers that include statements that reduce to MANIPULATIVE LIES.
i do not deal with people that operate in that fashion.
F# STINKS.
my dog eats poop... i'm not saying you shouldn't eat F# up... i'm sure lots of people will. people who don't mind things that STINK.
the solar system is a program of physics. a child understanding the program enough to alter a simulation of it makes the claim of the child having no programming experience quite questionable.
if they succeed, then everyone will agree that their product accurately provides reliable results.
after that happens, in the same way search engine optimizers operate, beef quality optimizers will step in to spray on or radiate out whatever the device is looking for.
fast forward a generation and we're all convinced mcnuggets are the highest quality food.
here is my thoughtful argument in addition to a statement that your mother raised an idiot.
grocery store analogy is retarded. i don't want any grocery store, i want a specific grocery store, but i don't know where it is. they have multiple locations.
thank fully i can ask people where the nearest grocery store is.
now at that point would i ask for the nearest grocery store, or a specific chain of grocery stores, or just any place i can get a sandwich?
WE ARE TALKING ABOUT NETWORK DNS REQUESTS, NOT GROCERY STORES.
it's not about the DNS server the user is using... it's about the DNS servers used by the DNS server the user is using... and any DNS servers they might use.
that is not specious. that is a problem.
the user never directly entered into any agreements with the service providers in the middle.
what about the DNS authority that the users DNS authority uses? or what about the DNS authority that DNS authority uses?
currently the user defining IP is visible to the ISP and the domain owner the user requested. as it should be, as i have never entered into any agreements with anyone else.
domains can already manage their own worldwide content distribution networks, and route requests after they get to them.
when large volumes of bits are involved, like most responses from cdn servers, then YES, "This is important!"... but for the dns request packets to also be pooled and routed in this fashion is unnecessary and as the submitter points out opens up massive privacy holes currently plugged.
this isn't about single points of failure... it's purely load balancing that can already be done without sacrificing anything. google just has their hands on so much of the system that it makes sense to them, the same sense it would make for a video software developer to put a mpeg codec directly in the OS kernel...
well... what you see is information. that is what they have. you need knowledge and information. you must click more if you wish to find knowledge and information.
Slashdot Mirror
while he may be entirely correct about "marketing droids", the conclusion that "F# stinks" doesn't exactly follow from that
it does when the subject in question is THE CREATOR OF THE PRODUCT.
F# STINKS
i do have horror stories to share. do you need to hear them?
more importantly, i have very positive stories to share about very positive things. none of them include claims by the manufacturers that include statements that reduce to MANIPULATIVE LIES.
i do not deal with people that operate in that fashion.
F# STINKS.
my dog eats poop... i'm not saying you shouldn't eat F# up... i'm sure lots of people will. people who don't mind things that STINK.
the solar system is a program of physics. a child understanding the program enough to alter a simulation of it makes the claim of the child having no programming experience quite questionable.
go tell someone else, marketing droid. F# stinks.
Even after well over a decade, PHP still makes is too damn easy to write code.
fixed that for you....
what about lighttpd?
if they succeed, then everyone will agree that their product accurately provides reliable results.
after that happens, in the same way search engine optimizers operate, beef quality optimizers will step in to spray on or radiate out whatever the device is looking for.
fast forward a generation and we're all convinced mcnuggets are the highest quality food.
the LOAD for the RESPONSE is ALREADY HANDLED BY CDN.
the load OF the REQUESTS is ALREADY HANDLED BY DNS.
you are NOTHING.
MY DNS server....
what if MY DNS needs to use SOMEONE ELSE'S DNS server?
i never entered into an agreement with them... my DNS provider did... so any requests THEY send should include THEIR info... NOT mine.
the DNS layer isn't about load balancing, and shouldn't be.
here is my thoughtful argument in addition to a statement that your mother raised an idiot.
grocery store analogy is retarded. i don't want any grocery store, i want a specific grocery store, but i don't know where it is. they have multiple locations.
thank fully i can ask people where the nearest grocery store is.
now at that point would i ask for the nearest grocery store, or a specific chain of grocery stores, or just any place i can get a sandwich?
WE ARE TALKING ABOUT NETWORK DNS REQUESTS, NOT GROCERY STORES.
YOU ARE AN IDIOT.
and the answer to all of your other bogus issues: CDN.
good use on the quotes around "wrong"....
you're right... it isn't "really" wrong.
it's not about the DNS server the user is using... it's about the DNS servers used by the DNS server the user is using... and any DNS servers they might use.
that is not specious. that is a problem.
the user never directly entered into any agreements with the service providers in the middle.
DING DING DING DING DING DING
right on the head.
anonymous genius.
are you joking? i'm not teaching classes here.
your question is flawed. you obviously don't understand the system.
what about the DNS authority that the users DNS authority uses? or what about the DNS authority that DNS authority uses?
currently the user defining IP is visible to the ISP and the domain owner the user requested. as it should be, as i have never entered into any agreements with anyone else.
NO IT ISN'T.
domains can already manage their own worldwide content distribution networks, and route requests after they get to them.
when large volumes of bits are involved, like most responses from cdn servers, then YES, "This is important!"... but for the dns request packets to also be pooled and routed in this fashion is unnecessary and as the submitter points out opens up massive privacy holes currently plugged.
this isn't about single points of failure... it's purely load balancing that can already be done without sacrificing anything. google just has their hands on so much of the system that it makes sense to them, the same sense it would make for a video software developer to put a mpeg codec directly in the OS kernel...
the layers are there for a reason.
i will bet you $100,000 that the area of the frame is not larger than the area of the display.
you can't be this dumb.
is that you michael dell? jealous?
you would like the frame to be 39% of the body?
you want it shaped like your front door?
has slashdot readership forgotten the meaning of not being dumb?
iphone nano
triple whoosh
there is also a bug in the interface to switch locales... once you make locale=el_GR you can't get out of it.
message?
all i did was read the first sentence of text in the first video that automatically displays...
scientology.org... see for yourself.
they also welcome vistors defensively and suggest the vistors have heard negative things... they are probably right.
well... what you see is information. that is what they have. you need knowledge and information. you must click more if you wish to find knowledge and information.
knowledge and information
scientology videos
how about both of you shut up?