daakus

In other words - CSRF fail.

Marcel Laverdet has built a node extension that provides yield: https://github.com/laverdet/node-fibers

I did have SICP when I started undergrad, and I wish, and asked my professor why can't we use "something modern like python". He gave me some reasoning, and I wish I remember what it was. I think part of the problem is that there isn't enough of a "fun" or "excitement" component in SICP for a very many n00bs, which I was then. Python was cool. Perl was cool too. They're not terrible languages, but admittedly boggled down by syntax. Scheme had a "for education purposes rep" (many times propagated by professors themselves). And there was no "easy_install mechanize" or "easy_install pyqt" to start doing cool shit in Scheme (which I don't believe is true, but for whatever reason at that point it wasn't apparent this was even an option to me).

Overall, I had a lot more fun starting off with Python on my own time. I may have taken longer than most to come around and appreciate Scheme, and certainly find myself wishing JavaScript had less syntax. SICP is awesome though. In fact, I sold most of my books after I was done with university including that one. But maybe 3 or 4 years later, I ended up purchasing it again as I wanted to find classic Lisp literature. Only after it got delivered did I realize this was the same book. And this time around I did truly enjoy it. But I wish I remember what reasoning my professor gave for preferring Scheme over Python.

Why would one use a language where the best you can say is "it gets the job done". There are so many better options in absolutely every single way that the only reason I can fathom for one to start something new using it out of choice is laziness to learn something better.

It's sad that Safari does this, especially considering there's a work around using POST: https://gist.github.com/586182 -- it translates to complexity and has performance hit, and doesn't actually add security.

If you click on the lock icon on Facebook to set privacy, you can type in names of lists to explicitly hide or specifically limit content (blacklist or whitelist). This would allow posting some piece of content controlled via a named list of people you've created.

This combined with MicroXP resulted in a ~500MB VirtualBox image with IE6,7,8 -- very impressive.

Unnecessary plug: I wrote a ridiculously simple version using node and socket.io to get a feel for this too: https://github.com/nshah/tictactoe -- it only has random matchup mode. It's running here: http://tictactoe.daaku.org:9999/

I'd split the semester into two parts -- one close to metal, something simple like a url shortner. Then something using an existing framework to build something more complex like a blog with an admin interface and some RSS feeds or JSON API.

"He couches his fanaticism in "good taste"." -- this is exactly it. It is fanaticism no doubt. Given enough variables, like there are here, making it taste good is clearly possible. I use and like Apple products, but trying to justify everything they do as being "good for the user" does no good imho.

I had a good experience with Prgmr for the most part (dirt cheap memory for the price), and was reliable while I was using it. My only gripe was that IO performance was terrible, to the point that using ls in bash was annoying.

I switched to Linode and have been very happy with it.

I understand the need for analytics, but I _think_ most twitter users don't care about that. Couldn't twitter just not count the URL towards the 140 characters? (Yes, more complicated than that in order to prevent spam or whatever, and yes backward compatibility sucks. But basic auth is being killed too.)

Maybe I'm a bit crazy, but I just disable swap all together. With 2 tornado servers, 2 nodejs servers, nginx, postgres, memcache and monit I end up using 170M of memory. (None of the sites are data heavy, so this may be skewed.)

Don't macros change the rule a bit?

I open tabs in the background all the time -- this doesn't seem any different than one of those being a phishing site. It's pretty simple imho, don't type in a password unless you also typed in the url or used a bookmark. That's the advice I usually give family/friends.

I just rent a cheap $20 month VM on the cloud. Every now and then I need another one to test stuff, so I'll just rent another one for that duration, which get's pro-rated. Screen does the rest. Having scripts to bootstrap VM's is crucial to make this setup viable imho. I do wish cheaper dedicated servers were available with the same easy management cloud VMs provide.

while i'm all for using modern css capabilities -- i think ie7/ie8 will keep us from relying solely on them. i haven't looked into Aristo's source, but using sprites as a fallback the less capable browsers is pretty much the only option atm. add to that the fact that it's typically difficult or impossible to sprite gradients and rounded corners well, and the number of images used don't seem ridiculous anymore.

I think the point is avoiding complexity until absolutely necessary. Splitting code and creating abstractions "because it will make doing X easier in the future" is often the wrong thing to do. The right thing imho is to split it when you need X now, not the future.