> First, there is no reason to believe that we can built robots that can reproduce themselves.
What? This is exactly the technology humans are trying to reach! We're already a significant way down this path!!
> Second, there is no evidence that we or anyone else can build intelligent machines, as the original story seems to presuppose.
Nature did it. We can do it.
> Third, biological organisms are so many orders of magnitude more efficient and flexible than machines that it barely makes sense to put them into the same qualitative category "form of life".
This whole conversation is about extrapolating on the cosmic scale. If you look at the path robotics has taken in the last century it does, as pointed out, actually support the premise of this article.
> Hint: A human consumes only about 2.9 kilowatt hours per day, the equivalent of 1-2 light bulbs
Not relevant. Once machines are replicating and repairing themselves they'll do exactly what we do and find other sources of energy.
Frankly I agree with you that it's hard to picture Transformers inhabiting the universe, but OP did make a really good point that extrapolation isn't even in the ballpark of refuting this clown. Honestly I'm shocked he didn't come back with that XKCD cartoon.
Just wanted to thank you for the links. I was especially pleased to find that Python is supported!
Thank you! You've given me reason to sit up and pay attention when 3 rolls around, I appreciate that.
I would recommend against showing the more diehard Photoshop fans that link, though. It won't get you anywhere because what it really needs to be is a list like this:
- GIMP has a plugin/feature for automatically generating normal maps from elevation data.
- GIMP has a perspective correction feature that is superior to Photoshops in that it...
- GIMP's 'save all layers' button saves all of the layers in your file into seperate files.
5 is horribly overrated. Lots of artists can script, but few (if any) can make actual plugins or modify the source code. (Even if they do dig in to the code how do they maintain those features when a new version of GIMP comes along?) I do want to mention, though, that there's another reply to my original post that seems to have covered the scripting point. I haven't checked it out yet but given that scripting is something I do, I'm certainly interested in trying that out.
6 needs an extra line, something like: "its better than Photoshop's Batch feature because...."
10... actually this is a really good one. In fact, just before this thread started, I went and found the portable version and downloaded in. Why? Welp, if the scripting that Culture20 posted a link to turns out to be worthwhile for me, coupling that with a portable version of GIMP is *awesome*. What that means is I will be able to automate certain tasks AND keep a fresh install on my DropBox account so I can even use it off-site. This is 1 out of 9.5 (I gave partial credit to the source-code bit) and, as you can already see from other replies you've gotten, most are refutable.
I'm a little worried you might read my post and think that I'm trying to perpetuate the GIMP vs. Photoshop debate. I'm not, instead I'm trying to explain what needs to happen explanation-wise to get more Photoshop people to try GIMP out. I think there's this mentality that people should switch to GIMP and that's simply not true. If you got the professional Photoshop users to start using GIMP for certain tasks, you may find that some studios may find it worth their time to invest some development time into improving it. Given how Adobe has been dicking around with the licensing, this would be a good time to get that ball rolling. Start touting the unique features it has that shave man-hours off a project. If those features don't exist, then the team needs to start talking to people like me and finding out what else they need.
If a subordinate asks you a pertinent question, look at him as if he had lost his senses. When he looks down, paraphrase the question back at him.