RDS/Aurora does do autoscaling, backups, georeplication, encryption etc. It's more a matter of time & convenience rather than skill. Sure you could do all of it yourself on an EC2 instance, but at some point it becomes a big chunk of your job, and you would rather be spending your time on other things.
Because companies aren't spending millions of dollars, hiring specialists and tweaking their content in every which way to get to the front page of Bing.com results.
Why do you think WhatsApp doesn't need section 230 immunity? Do you think it can survive while being held liable for every bit of content shared on it?
In terms of acquisition value, the codebase ranks dead last behind talent, product, engaged users, company brand, patents and just about everything else. Even very successful products are almost always rewritten when acquired by a larger company.
Depending on what your co-founder is walking away with, you may want to negotiate a better exit. If there is nothing else, then more than the code work on selling yourself to an interested company.
> If I were you, I would fight for ownership in whatever is next for your cofounder
Depends on whether the cofounder is using the current company's assets towards the next venture (and it seems like the answer is no, so there is really no basis for that ask).
If you don't need a GUI then you can use Docker for basic sandboxing. It isn't a foolproof solution, but it's about as close as you are going to get without full virtualization.
The average non-technical user is never going to open up the terminal and run commands. The well educated technical user is going to be vary of untrusted sites and various forms of attacks (which I'm assuming the author of this post falls under).
IMO this is good advice for those that fall in the middle of these two categories, i.e. slightly technical people who run into problems and copy-paste solutions from Stack Overflow hoping that something will work.
> you’re not running some random shell script from a random author
This is exactly what is happening in the vast majority of these cases. These users are going to be vary if linked to an executable or installer, but "hey just run this simple line of code" sounds like a very appealing solution.
If this is a foreign concept to you, research the many companies that Cisco spun off to develop new technology and subsequently spun back in. While not a common pattern it is a recognizable one. It is possible that is what is happening here.
