Among the stories of your life, family and other things, also tell a story of progress. Tell of things that we enjoy today that didn't exist when you were a child. How did those things come to be?

I am very sorry to hear of your impending death and the pain it will bring to your family.

Maybe also tell a cautionary tale for when she is an adult. The world has had dark episodes of history before. And it could again, but on a much larger scale. What lessons can be learned from the past to prevent it happening again?

To get the best of both worlds, use each tool where it works best.
1. Use Java Applets in the browser to get Java's famously good start up times and the kind of Security that comes with complex interactions between JavaScript and a Java Applet that has elevated permissions
2. Use interpreted JavaScript on the server (not Node.js)

Use Windows as the Server OS, in order to get the kind of security, robustness and stability you've come to expect from Microsoft
Use Linux on the Desktop to get it's legendary ease of use*


(* however Linux ease of use is great in the last few years)
(I hope I do not need to add a humor tag)

I am not complaining about the 2nd amendment. Only that crazy people can get weapons. And not just ordinary weapons.

> They have put a kill switch in them somewhere

Um, isn't the TRIGGER a kill switch?

The US won't let al-Qaeda or ISIS get armed drones any more than the US would let them get US made weapons.

I hope that answers your question.

:-)

I sure hope it was not necessary for me to use the SARCASM tag in the above post.

Um, I am going to be very surprised if they forbid citizens to buy unlimited numbers of armed drones. Or if they regulate ownership, or require background checks or registration. After all, when the 2nd amendment was written, it envisioned every citizen having enough firepower to start a world war.

Please remember this holiday season that firearms make excellent gifts for the entire family. Family packs available at participating retailers. Check out the new Starter Guns sized just right for the little ones. Please use firearms responsibly when drinking. The NRA offers discounts to those who can show proof of mental impairment or illness.

This is a strategy for demonstrating the absurdity of the current patent regime, right?

I think you may have meant this is a tragedy for demonstrating the absurdity of the current patent regime. Just a typo, I'm sure.

Shouldn't it be called: Algorithmic Patent Trolling

If you trust the document's own encryption mechanism, then you are still left with a problem. How do you communicate the password? PKI is a good answer.

That is my point. A basic understanding should be expected. Now a detailed expertise. I agree completely with what you are saying, and I say similar things elsewhere here.

Just to add: if you did what I described, you would quickly discover that the actual secret you should send using PKI is the key to some other more efficient symmetric algorithm.

Your question demonstrates that you don't understand the problem. How do I securely send you a file? If I use Excel's encryption, then we have a new problem: how do I send you the password to open it?

Furthermore, it is a legitimate question to consider whether you should trust Excel's security. (And I'm not picking on Microsoft. At least not this time.) You don't have access to Excel's source code. You can't know it is secure. You could sleep a lot better if you simply assume the Excel is just like any file, and like any other file, you encrypt it and sign it with PKI so that the person on the other end can decrypt it and verify it is from you. (Actually encrypt and sign a small key to a more efficient symmetric algorithm.)

It depends on what you mean by 'know how it works'. If they are using it in the project, then I expect them to 'know how it works'. I don't expect them to be able to write their own from scratch. Just a basic understanding. Not an explanation that you sprinkle magic encryption sauce on the data.

Generate a pair of keys. Make one public. Ask the guy at the other end to do the same. Now we can read each other's public keys (and so can anyone else). I encrypt the PDF with your public key and then with my private key. The guy at the other end can verify that it came from me, and he is the only one who can decrypt it. I don't need to know all the detailed math. I don't have to write my own BigInteger code. Just a basic understanding.

Why is this more to ask than that someone knows the language that a shop uses. Knows how to use the framework we use. Etc?

Life Long Learners is also a plus.

Whew! Now that I've got a diploma, or certificate or whatever, I don't ever have to learn anything ever again!

I would place much greater value on a developer who prefers to constantly learn.