NetBSD 7 gained support for hardware acceleration on the Raspberry Pi last January, and OMXPlayer was ubsequently imported into Pkgsrc. This combination allows seamless video playback directly in console.
Last week-end, I was finally able to dedicate some free time to play a little bit with the Raspberry Pi again, so I decided to plug it on my TV and try RISC OS Open using the prebuilt RISC OS Pi (RC14) SD card image.
In fact, I already had a brief encounter with RISC OS running on Acorn hardware (most likely a Risc PC) a while ago at a French demoparty in the late nineties. I’m not sure how popular those machines were in the UK, but in France, it was as exotic as it can get.
Here is a screenshot showing the desktop running a few applications : BBC Basic, StrongEd text editor, and the NetSurf Web browser pointed at my ASCii and ANSi Gallery :
This capture was taken using Snapper and converted from sprite to PNG using ConvImgs.
As a rule of thumb, an application server should never face the Internet directly, unless of course Nginx (or OpenResty) is being used as such. This is not only for performance reasons, although this is not much of a concern anymore with modern runtimes such as Go or Node, but mostly for flexibility and security reasons.
Here are some key points to consider :
At this point, Nginx is a proven and battle-tested HTTP server
This allows keeping the application as simple as possible : Nginx will handle logging, compression, SSL, and so on
In case the application server goes down, Nginx will still serve a 50x page so visitors know that something is wrong
Nginx has built-in load-balancing features, it also allows running several application servers on the same IP address
Nginx has built-in caching features (with on-disk persistence)
Nginx has rich rate-limiting features, which are especially useful for APIs
Nginx helps protecting against some DoS attacks (such as low-bandwidth Application Layer attacks)
Lastly, one aspect which tend to be forgotten these days is the importance of server logs. While in some cases it might be an accepable solution to use Google Analytics or Piwik, for measuring APIs traffic however, there is no better option. For a modern real-time log analyzer, I heartily recommend GoAccess.