andreamazz

Nothing. Neither with Carthage. The problem is that they rely on the project configuration (Cocoapods requires also an xcode workspace on top of that). It's a bit overkill for just a script.

This is clever. I can also see it being used by street artists.

Without code highlighting though, if I remember correctly. I don't see myself editing a >2MB file containing code, but still...

You should not have deleted all that porn though

To be fair, with Android you never controlled every pixel. You just cross your fingers. Also, what a weird image of jazz this man has on his head...

RIP King of the blues, you'll be truly missed.

I guess that technically it's leaking, not peeing.

> I'm 17 years old and a developer on the app store. The App Store feels opaque and like a black box where I submit builds with little to no feedback or control.

I've been pushing apps on the appstore form day one, there's a lot of room for improvements, but saying that you get no feedback is plain false. When an app is rejected the reasoning behind the refusal is always explained, and you have a chance to talk through the issue (sometimes I had the reviewer calling me on the phone). In the end it's just a matter of following the guidelines.

> Every part of developing for Apple leads me to this conclusion: I do not matter. My app does not matter.

We all like to think we're special, millions of developers do, that's true for the appstore, and the same goes for the open web.

Exactly, I was referring to the singleton stores and dispatcher

It's always nice to read a writeup on Flux. I would love to hear more about possible isomorphic implementation of the architecture though. Right now besides Fluxible the architecture doesn't play well with server side rendering. By the way, shameless plug, I wrote an article on Flux (backed by a Rails API) a while ago, if you're interested on the matter: http://fancypixel.github.io/blog/2015/01/28/react-plus-flux-...

Just to give you an example of the idiocy of our bureaucracy: paying a subscription to the Google Apps (around 3 euros per month per user) is considered like importing physical goods, therefore every 3 months we have to submit a form called 'Intrastat'. Since the bureaucracy is insane you need to pay a professional to handle the madness, so on top of the small Google fee you need to pay an additional ~50 euros every three months. On top of that, the next month you need to submit a form called F24, paying a tax on the 50 euros you just spent for nothing. Oh but the food is great.

I'm italian and one of the founders of an italian startup. Saying that it's hard to work here would be the understatement of the century. The fiscal pressure is insane, the laws are batshit crazy, and there is no startup culture nor respect for the IT in general. Don't get me wrong, I love my country, but founding a startup here is just madness.

Yes, you need a device to test this out. You can emualte a beacon with your Mac (there's a link to the app on the blog post) and that's about it.

Hi, I'm the author of the blog post. We also developed an Android client using the Estimote open source SDK, we're planning to pubblish that on Github as well. Since iBeacon is just a fancy word for saying B4LE, Android devices that ship with Bluetooth 4 chips work just fine.

I really like that design. We developed a similar idea a couple of weeks ago, when we received our Estimote beacons. Here you can find the blog post about it with the sources, albeit it's a simpler and rougher implementation: http://andreamazz.github.io/blog/2014/07/01/fun-with-ibeacon...