It depends on the app. Single page apps are perfect for websites that should feel like native desktop or mobile apps. For websites that have a lot of dynamic content I'd say it's a must - too much JQuery for AJAX and DOM manipulation may indicate that.
On the other hand, if the app is very simple and has got just a little dynamic content, there's no need for SPA approach. For example, an admin panel for cloud like DigitalOcean or my project (https://demo.virtkick.io/) are good enough with server-side views.
Also, if the app needs to be super-fast, especially on mobiles, then server-side generated views are rather prefered. However, Twitter serves server-side generated views for first page load, and then does the rest like a SPA. While not possible with AngularJS (yet), you can do that by building your own stack on top of Express.js - just render the templates with JADE on server-side or client-side. That's the example my friend did a few months ago: https://github.com/RushPL/express-app-angular
Thanks for your feedback. Actually, the explanation is below the menu. It wasn't clear enough I guess? This is a static HTML prototype.
There is only one dynamic thing: the noVNC console that connects to a real VM. The VM doesn't have any network or storage - it's just an Arch Linux LiveCD. A cronjob restarts it every 30 minutes to ensure it's usable - some people have bad habits to execute commands that break the OS. ;)
Bacula. http://bacula.org/ At my company we are using it for server backups. Linux desktop would do too. Google says it's possible to use Bacula Client on Mac, but you'd need to figure out yourself.
Becula is fine on Linux [server], but I'd never run it on Windows Server again, it has no effective IO throttling (just number of concurrent jobs throttling, which is ineffective). On Linux you can fix it using security groups with limitations placed on IO specifically (at the kernel level).
It is better at several large files than thousands of small files. In fact when you throw millions of small files at it it chokes pretty bad (CPU skyrockets). So if you need to backup an SQL server data store you'll be just fine, but thousands of XML files? Maybe not.
Thanks. OP wasn't interested in Windows. I have never been either, so I didn't even know. Thanks for the info.
Regarding the small files performance - thanks for pointing it out. We are using Bacula to backup JIRA & Confluence data stored directly on the disk as files. Some customers have thousands of small attachments in their instances. I haven't seen any performance problems though. Maybe because not only there need to be thousands of small files, but also they need to change often, which is not a case for us. Will keep this in mind. Thanks.
In understand the key is not transfered to the server, but I would still love to see SSL. I also wouldn't want any external resources on the page. No Statcounters or Analytics. Good direction though, appreciate the effort!
On the other hand, if the app is very simple and has got just a little dynamic content, there's no need for SPA approach. For example, an admin panel for cloud like DigitalOcean or my project (https://demo.virtkick.io/) are good enough with server-side views.
Also, if the app needs to be super-fast, especially on mobiles, then server-side generated views are rather prefered. However, Twitter serves server-side generated views for first page load, and then does the rest like a SPA. While not possible with AngularJS (yet), you can do that by building your own stack on top of Express.js - just render the templates with JADE on server-side or client-side. That's the example my friend did a few months ago: https://github.com/RushPL/express-app-angular