Recent submissions

Comment · 4 years ago
Comment · 5 years ago
Try sitting on an exercise ball instead of a chair. It worked for me. It takes a couple of weeks to build up to the point of being able to completely ditch the chair.
Comment · 5 years ago
Comment · 5 years ago
Comment · 6 years ago
Comment · 6 years ago
This is very useful. Note though that all of the following doesn't work unless you have ssh access to the server: - search - terminal - monitoring (cpu & memory) - report of used/available disk space - system information
Comment · 7 years ago
All of the JavaScript written for https://cloudbuddy.cloud/ is raw and developed from scratch (zero frameworks / libraries / dependencies). It was my belief at the time that maintenance costs would be zero or extremely minimal over time since there was basically no dependency on anything external. Since inception (over 2 years), the benefits have held true. The disadvantage of course is that it took longer to finish the service and offer it.

So, I'm an old timer. I've been doing software development professionally for 25 years. For me, new development is stimulating; maintenance - not so much.

Andrew, here is what I would suggest - create and finish a small project and code it in ReactJS. Then code the same one using only raw javascript. With the experience, you'll have your answer whether the cognitive load is worth it.

Comment · 7 years ago
Comment · 7 years ago
Comment · 7 years ago
Comment · 7 years ago
Comment · 7 years ago
Thank you kind sir.

When I was investigating backup solutions in 2010, I did read about rsync and had read a few negative reviews saying that user's had their backups corrupted (by rsync) and that they were unable to restore their backups. However, looking now I am unable to find those reviews. So, likely either those issues were fixed in a newer version of rsync or I am not remembering the posts correctly.

Comment · 7 years ago
So corrupt backups weren't possible - just my personal preference.
Comment · 7 years ago
Thanks for your comment. Actually, Client-Side-Encrypted-Backups is different in that a backup cannot be created unless tar, ccrypt and sftp on the user's machine execute smoothly. In your example, in the case of a user's local drive going bad during a backup, one of these (tar, ccrypt, sftp) would fail causing the backup to not be created. All files that show up in the completed_backups log file are golden backups and can be restored at anytime. For me, I have been exclusively using Client-Side-Encrypted-Backups to do all of my backups (since 2011). I don't ever recall seeing an issue in all of those years. It's been very reliable.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton