3 ms·
From the title I was expecting the RPi to be permanently inserted inside the Transformer somehow. Being at the mercy of the vagaries of 3G reception / public wi
by mooism2 14y ago
From the title I was expecting the RPi to be permanently inserted inside the Transformer somehow. Being at the mercy of the vagaries of 3G reception / public wifi provision is the sort of thing that puts me off doing this kind of thing myself.
Why an RPi as the backend though? Why not something that will compile your code faster? I recognise that not everyone is comfortable with renting a virtual server, but if you're going to leave your MacBook at home, can't you ssh into that?
- qznc 14y agoThe backend question is a big one and I agree that an RPi seems to be a poor choice. Samuel Stern has a MacBook Pro, which has much more power, single-thread and multi-threaded. Nevertheless it probably consumes much more energy than the RPi. Other people rent some server, e.g. Matt Might uses Linode [0], but something like $20 per month flat is really expensive, if you would use it rarely and not for business. Maybe Amazon EC2? Though I doubt it fits the use case of weekend use plus one or two hours per week day. [0] http://matt.might.usesthis.com/ http://matt.might.usesthis.com/
- stinos 14y agogood point here. I'd either ssh into the macbook or attach the Pi to the back of the Transformer screen and also power it from the transformer.
- habosa 14y agoI wanted my "backend" to be always-on, power efficient, and powerful when headless. The MacBook wasn't a good option because I often close it or leave it uncharged, and OS X doesn't have as many command line tools available as Debian or other Linux distros. It's also a huge waste of power to use the MBP as a server, whereas the RPi sips power from a cellphone charger. I could have also used an EC2 Micro instance or a Linode, but those are both much more expensive than an RPi for something I don't even use every day.