The command is very very simple: just type
curl -T localfile.ext ftp://username:[email protected]/remotedir/
If you want to use a different destination filename just add it at the end:
curl -T localfile.ext ftp://username:[email protected]/remotedir/remotefile.zip
Charlie Robbins wrote a nice article on how to run your node.js permanently.
Find the full article on nodejitsu.
A small, but effective, guide on how to quickly setup the Android Emulator using the x86 images (not the painfully slow ARM emulation) and GPU.
This step-by-step guide is designed to help app developers and entrepreneurs: understand the variety of ways to monetize apps and develop a pricing strategy that is flexible.
The guide, by Jen Gordon of Smashing Magazine, is freely available at http://www.designboost.net/app-monetization-guide/
Small step-by-step guide on how to install and run Windows 8 Developer Preview under VirtualBox.
Chris Chabot announced the new Google+ APIs:
I’m super excited about how the Google+ project brings the richness and nuance of real life sharing to software, and today we’re announcing our first step towards bringing this to your apps as well by launching the Google+ public data APIs.
The APIs are available at Google+ Platform Developers site, and an introductory article is also available at the Google+ Platform Blog.
Appcelerator’s approach to the Android platform has made another victim, a significant one: 6Wunderkinder’s popular Wunderlist ditched Titanium Mobile (TM) for Android, and is now a native app.
“(…) Wunderlist is now native – smaller, faster and more stable.”
Matthew Bostock, 6Wunderkinder’s blog
Translated, Wunderlist got rid of TM’s biggest problems:
- Size: even the smallest “Hello World” app weights at least 1.5MB (this is still huge in the mobile world – do the same thing using native Java and the app will only weight a few KB);
Appcelerator reacted two days after 6Wunderkinder’s announcement, stating that Titanium Mobile for Android will use, somewhere in the future, google’s V8 engine. This comes, however, with a still significant drawback: only devices running Android 2.2 or newer support android’s NDK, and therefore the natively compiled V8 Engine. According to Appcelerator’s own benchmarks, this will at least double the performance. Remains to be seen if the “Size” problem will be solved: V8′s binaries will still be inside the app’s package…