Since later point releases of 0.8 line (don't remember exactly) Node.js compiles on ARM out of the box. I think node.js is a great fit here, since it's a high level environment that is comparatively light on resources. Also, 0.6.x is available as debian package for ARM, but some cool things (such as connect-assets) need 0.8.
I myself have a Hackberry board (beffier and more expensive than Pi), and use it as sort of junk drawer of a home/download/communication automation server - runs headless version of Debian and bunch of small applications.
Also, automating the setup of the whole thing made the whole experience much more pleasant. I myself used Sprinkle - you can check it out here https://github.com/tmikoss/hackberry
I bought an Edimax N USB wifi adapter for my raspberry on amazon. It was like $11 and works out of the box with raspian. Now the damn thing boots and connects to my network faster than I can enter my 25 char password on my primary machine.
> since it's a high level environment that is comparatively light on resources
Just an FYI, but Node.js needs to load the V8 engine for each process. So each process is at least 10MB, which compared to pretty much every other language, is pretty heavy.
Not entirely sure, but it is possible that V8 is dynamically linked, and thus you would only get the 10MB hit once. Any experts around to confirm or deny that?
In the other hand, due to Node.js' asynchronous nature, single process (thread) can serve big number of simultaneous clients, assuming the code is non-blocking.
Raspberry Pi seems ideal for people who want to build Linux from scratch, including tinkering and compiling kernels - the known set of hardware and number of people running it helps. With a bit of luck this might help filter people into low level development. (Until they get yelled at for making a mistake or having a different opinion or having a child.)
Some of the projects look amazing, and could potentially get picked up commercially:
Not sure why, but Chrome/Safari are misinterpreting this gzip as a file, thus forcing a download (and there's no Content-Disposition header that I can see). Anyone else experiencing this?
I really like the idea of a portable web server - with a WiFi dongle (better yet, a 3/4G dongle) and dynamic DNS it should be possible to carry the a piece of the internet in one's pocket!
28 comments
[ 2.4 ms ] story [ 67.2 ms ] threadI myself have a Hackberry board (beffier and more expensive than Pi), and use it as sort of junk drawer of a home/download/communication automation server - runs headless version of Debian and bunch of small applications.
Also, automating the setup of the whole thing made the whole experience much more pleasant. I myself used Sprinkle - you can check it out here https://github.com/tmikoss/hackberry
Just an FYI, but Node.js needs to load the V8 engine for each process. So each process is at least 10MB, which compared to pretty much every other language, is pretty heavy.
Some of the projects look amazing, and could potentially get picked up commercially:
(http://hackaday.com/2012/11/01/one-button-audiobook-player-m...)
Audible should look into a vision-impaired friendly hardware player for audio books.
> http://www.loc.gov/nls/reference/factsheets/readingdisabilit...
From here I found a list of many of the devices specifically intended for use by people with disabilities:
> http://www.daisy.org/tools/hplayback
Could be some Nginx config somewhere, had to install quite a lot of caching quick when this got on the front page :)
Can you have another check?
Disable/Enabled W3Cache, cleared out Memcache and it looks to be working now, not that technical but got the job done :)
Its pretty neat to be able to build onboard as well .. just having a compiler onboard means so much, in terms of power and functionality.