Forgot your password?
typodupeerror

Comment: Re:It's about time (Score 2) 260

by xiong.chiamiov (#44096253) Attached to: iFixit Giving Away 1,776 "iPhone Liberation Kits"
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.

Comment: Re:It's a nice framework (Score 1) 110

by xiong.chiamiov (#33419296) Attached to: Rails 3.0 Released

But these serve different purposes. The kind of app you'd use Sinatra for is the kind of app Rails would be worse at, and vice versa. Sinatra is more in the same space as Camping, and I don't know if anyone still uses Camping.

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

Comment: Re:Speechless (Score 1) 282

by xiong.chiamiov (#33398582) Attached to: Czech Copyright Bill Undercuts Copyleft, Artists

Excuse me... Free has little to do with price. And in the case of GPL and LGPL, the price is as follows: "If you use the software you have to provide the source and any possible modifications you might have made to the people you sold/gave the software to." That's the price. Whether you view it as worth nothing or priceless all is in whether you're just a user or a developer.

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

I am not an economist.

Comment: Re:They released it under the BSD license? (Score 1) 337

by xiong.chiamiov (#33398400) Attached to: Glibc Is Finally Free Software

How exactly do you put something into public domain legally, such that you can legally protect them to be in public domain?

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.

Comment: Re:...And one generation behind on HTML5 (Score 1) 341

by xiong.chiamiov (#33293522) Attached to: Firefox 4 Will Be One Generation Ahead

So in summary they haven't been getting similar improvements in speed.

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.

Comment: Re:...And one generation behind on HTML5 (Score 1) 341

by xiong.chiamiov (#33293060) Attached to: Firefox 4 Will Be One Generation Ahead

> There's "fat-val", "tracer JIT" and "method JIT". Just curious, given all these advances in JS speed, are there technical reasons why stuff like Python, Ruby and Perl aren't getting similar improvements in speed?

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.

Comment: Re:...And one generation behind on HTML5 (Score 1) 341

by xiong.chiamiov (#33292842) Attached to: Firefox 4 Will Be One Generation Ahead

Nowhere. But right now it's the most widely adopted and implemented (pretty much everyone but Firefox either does or is planning to support it).

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.

The cost of feathers has risen, even down is up!

Working...