zombielifestyle's comments

I agree with OP, although I think the code example is misleading (but still awful).

Why? Configuration/Bootstrapping is needed, with simple, small and loosely coupled components even more, because you don't want to tie a some configuration monster to it. But it would indeed turn out to be a simpler configuration, usually a nice little array with few keys bootstraps any simple component nicely. On framework level it can be more DRY. Downside, every "framework" solves bootstrapping and configuration on it's own. Which would me make always feel bad about running multiple frameworks side by side.

For components (objects) configuration we could solve a lot of problems if the php community could agree about an plain array configuration protocol to set them up. At least it would be interesting if it's doable.

bigger version: http://i.imgur.com/YAlPH.jpg

bytecode caches (like APC) store the bytecode on the fly in memory. you can't create somthing like a "binary" file.

edit: at least they're not intended to create "binaries". you can probably mess around with APC and make php look and behave like a compiled language. but you won't gain any notable speed improvements beyond the on the fly caching.

edit2: you can store php projects in a jar like file, caller phar. http://php.net/phar

Didn't think of that, pretty obvious now. ty :)

* traits is a concept explored in smalltalk. surely the greates monkey patchers among us.

* array? yeah, it's called like that. it could even be named "fridge" or "smartass".

* due to the new release process php BC is guaranteed for non major versions. adaption will be fast.

* thriving ecosystems don't matter, PHP is just one possible piece in the toolchain.

Closure::bindTo gives a nice js-like feeling, but i wonder why the hell a invocation of a closure in a class member triggers a warning.

i can't manage fb to share location information from friend accounts. if 2 accounts upload an (similar) image including one active check-in fb only suggests locations based on the check-ins of that active account. this is even true for public images.

until someone provides a POC that states the opposite it's just YOUR data that YOU freely give to fb. no magic behind, just FUD.

responded to top post for karmawhoring. http://news.ycombinator.com/item?id=3377267

fb don't even matches the check-in of my fake wife at hollywood walk of fame to an pic of it uploaded by me.

I've tried it. i don't use fb for pics. i don't use wifi on my smartphone and i had the fb app only briefly installed. i also weren't on any trips outside my city.

I've uploaded 4 screenshot-ed landscape (including one building) pics from flicker with absolutely no metadata. at least 2 of them should be very recognizable. the only thing that fb suggested was the single check-in that i had, minimum of 500km off.

i'm pretty sure that there is only minimal (if any) intelligence on image recognition and that they guess locations by information that "leak" from you and your hardware.

The old script works better form me. Less false positives and rather stable results.

I have largely varying results in FF9.

The idea is interesting but, considering that the performance of the client (-box) can affect the results, it doesn't feel very viable.

What about DNS cache probing? Is it possible? I guess it will suffer from similar results but at smaller scale.

Galaxy S, Telekom / Germany is clean!