According to the Swedish newspaper Expressen, at least one of the founders (Mr Neij), currently living in Bangkok, does not intend to evade his sentence.

http://www.expressen.se/nyheter/1.2696506/hovrattens-pirate-bay-domar-star-fast

Google translate:

"Fredrik Neij now lives in Bangkok and he is disappointed with the HD's ruling. But he will not stay out of the sentence.
- But I'll probably try to get the punishment commuted, perhaps to electronic tagging or so, says Neij told TT."

It is bricked.

What if the accused claims the encrypted drive contains the proof of his innocence and he desires nothing higher than to provide the court with the password but regrets that the shock of his arrest and subsequent stress of the trial has rendered him unable to recall his password?

Careful what you wish for..."Congratulations! Your new sowing machine comes with no instructions whatsoever in accordance with the principles of 'self documenting design', which means that its designers understand how to use it."

But that implies that the arraysearch function would also contain the code to run when a match is found in the array, which breaks the rule of least surprise.

Perhaps simply:

if(arraysearch(array, value)){
//code to execute when item is found.
} else {
//code to execute when item is not found.
}

It can if you reapply the trick of staring hard enough at the experiment output until you see the desired result.

Well explained. I'dd only add something about where each of them fits. Roughly, to the best of my experience, Online Transactional Processing is for supporting business activity such as when customers place orders. The order is recorded first in the OLTP database for being processed by shipment systems etc. When the order is completed it is often deleted from the OLTP database that should be kept small and nimble to be able to keep up with incoming orders in a fast and responsive way. The OLTP database, as mentioned, is highly normalized (each item in the data is saved in only one place). This is to some extent to keep the database small but also to ensure consistency in the critical business data (when the same data is saved in two places it risks getting out of synch, perhaps leading to things like orders being shipped twice etc). For the same reason of consistency it is also important that all work is encapsulated in transactions. Transactions are a way to ask that several changes to the databases that go together logically for some business reason be done in an all-or-nothing fashion. For example, all the data changes to the database associated with, say, an order being placed can be saved to the database as a unit such that if all goes well all the data is saved but if any of the data changes for the order is met with an error none of the changes in the unit should be accepted into the database (thus the "Transactional" in OLTP).

A copy of the order is also saved to the Online Analytical Processing database, where is does typically not become deleted so soon and its data may be saved redundantly in multiple copies (denormalization) to speed up queries. The purpose of this database is not to support customers placing orders, but to support managers asking questions about "what is historically our most popular shoe color in December" and things like that (the "Analysis" in OLAP).

No, he would have spent three hours searching his house until he found his old DVD (at least that's what I would have done and I took it to be what GP meant) if the pirate bay option had not been there. There would never have been any more money going to the game company or anyone else, only a net productivity loss (three wasted hours) to the benefit of absolutely no-one.

if($sense == $it_is_a_little_bit_complicated){ // explain why here
};

If I started coding today I think I would go about it roughly thusly:

1) google "Game coding tutorial HTML5" or similar,
2) Find the code listings, run them, modify them a little to see what happens but eventually be annoyed that I don't really know what the magic incantations in javascript etc mean
3) Google "javascript introduction" and spend some time just writing "Hello world" apps and such, trying to learn basic javascript, until I got bored with that.
4) Return to the game code, be absolutely gratified by discovering I indeed understand a little more of the magic incantations, do a bit more targeted modifications of the code to see if I can actually predict the outcomes at all....until I got bored with what I could do with my current level of understanding and return to the course in basic javascript to learn more (repeat from 3, basically). At some point you may know so much general javascript that you can continue learning more about javascript itself by looking directly at the game code and realize how it must work.

As long as you find some little "loop" like that where you actually have fun all the time while learning, chances are good you will end up knowing quite a lot about how to program.

But what if it leads to few of the College trained developers you hire being able to code their way out of a wet paper bag precisely because before they enrolled they had already been coding as a hobby for years, an interest that was initially sparked by an online javascript course?

If by "people look down on it" you are suggesting veteran programmers look down on beginner courses because beginner courses have been around for ages, I would care to disagree. I am fairly sure many veteran programmers indeed began their careers with just such beginner courses, way back when, which corroborates your assertion that such courses have been around for ages but gives no insight into why anyone would look down on such courses...which leads me to guess that maybe you mean that it is the _hype_ that is being looked down on? In that case, sure, hype can look a bit laughable to a veteran who has perhaps seen the object in question being hyped several times before. On the other hand, perhaps for a few veteran coders it was some hype that once helped them to find their way to a beginner course that set them on their path to become veterans. So even the hype can have a purpose and should not be looked down on, in my opinion.

But perhaps you didn't at all mean "veteran programmers" by "people" ? On the other hand, I don't see how junior programmers would have enough experience to look down on the material they are still learning from, and the general public (assuming they know even less about programming than the junior programmer) would consequently have even less experience to draw on when looking down on the material.

So perhaps you meant "intermediary programmers"? In that case I must agree I have sometimes seen tendencies of some intermediary programmers who are overly eager to distinguish themselves from junior programmers to look down on material suited for the juniors, but it is an approach that rarely lasts for very long, and I would frankly advice against such advocacy as a way to establish one's experience as a coder as it is fairly transparent.

I'll even bet he's just the type to go around downloading and using free open source software without paying a penny for it!

So on this island no-body can ever have a week off from hunting pigs or their other duties?

What if the pig hunter produced some extra pigs along with saving up extra shells so that the other two could still buy pig during the week off?

And if the pig hunter can have a week off, does that imply the economy at large also isn't screwed?

"Just for starters, if you proclaimed that a Z80 with a stripe on it was the most awesome thing ever, anyone who actually knows what a Z80 and carse what it does is would laugh at you, and they'd be right."

But what about an all white casing where the user cannot change the battery? Slam dunk, right?