The gratuitous U.S. bashing in this thread looks exactly like something you'd see on Reddit (more likely, Digg). Not only is it ugly, it's utterly irrelevant to the nominal topic of discussion. Even if the U.S. were Nazi Germany, the Stalinist U.S.S.R., and the Pol Pot regime rolled into one, it would have zero relevance to the ethical position of Google with the Chinese government.
I suppose I could have said that Paul B.'s position (and that of several others) is a classic example of the tu quoque variety of ad hominem fallacy, but that would basically just be using Latin to say the same thing.
"Exactly who is in Guantanamo or the secret CIA prisons, and why?"
Well, not you, and not anyone you know.
The mere fact that you're comfortable posting this stuff on a public site, under your own name, demonstrates that you have ZERO fear that someone will break down your door tonight and take you off to a "secret prison".
To be quite blunt: you don't even believe your own bullshit.
Wow, for $1,000 per year you could just about buy a MacBook and a copy of Parallels, which would let you create a full library of VMs with all the different browsers and operating systems, then load any one you wanted.
Plus -- you'd have a sweet machine to use for other purposes when you weren't testing. This sounds way overpriced.
You could do the same thing with VMWare Fusion (though it's still in beta, and I haven't tried it).
Err... what does doing math have to do with it? If I have a good (human) assistant, I can ask him or her to find me all the Y Combinator articles and it just works. I don't need to write some formal mathematical description of the task.
It's true that it's all math/physics/chemistry underneath, due to how the brain works, but in practice we never worry about that, just as an engineer doesn't generally consider quantum and relativistic effects when he's designing a bridge, or an outfielder doesn't scribble down a bunch of differential equations before catching a fly ball.
Sure, any standard computer is equivalent to a bounded Turing machine, but Turing machines are a real pain in the ass to program.
Mathematical purity is one thing. Getting your work done is quite another.
As a second source (it's sometimes helpful to hear material from more than one perspective), UC Berkeley has some podcasts from a Scheme course which uses SICP:
I listened to a few of them a while back, just to check them out. Not bad, if you can ignore the lecturer's occasional side-trip into politics (well, it IS Berkeley).
Someone mentioned below that it's working on Reddit. I just looked at their feed, and it looks like they are indeed putting the comments link inside "description" rather than "comments".
Maybe try generating an Atom feed? Atom seems to be much better defined than any of the myriad competing RSS implementations.
Or maybe toss a hyperlink into the description tag rather than the comments tag ... from what I see in the RSS 2.0 spec, comments is a more of a "should" rather than a "must". The spec itself refers to it as an optional element, and Winer (I think) says in a note that implementers "should" support it. Clearly some of them don't. :-)
"I bet most people who use/used PHP got there because it was popular"
This is fairly accurate, but not quite the whole story.
Ascribing PHP's success to "popularity" makes it sound like a simple fashion statement. The reality is that, due to its popularity, PHP has a ton of libraries and an enormous base of existing code (ranging from little hacks to parse a certain data format all the way up to full-blown applications like MediaWiki). It's not just the language, it's the ecosystem.
That's a real advantage that's often overlooked by those who advocate other languages. Also, don't forget that PHP hosting is cheap and ubiquitous. Rails, not so much.
That said, Ruby is catching up pretty fast, and I've been using Ruby (and sometimes Rails) for any new project that isn't tightly coupled with existing code. For me, writing Ruby is vastly more pleasant and efficient than writing PHP, even though I've been using PHP for five years and Ruby for only one.
I still write a lot of Java, too, but JRuby is starting to eat into that pretty fast. It's an end run around the library/existing code problem.
Thanks, but I'm looking for instructions for going the other way. The Wikipedia article (at least the one I found) has good information for sending email to cell phones, but that information is all over the place.
What I need is a comprehensive, cross-carrier list for sending email from cell phones. I've found this information for a few carriers, but it's not complete by any means. For instance, it looks like Cingular (U.S.) and Rogers (Canada) use the same method as T-Mobile (U.S.), just using a different number (500 for T-Mobile, 121 for Cingular, and 0000000000 for Rogers).
I may have to devote a few days to digging out this information by hand from the carrier web sites. If I do, I'll add it to the Wikipedia article.
MacBook (non-pro). I'm poor/cheap, plus I actually prefer a smaller form-factor for notebooks; I have full-sized external monitors at both home and work, so the smaller display is a non-issue where I spend most of my time, and a postive advantage when I'm mobile.
Does anyone know of a reference list for sending from SMS to email on various carriers/platforms? There are all kinds of resources for sending email to SMS (generally involving sending it to (phone number)@(carrier address.com)), but I haven't been able to find a cross-carrier reference for going the other way.
On my T-Mobile service, for instance, I have to send an SMS to "phone number" 500, with the email address, subject, and body of the message separated by appropriate delimiters. How does it work on other carriers?
MacOS is a nice Unix in its own right, and if you really need to have Linux, it runs fine under Parallels. I've got Windows XP, Ubuntu, and the One Laptop Per Child project images on my MacBook, and can boot any of them depending on what I want to check out.
I've often wondered how much of the explosion in web creativity can be attributed to the transparency of HTML -- you can "view source" any page and find out exactly how the designer created that cool effect. By comparison, Flash is opaque. Yes, there are tools that let you dig in to the ActionScript and whatnot, but you don't have the immediacy of seeing it right there in your browser.
While Textmate is indeed the shizzle, this app isn't really playing in the same space.
Textmate is a code editor (and a very nice one). Coda is a web design tool, like Dreamweaver (integrated preview pane, built-in GUI support for CSS mangling, etc.). Coda looks to be a lot cleaner than Dreamweaver. I like it -- but I'm not sure I do enough web design to justify switching. It has more to do with the time to learn a new app rather than the cost; while Dreamweaver may be nasty, I've been using it for a long time. If I found myself needing to do a lot of web design, I'd definitely consider a switch. Coda seems elegant and intuitive.
I'm outta here.