Android does distribute the GPL portion early, they don't do that for the non-GPL real Android stuff.

Subtitle support was already great back in $a_date_long_ago_in_computer_years. Dunno what 2.0 improves on, fluff support was already pretty good, probably it's about doing that on soft subs.

Anyway, the thing with anime fansub subtitles is that they go beyond normal subtitling, adding karaoke with characters(and images) glowing, fading, changing colors and jumping around the screen; typesetting floating objects translations right into a precise place in a timed frame, along resizing, translating and rotating that object if the background image requires it.

It usually isn't that bad, but then Akiyuki Shinbo happens.

I believe there's a market for each product, but they should be categorized strictly:

• - Up to 3.5 inches is for people who want a classic cellphone, for calls, messaging, agenda, etc.
• - 3.5 to 4.7 inches is for handheld internet browsing, heavy touchscreen app users who still want a cellphone.
• - 5.3" is the electronic notepad category, to be used with stylus pens for making small notes and drawings, for users who also want the above capabilities.
• - 6 to 7" is the reader category, for extended, still, handheld, reading of books. They should be extremely light for their size, 300 grams at most, which pretty much only e-Ink readers can deliver that.
• - 7 to 10" is the tablet computer category, for touch screen app users, small presentations, business substitute for reports and documents, ~600 grams at most.

Anything north from that is not intended for handheld usage.

Read the chart above as "You will be uncomfortable if you use X to do Y."

Please correct me if I'm wrong in this analogy, Are _KDE_ Frameworks 5.0 is to QT the same as _Apache_'s many frameworks are to the Java SE/EE platforms? Really no major coupling at all?

I expect Apple stakeholders to be crying out in terror by tomorrow. I'm amused how he did that right after the market closed.

Since current Java SE code isn't expected to run and have the very same behavior in Android without modification in previous versions, I don't think it the current version would be any different. BTW, are Android developers considered to be Java developers by Oracle?

Robot tries to copy move, gets out-FALCON PAWNCHED by the original.

The issue is about cheating, Blizzard cannot verify if during your offline quests you didn't cheat, sou you can't go online with the same character and play with other players under the same rules.

The answer is simple, when you want to play offline, you can either start anew, or load a copy of your online character in cache in your computer. The Battle.net version of the character and its progress will remain frozen. When you choose to play online, you just continue with this online version; offline "tainted" characters won't ever be able to play in Battle.net.

This way you can have multiple "saved games" offline.

Well, bsnes is actually libsnes + qt gui(perhaps qt also handles the input, dunno), so you can easily build another UI as the emulation part is externalized.

Usually when one asks if language X has pointers, the person wants to know if it can do pointer arithmetic, and that's a resound NO in JVM based languages. Which is why we say Java has references, not pointers.

Yeah, they might also be able to perfectly predict earthquakes, tsunamis, gamma ray bursts and sudden influx of users in your site/internet-based product.

Yeah, they are dolphins wearing swimming masks, from Super Mario World: http://www.youtube.com/watch?v=W94OrZU4-aw&t=428

Yeah, ARIN should take all the unused blocks back, that would give us a lot of more time to complete the transition. Another two months should be enough, right? Right?

I've been paying my bills for 3 years developing in Java, and many more years programming at all, I don't know if this counts as an expert analysis or not, I don't care.

• Examining Exhibit J, I believe the Android implementation was copy-pasted from Sun's. In fact, it was a pretty lousy, newbie-ish job trying to mask it.
  Just looking at the bad parameters and local variable names makes me want to punch the idiot who named them. And what's with all the magic numbers hard-coded? On the other hand, I praise the Sun developers for their implementation.
  About the iteration structures, I also prefer using the for iterator instead of a while structure, it makes more sense when you want to scope the variable. Unfortunately the structure becomes a bit top-heavy with all the inlining.
• Examining Exhibit I, I'd first ask what is the problem. API documentations should be one and the same, it's a standardization FFS! The only strange thing I find with that Javadoc, is why java.security.Security is a java class, and not a java interface.

You could argue that the class design is really trivial, and how two different implementation could be identical under the KISS principle, but it's really hard to believe it's a clean room implementation. It's a bastardized version of Sun's code.

From TFA: