Generally you purchase a screen from eBay or various other places, then use our (iFixit's) guides to replace the old with the new.

Having the correct tools does not magically make broken things unbroken, but it helps you to repair them.

Hi! We're trying to build out a comprehensive set of resources for people wanting to start a repair business ([1], [2]), and we'd love to have any feedback or suggestions you might have. Information on the most common repairs, like what you've just provided, is an excellent example of the type of thing we're wanting to make more common knowledge.

Contrary to whatever silly fantasy world you live in, 99.9999% of the population DOES NOT GIVE A SHIT ABOUT DISASSEMBLING THEIR PHONE. They just use the damn thing.

They use it until they crack the screen; then they want a non-broken phone.

We do.

Ruby 3.0 is a long ways off. You probably want Rails 3.0 and Ruby 1.9.

Embraced, dammit.

Sure, but hasn't the Python community kinda imbraced Django as the One True fullstack framework?

Well, to be pedantic, that is the *cost* of the (L)GPL. The price is 0.

I am not an economist.

In some countries, you can't really. That's why we have the WTFPL. The Wikipedia article says there are only 11 uses of it on Freshmeat, but it's rather commonly used on GitHub.

Of course, by that time, everyone else will have been using Markdown (or similar) for 10 years.

You go inside to pay for gas? I just use the cardswipe/pinpad on the gas pump, which I thought was pretty standard practice these days.

The reason we complain so much about electronic voting systems is because all of the ones used in the U.S. are horribly insecure.

Perhaps that's because they didn't suck so much in the first place (with the possible exception of MRI)?

Because everyone chooses a language based on raw execution speed, amirite?

You were comparing relative increases between different implementations of one language before; now you're comparing the fastest implementation of one language to the not-fastest implementations of others. =_=

Even if they look vaguely similar on the surface, all of the languages you've mentioned are quite different internally. Some performance changes that would take too much effort to change, some won't happen for philosophical reasons, and a great deal more are not applicable to anything other than the language they were written for.

Perl... well, it's either dead or incredibly alive, depending on who you ask, but all development seems to be focused on Perl6.

Ruby doesn't have an "official" interpreter. The standard C implementation uses YARV for 1.9, which is considerably better than MRI (which was in 1.8). Rubinius is supposed to be faster, but isn't quite ready yet. Ruby Enterprise Edition seems to be fairly popular, but doesn't have 1.9 compatability yet. I believe JRuby is fairly widely-used, and it seems that it can perform better than YARV sometimes (and consistently better than MRI).

On the Python front, Unladen Swallow seems to be chugging along, although I'm not sure what we'll get out of it. PyPy is quite promising, and is faster than CPython in many benchmarks.

And pretty much everyone except Apple is planning on supporting WebM (or is, currently). Sure, IE will only support it if a vp8 codec is installed on the machine, but that counts enough for me.