|echo 'export PATH=$HOME/local/bin:$PATH' >> ~/.bashrc|
|curl http://nodejs.org/dist/node-latest.tar.gz | tar xz --strip-components=1|
|make install # ok, fine, this step probably takes more than 30 seconds...|
|curl https://www.npmjs.org/install.sh | sh|
|# You don't need Fog in Ruby or some other library to upload to S3 -- shell works perfectly fine|
|# This is how I upload my new Sol Trader builds (http://soltrader.net)|
|# Based on a modified script from here: http://tmont.com/blargh/2014/1/uploading-to-s3-in-bash|
|S3KEY="my aws key"|
|S3SECRET="my aws secret" # pass these in|
I saw you tweet about JSX yesterday. It seemed like the discussion devolved pretty quickly but I wanted to share our experience over the last year. I understand your concerns. I've made similar remarks about JSX. When we started using it Planning Center, I led the charge to write React without it. I don't imagine I'd have much to say that you haven't considered but, if it's helpful, here's a pattern that changed my opinion:
The idea that "React is the V in MVC" is disingenuous. It's a good pitch but, for many of us, it feels like in invitation to repeat our history of coupled views. In practice, React is the V and the C. Dan Abramov describes the division as Smart and Dumb Components. At our office, we call them stateless and container components (view-controllers if we're Flux). The idea is pretty simple: components can't
Recently CSS has got a lot of negativity. But I would like to defend it and show, that with good naming convention CSS works pretty well.
My 3 developers team has just developed React.js application with
7668 lines of CSS (and just 2
During one year of development we had 0 issues with CSS. No refactoring typos, no style leaks, no performance problems, possibly, it is the most stable part of our application.
Here are main principles we use to write CSS for modern (IE11+) browsers:
These instructions work for the Raspberry Pi running Raspbian (hard float) and create a hardware optimized version of NodeJS for the Raspberry PI, (and include a working install and NPM!!!):
Install Raspbian - http://www.raspberrypi.org/downloads
Install the necessary dependecies:
sudo apt-get install git-core build-essential
(If you just installed git then you need to administer your git identity first, else adding the patches below will fail!!!)
(tl;dr DOM builders like [domo][domo] trump HTML templates on the client.)
Like all web developers, I've used a lot of template engines. Like most, I've also written a few of them, some of which even [fit in a tweet].
John's implementation has since evolved and [lives on in Underscore.js][underscore], which means it's the default choice for templating in Backbone.js. And for a while, it's all I would ever use when building a client-side app.
But I can't really see the value in client-side HTML templates anymore.
|# It's important to convert the vbox image (VMDK or VDI or whatever) using|
|# the same version of VirtualBox that created it. You can try converting the image|
|# with qemu-img or kvm-img, but weird version mismatches will possibly make it not|
|# On your VirtualBox machine:|
|VBoxManage clonehd machine.vmdk machine.img --format RAW|
|scp machine.img root@kvm-host:/somewhere|