Or more to the point they are more likely to suffer from not learning how to take care of themselves.

Why do you think "today" is any different?

Less work to do up front makes it easy to get started. Not your problem if a 100000 line code base is unmaintainable down the track

Yes I agree thats way more secure.

What I mean is that cat /home/me/www/path/to/index.html will say Permission denied but it won't say Permission denied reading /home/me

Unix doesn't help much. I mean if apache can't read /home/me/www/path/to/index.html the OS isn't going to tell you its because of the permissions on /home. Meanwhile you have given up and gone chmod -R 777 /

But with python and javascript being so dominant we are headed in a totally different direction for the bulk of our applications.

My brother and I used to clear the static charge off the screen of our TV if we had been watching it when we weren't supposed to. Our dad was a tech and would pick up straight away that it had been operating.

The high frequency whistle they made. About five years ago my son switched our old CTV TV on and asked me about that sound. I realised that I had lost the ability to hear it just as the CRT became obsolete.

Try dropping the landing gear in a commercial jet at mach 0.8.

Friday wasn't intersex. Maybe you are confusing it with I will fear no evil. Friday was solid cyberpunk though.

They have just started a service in Australia and probably view Australian customers of US netflix as competition they don't want. So they have started to clamp down on VPNs

The only locks in git are within single repositories. The locks which control distributed merging are controlled by the hashes which identify change sets. They tell a repo about the origin of the data being merged in. So rather than thinking about a static blob of data which changes sometimes and needs to be preserved while other nodes are working on it, you think of a graph which extends into the future, each node identified by its hash. By working this way it is easier to find places to reintegrate the results of processing which takes place remotely.

My point is that git knows how to merge. It knows when a merge is required, when it is not, and when it can be done automatically. If you design your data structures properly, the same behaviour can be used in massively parallel systems.

...a tool which he may have heard off. It does connectionless, distributed data management, totally without locks.