mcs

All of these jsonp / iframe based instantizers have to be putting load on servers (probably not in great volume, but still). There's a reason Google had to put special consideration into how to make the ajax-endpoints scale :)

I'm going to be that guy, but I disagree with that as well. I lived in a very poor area in Southeast Texas and built my first computer (literally) from junk parts I found in ditches. I had a little help but it was pretty easy to figure out since everything had notches to make sure everything goes in the right place.

I was 8, coincidence here.

With a pirated Windows 98se from my mom's boyfriend at the time, it worked out alright. I tied up my mom's phone line with netzero, and that's when I started my adventure into the web.

Edit: For clarification, I had built a 233mhz machine with 32mB of ram. I put 98se on it because I hadn't learned of linux yet, and it probably would have been too much for me at that time anyway. Ubuntu didn't exist.

Around age 10 we finally got DSL, and by that time I had gathered up enough money to build a "real" machine, with an Athlon XP. Again, with all pirated software.

Software piracy enables more to younger poor people than your parents being wealthy in my opinion. Not saying it's right, but it sure allowed me to do things I otherwise wouldn't have been able to do.

That article is more relevant for people that grew up in the 80s, when hardware was less available than it is today. I started my adventure in the 2000s.

I'm 18 now, work for a startup, and I have quite a little nestegg from social marketing apps I've built in the last few years. Nothing my family did really had any effect on my interest in computers.

So if you have Dish Network, and the HD version is right above the SD version on the channel guide, you'll watch the SD version if the number is even?

Some actually try to remove lines of code on purpose. :)

I spend more time thinking about program architecture and design than actual coding.

Unless it's something simple, then I can just open vim or textmate and go to town. If it's something that I know the development scope is fairly small I may even dive in and figure things out along the way. It really depends on the project.

I can crank out a few hundred lines of code per hour but that's totally subjective. 10 lines of code in node.js do a lot more than 10 lines of code in C.

There's also the revision stage if it's a project you know you'll come back to. I generally do spend more time refactoring than the initial prototype. I would hope a lot of developers are like that.

For example, I wrote a Meebo libpurple connector in glib in about 3 hours, but I spent 2 days refining it before I could consider it useful because I had done things that were silly and not the normal way of using glib.

Is the music still being done by Daft Punk?

It's not even pop. :)

Well Adam has stated in at least one interview that he reads Hacker News regularly so maybe we'll have a nice anonymous reply :)

The E block is really 'reserved' and 'meant for test purposes'.

If Windows can't talk to those IP addresses they're actually within spec. Though it is a useless waste of a lot of bits.

I figure one change that will happen at the beginning of this "crisis" will be that ISPs will start NATing traffic, as tptacek said.

A lot of ISPs already have policies for not having daemons on ports, so they could use that as justification for not having your own IP completely accessible from every port (which I don't believe would be possible without explicit port forwarding from the ISP itself).

What would this mean for end users' internet? Not much, but IPv4 IPs would be shared by multiple users (hopefully not many at first). A lot of websites have session policies and all sorts of mess based on the remote address, so it will be interesting to see how the aging webapps deal with the change.

I figure servers will get first priority at v4 addresses. Yeah, there's useless crap going on like IRC vhosts, but I figure once the market closes in on the addresses people will likely sell them (hell, I know people squatting on address blocks until the 'apocalypse', thinking they'll score a huge profit!).

Fun times.

It's kind of funny that people see PHP related to anything other than serving websites and they cringe.

As of 5.3 (and I won't say prior to that because even I don't believe it), PHP has become a nice utility language for just more than serving out wordpress.

Closures and the reference sweep GC level the playing field.

It's okay.

http://github.com/scottgonzalez/figlet-js

I hope nobody. Cloud webhosting shouldn't just take apache out of the box and cloudify it. An event driven http server designed for cloud requests needs to be designed from the ground up, but implement most of the .htaccess directives to be viable for your average webhosting consumer.

With Redis, memcached finally has a contender for most awesome cache... thing. However I'm surprised I don't see more benchmarks. Performance should be roughly the same unless there's huge I/O contention for persistent storing.