HNHacker News
TopNewBestAskShowJobs

koko775

990 karma · joined September 27, 2009

submissionscomments
koko775··on On switching to Arch Linux
Those downsides were upsides for me. I love that everything must be configured on Arch, because I know that I am doing all the configuring. I've tried to customize Ubuntu's motd, change services to start backgrounded, and install packages from source in a way that integrates with the packaging system. Ubuntu likes to get in the way of this in the name of simplicity and for a casual or even intermediate user, sure, this works. For advanced users too, depending on your priorities.

Arch is awesome because it's basically FreeBSD-like packaging and something not unlike FreeBSD's service configuration on a Linux box. Things are in a predictable place, rather than in /usr/local OR /usr/, and installing source packages is something that is very customizable and very easy. It yields the responsibility to be careful about your versions to you, but in doing so gives you an immense amount of power to be the master of your system.

For minimal systems, where you know what you're doing, it's fantastic. Running Xorg is a bit of a pain, but I hardly blame Arch, and if something that "just works" were what I was going for, I wouldn't run Arch. I wouldn't use it on my MBP, but it's been running great on my home server for quite some time.

koko775··on I want to fix programming
Sounds like a combination between flow-based programming and declarative programming. Perhaps a possible approach would be to write a flow-based programming language with some methods marked as "pure" which statelessly map input to output and others able to be written in a more traditional, imperative, less functional style?

In a flow-based architecture, it seems to me that by design, almost every component in the flow would be testable.

koko775··on Request for Startups: Kill Hollywood.
As an engineer working at a startup that is actively challenging the entertainment status quo through a slightly non-traditional vector, this RFS strikes me as amazingly naive and lacks any realistic suggestion for what kind of challenges might be most effective.

Hollywood isn't dying, nor is it anywhere close. Shedding some excess, maybe, but not dying. It's an overweight person rationalizing away his weight problem instead of committing himself fully to do whatever it takes to become lean and efficient. Apologies if that offends; I don't mean any malice. I simply mean to point out that even without Hollywood, there are any number of entertainment pieces constantly being produced and distributed. Indeed, Hollywood is, in my opinion, little more than a destination and mini-society that brings together and publishes works, as well as an ecosystem of funding. Try finding an animated movie that truly, terribly falls flat like some films. It'll be harder than it would be for a fully live-action film, because they know that without star power or explosions as a fallback, that much more effort needs to be spent on narrative to produce something that, if nothing else, will not tank incredibly. Is it any wonder that the animated versions of large or popular franchises typically have terrible movie productions†?

(† in this case I am also including live action movies with a very major animated component, i.e. a mix of live-action and animated characters)

The people who build the technological platforms hosting today's entertainment are, by and large, not dumb people. It takes some real skill to scale a site that serves up any number of combinations of video profiles and different target platforms. This, especially, is somewhere the cloud has trouble with cost-effectiveness. Video loads are large, and can be CPU, RAM, and I/O bound (if you're trying to make the most of your resources), and iteration and improvement on the process can take hours or days, not simply minutes, for almost-imperceptible but possibly still important improvements. There are reasons it works for Netflix and reasons that it's more expensive for smaller companies to scale. There's also the fact that DRM is often a contractual obligation, and the start-up costs can run well into the several hundreds of thousands of dollars range, not including high upkeep contributing to a gargantuan TCO by any startup's standards. Then there's the revenue sharing, of course.

The problem is not technology, or throwing more startups at the problem. The innovation must come from hacking the business side, or altering the deal with how content providers bring their content to the masses. Building more technology without doing this will waste people's lives and embitter them, because entertainment is being held back not by the available channels to get it to you, but because taking risks and failing fast nets you a blacklist from the people licensing you the content. Put another way, the content providers are choking off new media, not the actual proponents of new media. The pipeline of people making a living off of this stuff leads into hollywood and anything that can be done to divert them away from that walled garden and into a content bazaar will do more to kill Hollywood than actually targeting Hollywood ever will.

The solution, in my opinion, is to empower the entertainers and the content producers to reach their audience more directly, more broadly, and with more engagement than a TV or, let's say, a comic book will ever be able to give you. As a medium for entertainment production, YouTube falls flat. It's not the product online entertainment wants to be. It's not a product designed for simulcasts, and it's not a product designed for building communities, or for social watching, or for alternative media formats, or for worldwide publishing with subtitles of customizable language or styles, with pre-roll, mid-roll, or post-roll ads, or for subscription-based monetization. And even if some of these exist separately, they're not all in one place.

Also, large video ad tech is fucking terrible and poorly specified, except for Hulu, which has full access to its own tech, which it doesn't license out, as it runs its own in-house ad network. Ad companies tend to have shitty engineers or get bought by Google. But Admob's video ads monetize poorly compared to the other (technically worse) options, surprisingly.

koko775··on Why I'm a Pirate
This argument evaporates when you consider services that offer all-you-can-eat for a flat monthly fee.

If you only have to pay the price of one day's lunch for access to a library of content, then downloading a title rather than watching it on its official outlet will reduce subscription fees and thus impact revenue sharing. So rather than buying less than 10%, there may in fact be no threshold at which pirating becomes more practical, once the initial monetary threshold (being able to afford the subscription fee) is met.

Therefore, copyright infringement can result in a much stronger loss in revenue than you presume, even though I personally agree that it doesn't constitute "stealing", as no physical good has been removed and appropriated illegally. However, what that copyright infringement can do is impede or obstruct certain consumer-favoring (IMO) business models from being viable.

It's possibly true, in my opinion, that sharing in a gray area of material whose market has not yet matured may increase visibility and have future benefits, but no company which deals with content producers and the platform to deliver content can afford to acknowledge this to the content producers or to the audience without risking legitimizing copyright infringement and therefore delegitimizing their own business (which is why I'm not disclaiming where I work, other than it is familiar with these issues).

Not that I'm arguing that there should be no such thing as sharing, but making the moral argument to justify it that stealing isn't putting the company in a worse position is a poor rationale. It's not true and it's not something that can be defended against in public.

Nor am I arguing that piracy will make or break a business. If it's big enough to be popular, it may be big enough to grow a legitimate market faster than the illegitimate alternative. However, this also relies on cooperative content producers and an audience willing to pay for the content. It's a tricky balance but the reality is that while violation of copyright may not produce economic devastation on its own, neither is it devoid of any impact.

tl;dr: Reasonable people should pay for content available to them that they enjoy, especially when affordable.

koko775··on Expecting more from Yelp
Precisely.
koko775··on Expecting more from Yelp
So I take it you've never tried Ness (http://www.likeness.com/)?

* Ratings don't need reviews

* Personalizes like Netflix

* Shiny mobile app

(Disclaimer: The CEO is a good friend of mine)

koko775··on New York vs San Francisco in fight for tech start-ups
I live in Berkeley and work in SF. To make this work you'll probably want to live near the BART and work somewhere on Market, or if you're OK with a little more transit time, in SoMa.

BART from Downtown Berkeley to Montgomery Street is 20 minutes in ideal conditions, but around 30 more typically due to waiting or a transfer at MacArthur. Expect to add to that 5-10 minutes for somewhere on Market and 10-15 minutes for somewhere in SoMa

koko775··on HP to Contribute webOS to Open Source
And would never happen. Oracle has a huge vested interest in controlling arguably the most successful universal language and vm platform in the world.

As fantastic as it would be for it to happen, imagining a multibillion dollar company managed like Oracle giving away that much value for free isn't just wishful thinking, it's delusional.

koko775··on Standing Up For Android
Oh, no, it's on an entirely different level. You not only have to deal with elastic screen size, you also can't tweak to pixel-perfection nearly so easily as you can with iOS. If this were all that was wrong, Android would be better. However, due to fragmentation, any app with nontrivial data parsing/caching/display requirements that wants to be both widely usable as well as robust and stable needs to (in my experience):

1) Use the compatibility library for lazy-loading and easy reloading of data via CursorLoaders and SimpleCursorAdapter. This means mostly abandoning ArrayAdapter (it can easily cause eternal garbage collection if your dataset is slightly too object-heavy), assuming your data is mostly expressed in rows in the SQLite database.

2) Use Content Providers, as this is the only simple way to make the CursorLoaders work. Lots of boilerplate and semantics to accidentally get wrong, and URI overhead that you really don't give a damn about.

3) Either use a service or something resembling one that's initialized in Application#onCreate() to make API calls that store into the database (having them run inside an activity can cause nasty bugs if you're not careful as AsyncTasks are unceremoniously killed when rotation causes the activity to be killed and recreated)

I'd have to say as a developer of both iOS and Android, iOS is way, way more flexible, and gives you better APIs, and frees your mind to work on interesting problems. Android has too many development dead-ends that are easy to waste time on, and an irritatingly slow build process, if you want to ensure your build doesn't have any bad information from dirty caches that failed to clean. I can't say how many times I switched git branches only to find images and color resources still stuck on old values, even when I was exporting to deploy the apk.

tl;dr: Even if Android is worth developing for, it's still a time suck because a lot of little things cause problems. Nowhere is it made more clear that simplicity requires complexity than in the comparison between iOS and Android, because Android shoves all of that complexity in your face with not a whole lot in terms of guidance to guide the way. Meanwhile, Apple's documentation is world-class.

EDIT: not to mention different devices appearing differently because of stupid default themes, the lack of a stable image loader service that doesn't cause memory and application response issues at volume, crashing inexplicably because some bitmap refused to decode, random devices with non-compliant h.264 decoders failing on perfectly valid videos - randomly during successful playback, too! - vocal commenters/raters using extremely old devices complaining about the lack of support, occasionally nondeterministic state preservation when paging out views/activities, and a fuckton of other shit that's annoying as hell.

koko775··on Stop being so productive
I've long known that excessive context switching dampens my productivity, but how else am I supposed to take my job seriously and give my side projects a shot? :/
koko775··on Sergey Brin gives $500,000 to help Wikipedia
> - A lack of respect for the customer and an attempt to maximize profit at the expense of their enjoyment of your product. I do not subscribe to Hulu for this reason.

As someone who works for a different video streaming site (that also has legal content licenses), your ire may be misplaced. Rather than a lack of respect for the customer there's a very likely possibility that the ads must be shown, even for subscribers, due to licensing agreements.

koko775··on Jack Dorsey does 8 hours at Twitter, 8 hours at Square daily
Well...VenMo is competition and waives the transaction fee - so there's definitely competition there.

I still think Square is superior, though.

koko775··on Google TV, Take 2: Android Apps now on Smart TVs
I developed one of the featured TV apps. I think licensing is indeed one of the sticky points. One key point is that a lot of licensors may require DRM in their licensing terms. Google has a lot of room to grow in this area, and certainly will over the next year. Support for HLS is also another biggie, as it's not a POS like RTMP nor is it trivially copied like progressive download.
koko775··on Steve's Google Platform rant
So this is somewhat related, somewhat off topic from the subject at hand, but... ----

As for bringing content owners on board - as far as I can tell, they did. Their developer support was also very responsive. A+ on forming a dialogue with developers.

Their problem IMO is that they don't appear to feel it in their bones how important product differentiation is. Maybe they get it, but I don't think it's sunk in.

Allow me to elaborate. What's the difference between an embedded device, a phone, a mini-tablet, a tablet, and GoogleTV? Well...

* Embedded devices might have a pre-2.x Android that never got updated. But that's okay, nobody develops apps for them anyways.

* Phones probably have 2.1, maybe 2.2.

* A mini-tablet could be 2.1 or 2.2, and has the mobile device UI.

* A tablet might have 3.0 or 3.1 on it.

* GoogleTV has 3.0 on it, but its market app might filter like it's 3.1. How do you differentiate this in code? Version specifiers, specifying notouch (which will break if googletv ever supports any kind of touchscreen, on a large screen size (which is smaller than a tablet, which has a extra large screen), etc.

Want to develop for iOS? Great. Would you like iPhone or iPad? Or both? Need to make sure it works on 99.9% of the devices that can download it? No problem. And hopefully, sometime in the future, maybe Apple will see fit to enable the AppleTV for developers.

Circling back to address your statements, if Google's aim, or one of them, is to make GoogleTV into a gaming platform, I don't have much confidence in Google's ability to deliver on that goal, because GoogleTV is little more than a revision of Android plus some optional APIs, and Android is architected as a multi-device platform. It's not a single device with multiple revisions, as is the case with the iPhone 3G/3GS/4/4S sequence, or even the Nintendo DS and its subsequent revisions. There are reasons that Android isn't as compelling a game platform as iOS is, and that is a big one.

With respect to building a multimedia application platform, GoogleTV has potential if for no other reason than it's one of the few set-top boxes with an app store, period, and a programming interface that isn't thoroughly obtuse, but the GTV's design and usability are very weak, almost pre-alpha, even, as if it were scarcely more than a straight-up port of Android's touch-optimized interface with an inadequate amount of polish. It's nothing your average TV-watching user is going to grok, if the keyboard+mouse remote didn't clue you in.

Really, what it comes down to is that, even for hardware, Google just doesn't seem to want to release something "perfect". They just want "shippable" -- or I daresay "just barely shippable" - if you can call it that. Even if they have critical bugs, so long as developers can work around them, even if they haven't nailed down the UI, and make a sweeping change right before public release, that's still "good enough". And "good enough" is the enemy of "great".

Until Google puts design thinking into their products from the ground up, as you put it, they aren't going to be able to lead the marketplace.

/rant

koko775··on Richard Stallman on Steve Jobs
Well, more accurately, Safari was born from KHTML. WebKit was Apple's massive retooling of it, and was widely acknowledged as superior to KHTML (someone correct me if I'm wrong) and in time replaced it. However, your point isn't necessarily invalidated, as iirc the changes were simply dumped in one large mass rather than as patches.

Additionally, OS X was created from NeXTSTEP, which - again, if I recall correctly - was built on a licensed, proprietary UNIX, so claiming that using BSD for the underlying system in some way took something away or co-opted it, as opposed to made use of it as the license allowed, seems slightly inaccurate.

That said, while I am a big fan of Apple's APIs I am astoundingly opposed to the App Store's walled garden - I surprise even myself, a self-professed fan of many things Apple - with the complete and utter disdain with which I view the terms of the App Store. It really is a jail, and it's a huge problem for the company I work at. Other than the BS about how some of our content might offend sensibilities according to some nebulous standard of western values (disclosure: I work at a company that streams anime), the policies applied seem to do little else than stifle competition.

tangent:

With Siri, I see something bad as well. It seems that controlling the user experience of search - the user experience, the anointed services - leads down a path where it is not the search providers with the best results or presentation which win, but the one which Apple anoints with their approval. Apple seems to think that producing the device entitles them to applying rules which enable Apple to step in and compete with an advantage on things which are not their core competencies. I think this is dangerously close to anti-trust territory, in which a monopoly (not bad by itself) could be abused to foster anti-competitive acts.

/tangent

koko775··on The Best Science Fiction Books (According to Reddit)
I'm surprised that there's only one mention. It is an engaging and very fascinating read which explores some of the fundamental aspects of transhumanism.
koko775··on The Sad Reality of Post-Mature Optimization
Note: "the guy" is Jonathan Blow, who created Braid.
koko775··on A few days of programming on iOS and Android illustrates a vast difference.
Google provides an ImageLoader library. It kinda sucks, and occasionally causes Application Not Responding errors or out-f-memory exceptions in my company's apps, but there's nothing better that's open-source. I wrote something pretty cool at my previous job that unfortunately probably will never be open-sourced that pipelined and cached image fetching, and supported a responder-chain like pattern for handling the images, as well as decoding it to a limited size rather than fully decoding into a full-sized bitmap and then resizing, as that would occasionally fail due to the bitmap decoder deciding to return null sometimes - probably in low-memory cases.
koko775··on An iOS Developer Takes on Android
The more you know:

UIViews are basically event-handling abstractions above CALayers, which in turn are a relatively thin abstraction above common OpenGL actions. Core Animation simply manipulates these layers in the hierarchy, of which there are three per view: model, presentation, and render. The model is the one you interact with. When you change the location of a view, it changes the model, which is then reflected in the presentation. When you animate, it tweens from the beginning state to the end state. Fun fact: when you start a new animation and start it from the current screen state, it uses the presentation layer, instead of the model layer. If you don't start the animation from the current state, this is why you might see jerking - it tweens from the model layer instead of the presentation layer.

The render layer, the last of the three, is rendered by the render server, which is hardware accelerated, and shown to you. Fun fact: CALayer's renderInContext runs on the CPU, whereas UIGetScreenImage uses the render server, which is why it's so much faster - it runs on the GPU.

koko775··on A few days of programming on iOS and Android illustrates a vast difference.
No, there are methods and settings that can be set via code that cannot be set via the XML, and vice-versa - I'm not talking about mixing them together. Yes, they are the same classes. No, they are not created and instantiated and configured in exactly the same fashion; there are occasionally differences.
koko775··on A few days of programming on iOS and Android illustrates a vast difference.
Moreover, Interface Builder's file format is quite literally a serialized version of the class constructed at runtime, as configured in Interface Builder. What can be done in IB can also be done in code, which is more than I can say for Android's xml.
koko775··on A few days of programming on iOS and Android illustrates a vast difference.
Agreed on all counts. As for the backgrounding stuff, though, don't worry too much, as with a local binder, services become little more than classes running in the background. The ickiness from all that AIDL stuff I've found to not be particularly necessary, as you won't have other applications needing to access your service, typically. Exporting content providers to other apps doesn't seem to be particularly useful, anyways, unless you're Facebook or OEM, where apps might reasonably expect to find the content provider or service they're looking for.
koko775··on A few days of programming on iOS and Android illustrates a vast difference.
You're high on the post-development rush. It's addicting. But it doesn't mean the platform will scale with you. I've done extensive iOS and Android development (more extensive on the Android side due to business necessity). Here's some gotchas that I've encountered, from memory, because these are only the recent ones (plus one or two memorable ones from way back).

EDIT: Disclosure - I am one of the rare types who is actually a big fan of both Java and Objective-C's syntax, though I'm more partial to Scala's approach than Java's, overall. I view Objective-C, conceptually, as somewhat in between C and Python, with good parts from both (though of course ObjC is far older)

Example #1:

I made the mistake of using ArrayAdapters, and hand-writing my own wrappers around the android sqlite libraries to manage my app's data. What did it get me? Garbage collection cycles that crashed the app, among other things.

Example #2:

I am of the opinion that in order to build a stable, robust app, Content Providers, at the very least, are required (for many reasons, the primary one currently being the ability to use LoaderManagers and CursorLoaders). But where was the documentation that explained why this was so? The complete lack of a centralized, high-level overview of Android systems have lead me to several development dead-ends, resulting in rewrites. While I'm wiser for the effort, and have finally settled on a sane, reusable, fairly general pattern for data-driven Android apps, I used up some really valuable development time finding this out. And you know what? Looking at the codebase before my (just-deployed) rewrite, and looking at the Android codebase at the job I left before it, everyone is making these same mistakes, and not many are realizing it until later.

Aside - Rant:

BaseColumns (http://developer.android.com/reference/android/provider/Base...) has no discernible use other than for a class to inherit some static variables. This is kind of ridiculous, as there's no requirement to use the column constants anyways, and they're static. I use enums instead, for each database table. Works much better. At my last job I even wrote an automatic SQL create statement generator for use in onUpgrade(). Oh, and if you want to use anything other than _id for the column name for your objects' unique IDs, you're not going to have an easy time with automatically binding your database objects to your UI.

Example #3:

Lots of stuff requires contexts. Against your common sense, you should try to avoid supplying the current activity as a context when you can use the application context instead. Why? Because if an Activity, which is a context, is retained as a member variable in something - perhaps a class that is, itself, a member variable of the aforementioned Activity, voila! You've got a circular reference and a potential memory leak! Where was this in the documentation? Nowhere. It was in a blog post that isn't exactly on most people's radar: http://android-developers.blogspot.com/2009/01/avoiding-memo...

Example #4:

Changing orientation destroys and recreates an Activity. Did a AsyncTask run at an inconvenient time? Oops. Chances are you're going to crash if you needed to do anything special with your Activity's state.

Example #5:

Using Apache's HTTP client? Careful. Don't use RequestWrapper, because executing a POST request wrapped in one can cause it to drop headers from the request. Just use different methods for HttpGet and HttpPost, and add on (for example) authentication parameters, device model names, other info for metrics, etc. separately for each. Funny thing is, I had better luck duplicating code for GET/POST here than reusing it, which I found disgusting, because duplicating code is not a good solution to anything, but it just got the work done.

Example #6:

I've gotten unreasonable Cursor closings that weren't my fault because someone at Motorola thought they were being clever and closing Cursors in a finalize() method was somehow a good idea: http://stackoverflow.com/questions/6552405/android-compatibi...

TL;DR (my main argument):

Android has many avoidable gotchas that require a solid programmer to identify and work around, but which aren't immediately fatal if ignored. Android provides a lot of infrastructure, and some of it is even good! Despite its mess of poorly-written, poorly-documented, or incorrect APIs, it manages to allow decent programmers to write pretty decent solutions and some pretty robust code. But it does a damn piss-poor job of documenting its wrongness when it rears its ugly head, and it fails to make clear that while there's freedom to do things many ways in Android, there are really only a few ways to do them well.

Rant #2:

All android devices seem to suffer from gross over-logging, some far more than others, like Motorola, or some newer HTC phones., which is a huge pain in the ass when I'm just concerned with my own error logs, and not spurious calls to the logger that the software author or device manufacturer forgot to or didn't care enough to elide.

Rant #3 (emphatically):

The worst and most fundamental flaw with it, though, IMO, is that the classes for the views and the serialization format representing them (the layout xml's) do not have anything even close to a 1:1 mapping. Serializing a class - it's not that hard. iOS does it by literally serializing the state of the view objects as configured in Interface Builder into what was once a binary file, but now is an XML file (nib, xib). Anything you can initialize or style or otherwise edit to affect the initial state of a view in interface builder or (were it reasonable) another method of directly editing the serialized representation you can also do in code. Not so in Android.

Here's a link to a post of mine last month that addresses some more gripes with Android: http://news.ycombinator.com/item?id=2737284

P.S. I've talked to Bob Lee (of Square; former core library lead of Android) about this before. Even he agreed that Android's APIs were poorly thought-out and designed in places. That's pretty damning right there.

koko775··on What Happened to the Future?
Shallow social connections have earned me two jobs and a number of deep social connections by leapfrogging off of shallow social connections.

If you think there's no value in maintaining shallow social connections, then I think you too need to put some energy into adding meaning to your social connections.

koko775··on Android takes huge lead in US Smartphone market
To be clear, the NDK will probably remain supported and first-class on mobile devices. Given that I have an NDA for the current Android device I'm targeting, I can't say anything really specific about it, only that the NDK is not designed to work with it (though it would appear that it does support JNI). So I wouldn't discount Unity necessarily.

I have half a mind to just write up a new UI framework in OpenGL or something, and use it as a vehicle to learn OpenGL better, but I don't have the time or the money to do so, and ultimately I can worth with the stuff that's already there, albeit with constant frustration and platform angst.

koko775··on Android takes huge lead in US Smartphone market
Ha. You don't know how good you have it. On Android:

* Certain devices decode h.264 wrong and crash, others don't, and it's hard to reproduce and virtually impossible to test

* No, there is no Android device dominating the others. Not even close. Program to API 7 or API 8 if you must, but the whole thing's a headache.

* No expectations for resolution

* This freaking bug (ARGH!!!!!!): http://code.google.com/p/android/issues/detail?id=1353

* Everything is sized relatively, but the only way to size to a % of the screen (that I've found) is to pad a view with empty views with different weights, and set the middle view to 0dp (density-independent pixels, which, because of some manufacturers' lies and trickery, aren't always density-independent) tall, and have it resize later. But wait! Setting it to 0dp messes up other aspects of resizing!

* The order of operations that Android goes through to resolve layouts, if it's even logical, is incredibly opaque, and at the very least, not at all intuitive. For example, denoting a view "A" to be above another view, let's call it "B", is not the same as denoting view "B" to be below view "A". Now try that with four views, arranged in a T formation. Hellish! And good luck trying to resize an image to clamp its left, top, and right edges to the screen, and crop it at the bottom - it won't work unless you clamp only a corner (i.e. top and left) then have it resize to fill the third clamped dimension, that is unless you're using other special tactics to mess around with other parts of your layout, in which case you'll waste a LOT of time finding the right answer, or one good enough to use.

* The concept of resource overlays in Android is a huge, huge, huge pain in the ass. Possibly necessary given the complete fragmentation of the devices.

* Devices will actually lie to you about their screen dpi/resolution because they think it'll be better

* Some devices might have bad defaults, or not allow you to select a button without tapping it (i.e. with a directional pad) while others will.

* Weak-linking and adding in checks for future functionality is not possible, to my knowledge, on Android. Adding in support for Honeycomb features entails actually not supporting them directly, but proxying them through a compatibility library.

* The error-checking for XML layouts and themes is weak.

* XML layouts and creating views in the equivalent of a view controller is entirely different and the mapping is not 1:1. Combining the approaches piecemeal complicates the whole process enormously.

* Asynchronous data can only really be loaded one way without causing lower-end devices to crash on large datasets, and that is with the whole cursor/content provider ecosystem, which is a poor excuse of an abstraction given Java's power.

* Parsing stuff tends to be dog-slow unless you spend an inordinate amount of time paying attention to it.

* Certain upcoming platforms running Android - and developed by Google itself - don't even support the NDK, which means you can't even dip into C/C++ for performance anymore for said platform.

God, I miss developing on iOS. It's too bad our app got rejected for using In-App Subscriptions, then rejected for not using In-App Subscriptions.

koko775··on Massive Indestructible Botnet
Seriously? Nobody's read Accelerando? :(
koko775··on Massive Indestructible Botnet
Next thing you know it'll be asking to be uploaded onto a mining colony on some asteroid!
koko775··on AWS drops bandwidth pricing
I suggest using prgmr.com instead. $6/mo is worth a Xen instance with IPv6 and everything.
koko775··on Designing GitHub for Mac
Holy crap, yes. This was incredibly alarming. SSH keys are far and away more secure than username/password. I would be far more comfortable if it were possible to use GitHub with nothing but my SSH key. The ability to create a passcode-secured key is vital to me, because the keys and the passcodes have to be stolen to be useful at all.

And if you use ssh-agent, I'm pretty sure it doesn't even send your private key; SSH creates a challenge that your key is used to compute, so even someone eavesdropping with a keylogger on the server won't be able to sniff your password.

← PreviousPage 8 of 10Next →