bengl3rt

So you implement some HTTP API using Cloud Code, and you deploy it. Shouldn't their SDK, through magical synergy, expose the native function to communicate with that API on the device? It seems like I can implement my HTTP API using Cloud Code, but I still have to bring in something like RestKit or ASIHTTPRequest on the device to actually talk to it.

So they have native APIs for talking to their HTTP API, but not the custom ones you implement using cloud code? Their example shows them calling it with curl, rather than "here's how to call this from inside your native app that already uses all the other Parse goodies"

Such is not the case with apps. If you've spent a few hundred dollars on apps over the course of a few years using iOS devices, the cost to switch (assuming you care about continuing to use any of those apps once you're on Android) is pretty high.

My rationale is that I'll only do it for a few years, and it's worth it to have the company in question on my resumé. I think the fact that we all aren't working from home 2-3 days a week is frankly ridiculous, but the sea change is already in progress and can't be stopped. Eventually working remotely 50-80% of the time will be the norm.

Yes! Finally someone gets it!

Motherfucking space! Is aspirational!

We go to space not because it is easy, but because it is hard AND AWESOME.

Also, in a world of politically correct egalitarianism I respect a company that has the literal and figurative balls to stand up and say, nope, this is for men (and go so far as to bake that assumption into the product name)

Shirts are a little different, but I use it for stuff like razor blades that are consumable.

Exactly how I learned as a 10-13 year old: I wasn't writing very much code from scratch, but rather gluing together large swaths of copy/pasted example code from the internet. It was messy and nasty, but by bending other peoples' code to do what I needed I slowly came to understand it.

So, the big news here is that that's no longer required, and that stock Android devices will now be allowed.

http://zserge.bitbucket.org/jsmn.html

-Benglert

In this case I'm thinking of the time just a few months ago when a hose clamp that was misplaced during a cooling system overhaul caused a head-gasket-damaging overheat... which cost $4800 to fix.

I have always been amazed (in a bad way) at the quality of the work done by service departments at luxury and high-end car dealerships. I'm not sure what kind of agreement these independently-owned dealerships have that they're allowed to use the manufacturer's corporate identity to promote their business, but it should be a whole lot stricter.

Conversely, I've never had my laptop receive a shoddy repair at an Apple store - after all, the repair facility is owned and being operated by the same company who built the machine in the first place, so they share common goals and incentives. If Tesla is trying to do for car dealerships and service centers what Apple did for high-tech retail, the privilege of participating would definitely be worth $600/yr to me.

Now, Apple does have a licensing program in place to certify independent repair facilities as "Apple Authorized Service Centers" where warranty work can be performed. I think Tesla would do well to create a similar program, and maybe they plan to! Who knows, it's early days yet.

I mean... they did release a device that's basically just a huge screen...