that people don't really want machines to exhibit human intelligence. You wouldn't like real AI. You could just hire a secretary. People just want machines to be more responsive.
Flash tends to be small (even smaller than equivalent sized JPEG in many cases). You can always use a proxy which blocks requests for swf files and replaces it with a blank one, ala squid or something.
No, the thing I hate is the flash plugin, which tends to peg the CPU. Click to play keeps it from loading until I want it to. It also stops me from seeing those annoying banner ads (while still "registering" an impression)
No wait, it looks like a hack-job whacko's website! Not the first time I've seen it pushed here.
If detailed analysis means he would take each raw exposure image of the "machinery" and, considering the response curves, building a likelyhood estimate model of the chemical composition due to reflectivity across various bands, and produce a list of likely material compositions...
Oh wait, he's making speculations based on what it "looks like" from a grainy photo?
Give me a fucking break. I have a paperweight that kinda looks like Jesus when the sun is setting. Interested?
divided into parallel channels by a strong surface wind. It's fairly evident by the even spacing that the formation has a uniform density. I believe the prevailing flow is SW to NE (assuming up is "north") because of a small, secondary ridge of accumulated material on the NE side of the formation. As wind blows particles from the slopes of the channel and down the backside, some is desposited and builds up upon itself on the plateau behind it.
You can tell its wind-based by the similar bottom-left to top-right streaks all over the landscape.
Very cool, but definitely not organic. You would see this kind of thing at the beach if we have hurricane force winds all the time.
You can't just combine grayscale images from the L2, L3 and L5 filters to get a color in between ("true" red).
They have widely varying response curves all over the visible spectrum. Combining them all will make a huge, lumpy response curve centered somewhere around the red visible, but emcompassing and emphasizing frequencies well outside it!!! It will be completely unrepresentative of what the eye would see on Mars. The same goes for all the other simple mixing he's doing, adulterating the other bands.
The filter response for L1-8 are NOT notch filters people, they have defined curves. Two of the filters are specifically wide band responses as well. And the human visual response curves are equally important.
No, what he SHOULD have done is essentially what Nasa did, which is to solve a minimization problem matching up weighted averages response curves from the available filters to the red/green/blue response of the human eye, and taking the combination with least squared error.
But apparently he was too simple-minded to realize this. And also that NASA saturated all of their pictures on tranmission to reduce error (and the exposure settings are nowhere to be found), so you have even less information to go on.
He just kept the combinations he "liked", method be damned. Nasa did the same thing for the press. His colors are not "correct" and your arguments hold no water (oh, I'm sorry, MUD) if you cite him as authority.
and I'm sure you could otherwise survive the unending, deadly wind of alpha particles, free neutrons, and other ionized nasties streaming out of the sun. You do know that if the van allen belts suddenly failed, you'd be a dead man.
Setting off hydrogen bombs in space is a drop in the bucket, my friend.
But if it was just asleep, it takes about 3 or 4 seconds to be usable (that's about how long it takes to intialize the video and spin up the hard drive if necessary).
It seems about consistent for linux and windows. I imagine FreeBSD is the same; I've never used it on a laptop.
They don't actually move. These web browsing agents, personal agents, what-have-you, are all installed on the devices where the information will be processed by IT guys or yourself.
It is foolish to assume the code moves with the data. The data moves to the code, and the code runs wherever we let it (and this is the fundamental change).
aside from XLST, there isn't anything really valuable about XML anyway. It looks like HTML, so maybe that's comforting. Of course it only helps humans to read it, but never mind that you need a DTD anyway to make sense of it, so it's not really convienient for humans OR computers. Until Microsoft, IBM, et al. spoke up and decided what DTDs and protocols they were going to use, it wouldn't help at all. In fact, you could just drop the XML and call it any old binary protocol, as long as everyone agreed on what it was. It might as well be ASN.1 over TCP/IP for what it's worth. It's UDDI that's the real enabler. It does the actual work of finding the stuff to hook up, and negotiating how.
Anyway. It's more about having operating systems that cluster better (especially w.r.t. data storage, SANs) which let you decouple the workload from your physical hardware resources. It's funny because the decreasing cost of physical hardware, with a focus of harnessing many smaller servers is what drove this effort. This is how the industry reacted when businesses were just buying what they needed upfront, underestimating and having to buy incremental hardware to meet demand. So they make their OSs and services scalable. Now suddenly the system integrators release they can just take all the small boxes back and sell it out to you "on demand" instead!
That kind of detachment is what makes it possible to abstract services too. Web services is just one way to hook it all up.
But I think the companies are giving this idea more credit than it warrants. It's a confluence of situations, not some kind of revolution.
as network services. The idea being you have the network listener already written, and you can add functionality by hooking it up to easy-to-write stdin/stdout unix utilities on any port via the configuration file. *inetd does all the hard stuff (connection throttling, creating/maintaining sockets, etc.) and you just write a simple implementation of the protocol you want to implement in a perl script or C or something.
hosts.allow and hosts.deny are a configuration files that were historically used by inetd, but xinetd and tcp_wrappers also honor them, in addition to their own configuration files.
The question is, why haven't you downloaded an ISO? You can subscribe to RedHat's errata list and know when to look for new WB RPMs (or just rpm -bb the SRPMS from RHES, same difference)
SuSe, Mandrake, and Redhat (well anything UnitedLinux too) use the sysvinit scripts.
That is/etc/init.d,/etc/rc#.d, chkconfig. Some differ in easy access to subsystem start/restart. I'm fine with calling the scripts directly, so I never differentiate.
Slashdot Mirror
that people don't really want machines to exhibit human intelligence. You wouldn't like real AI. You could just hire a secretary.
People just want machines to be more responsive.
animated, full-motion pokers, with sound!
Flash tends to be small (even smaller than equivalent sized JPEG in many cases). You can always use a proxy which blocks requests for swf files and replaces it with a blank one, ala squid or something.
No, the thing I hate is the flash plugin, which tends to peg the CPU. Click to play keeps it from loading until I want it to. It also stops me from seeing those annoying banner ads (while still "registering" an impression)
Fuck Quest
"It rewarded me by crashing my computer."
makes me think all kinds of credible.
No wait, it looks like a hack-job whacko's website!
Not the first time I've seen it pushed here.
If detailed analysis means he would take each raw exposure image of the "machinery" and, considering the response curves, building a likelyhood estimate model of the chemical composition due to reflectivity across various bands, and produce a list of likely material compositions...
Oh wait, he's making speculations based on what it "looks like" from a grainy photo?
Give me a fucking break. I have a paperweight that kinda looks like Jesus when the sun is setting. Interested?
divided into parallel channels by a strong surface wind. It's fairly evident by the even spacing that the formation has a uniform density. I believe the prevailing flow is SW to NE (assuming up is "north") because of a small, secondary ridge of accumulated material on the NE side of the formation. As wind blows particles from the slopes of the channel and down the backside, some is desposited and builds up upon itself on the plateau behind it.
You can tell its wind-based by the similar bottom-left to top-right streaks all over the landscape.
Very cool, but definitely not organic. You would see this kind of thing at the beach if we have hurricane force winds all the time.
You can't just combine grayscale images from the L2, L3 and L5 filters to get a color in between ("true" red).
They have widely varying response curves all over the visible spectrum. Combining them all will make a huge, lumpy response curve centered somewhere around the red visible, but emcompassing and emphasizing frequencies well outside it!!! It will be completely unrepresentative of what the eye would see on Mars. The same goes for all the other simple mixing he's doing, adulterating the other bands.
The filter response for L1-8 are NOT notch filters people, they have defined curves. Two of the filters are specifically wide band responses as well. And the human visual response curves are equally important.
No, what he SHOULD have done is essentially what Nasa did, which is to solve a minimization problem matching up weighted averages response curves from the available filters to the red/green/blue response of the human eye, and taking the combination with least squared error.
But apparently he was too simple-minded to realize this. And also that NASA saturated all of their pictures on tranmission to reduce error (and the exposure settings are nowhere to be found), so you have even less information to go on.
He just kept the combinations he "liked", method be damned. Nasa did the same thing for the press. His colors are not "correct" and your arguments hold no water (oh, I'm sorry, MUD) if you cite him as authority.
I mean, they spent a lot of money on that camera, it seems a piddly thing to leave out of it and the comm protocol for sending the pictures.
I repeat, Who is that little succubi ?
Soooo cuuuute. >_<
>_ I want one.
Holy shit that game appears to kick ass from the trailers. Do I have to learn Japanese to play?
Because it kicks ass compared to 5 years ago, esp. with Mandrake or even RedHat.
I mean, do you need anything more than emulated games?
Anyway. What the _hell_ is SubGenius? It's so fucking, I don't know, lame + inaccessible + clique-y.
I've gotten some kind of weird suntan from the GBA SP.
You suck, munch a won-eyed fyeRman.
In other words, eat a dick, and choke on the blood.
and I'm sure you could otherwise survive the unending, deadly wind of alpha particles, free neutrons, and other ionized nasties streaming out of the sun. You do know that if the van allen belts suddenly failed, you'd be a dead man.
Setting off hydrogen bombs in space is a drop in the bucket, my friend.
I could have SWORN up and down that it's in the standard. I thought the scales were 3m low power, 10m medium power, and 30m high power.
But if it was just asleep, it takes about 3 or 4 seconds to be usable (that's about how long it takes to intialize the video and spin up the hard drive if necessary).
It seems about consistent for linux and windows. I imagine FreeBSD is the same; I've never used it on a laptop.
They don't actually move. These web browsing agents, personal agents, what-have-you, are all installed on the devices where the information will be processed by IT guys or yourself.
It is foolish to assume the code moves with the data. The data moves to the code, and the code runs wherever we let it (and this is the fundamental change).
interface now seems to be Windows NT 5.x. (okay, so XP SP1 supports automatic throttling, but you can't control it)
Yawn. 3rd party software? Bleah.
And yes, it supports Centrino.
aside from XLST, there isn't anything really valuable about XML anyway. It looks like HTML, so maybe that's comforting. Of course it only helps humans to read it, but never mind that you need a DTD anyway to make sense of it, so it's not really convienient for humans OR computers.
Until Microsoft, IBM, et al. spoke up and decided what DTDs and protocols they were going to use, it wouldn't help at all. In fact, you could just drop the XML and call it any old binary protocol, as long as everyone agreed on what it was. It might as well be ASN.1 over TCP/IP for what it's worth.
It's UDDI that's the real enabler. It does the actual work of finding the stuff to hook up, and negotiating how.
Anyway. It's more about having operating systems that cluster better (especially w.r.t. data storage, SANs) which let you decouple the workload from your physical hardware resources.
It's funny because the decreasing cost of physical hardware, with a focus of harnessing many smaller servers is what drove this effort. This is how the industry reacted when businesses were just buying what they needed upfront, underestimating and having to buy incremental hardware to meet demand. So they make their OSs and services scalable. Now suddenly the system integrators release they can just take all the small boxes back and sell it out to you "on demand" instead!
That kind of detachment is what makes it possible to abstract services too. Web services is just one way to hook it all up.
But I think the companies are giving this idea more credit than it warrants. It's a confluence of situations, not some kind of revolution.
as network services. The idea being you have the network listener already written, and you can add functionality by hooking it up to easy-to-write stdin/stdout unix utilities on any port via the configuration file.
*inetd does all the hard stuff (connection throttling, creating/maintaining sockets, etc.) and you just write a simple implementation of the protocol you want to implement in a perl script or C or something.
hosts.allow and hosts.deny are a configuration files that were historically used by inetd, but xinetd and tcp_wrappers also honor them, in addition to their own configuration files.
I mean really.
Never mind that `mozilla' is a shell script anyway, which lets you set the TMPDIR for anyone who uses it on said system.
I don't see the problem.
Come on people, use common sense.
The question is, why haven't you downloaded an ISO?
You can subscribe to RedHat's errata list and know when to look for new WB RPMs (or just rpm -bb the SRPMS from RHES, same difference)
SuSe, Mandrake, and Redhat (well anything UnitedLinux too) use the sysvinit scripts.
/etc/init.d, /etc/rc#.d, chkconfig. Some differ in easy access to subsystem start/restart. I'm fine with calling the scripts directly, so I never differentiate.
That is
Also note these are all RPM-based.
Debian and Slack use rc-subsys BSD-style scripts.
Also, everyone is using xinetd these days.