Please cite facts, not unsubstantiated tinfoil hat material devoid of citations.
I has been shown [1] that the risk of being affected by narcolepsy among children vaccinated with Pandremix is 4.19 times higher than the risk among children that were not vaccinated with that particular vaccine. This in Sweden, related to the H1N1 mass vaccinations.
69 verified diagnoses of narcolepsy were found among vaccinated children. It has not been proven that all cases of narcolepsy were directly caused by the vaccine.
Your claim that this Finnish woman's assertion that the Swedish gov't in cahoots with the US gov't wanted to "get rid of young people" is somehow not "balooney" is patently ridiculous based on the simple facts.
The graphics output from the CPU is sent over Intel's own FDI (Flexible Display Interface), so the limitation lies in the PCH (chipset) that converts FDI to the various display interfaces.
I looked at one datasheet [0] for the 7-series chipsets and it didn't mention Dual Link DVI at all (although DVI was obviously mentioned). It did say "DisplayPort/HDMI/DVI 2560x1600 at 60Hz" in one of the tables, but your guess is as good as mine if that implies support for Dual Link DVI or not.
Edit: added link to referenced datasheet. See chapter 5.28.
Wouldn't you want to use a language that is familiar in a competition? If Ruby is your forte, surely you should use it?
I fail to see how "magic" properties of a language matter if you've got reasonable algorithmic chops and focus on solving the problems rather than trying to be clever.
If the goal of the competition is to slice apples, then a knife is pretty good compared to a gun. Or if the competition takes place under water. Or if you're Steven Seagal and the ship where you work is taken over by a splendidly over-acting Tommy Lee Jones and his gun-wielding minions.
Execution speed is nice, I don't disagree. But it's not always the be-all and end-all deciding factor for what tool to use to solve a problem in a specific context.
Competitions can be stressful, and choosing a tool that feels like an extension of yourself (be that Ruby, COBOL or whatever) is, to me, the better route. Compared to something that executes faster on your computer but not in your head.
I don't think the parent post (which I totally agree with) was saying that you must always decide by picking an inherently fast language, but rather if you decide to pick one whose execution time is not inherently fast to enter a competition where execution time is factored you will start with a major disadvantage.
That doesn't mean you'll lose (ala your Steven Seagal analogy), maybe you're so much better than everyone else that you can overcome the disadvantage, but you'll surely be starting in a bad position compared to someone holding a 'gun' even if he or she is somewhat less skilled at using the gun than you are at using the knife.
My experience with GCJ has been that raw execution speed almost never matters as long as you have the right algorithm.
In the case of the OP, for example a trivial optimization(the kind you do without even thinking in these competitions) would've brought his execution time down 10000x. Basically, you are asked about the number of "fair and square" numbers in a certain range, over and over again, in 10000 different cases. He could have just taken his solution, pre-generated all those numbers once and then ran all those test cases by counting in that pregenerated list, instead of generating it for every single test case(all 10^5 of them). It turns out, that in the whole span of 1->10^14 there is only 39 such numbers and it would've taken his program probably less than a minute to generate all of them(I'm being generous here, since it ran 10^5 test cases in 53min).
In fact, if you read the problem analysis later provided by google you will see that in fact you were expected to make this optimization to solve the problem. The fact that C-small had 100 test cases, C-large-1 had 10^5 and C-large-2 had 100 should've been a strong hint that C-large-1 required some pre-caching across test cases.
Well sure, adding "where execution time is factored" makes it hard to disagree with you. (And ultimately, it usually becomes a factor sooner or later.)
That wasn't the context in which I was writing my original reply, however. I was responding to a post that mentioned "magic" as a reason to disregard Ruby for competitions, which I didn't agree with. (The Ruby solution in the submission was slow even using a while loop, which is far from magic.)
If you're able to solve problems in the same amount of time using a fast and a not so fast language, of course you pick the faster one in a competition. I'm not arguing against that.
I disagree with the premise in a similarly nonsensical fashion. (I mentioned neither execution performance nor weapons in my reply.)
The ultimate goal in a competition is to solve the problem within a fixed amount of time. This requires you to actually implement the solution to be able to run it. If you are able to do that more easily with a language that is inferior in execution speed, that will probably be the best strategy. At least compared to using a really fast language that you are not as comfortable with.
It's why IOI (http://www.ioi2012.org/competition/rules/) doesn't allow interpreted languages, because they are (or at least when the competition was first held were) just too slow.
If you have only 1-5 seconds of computations time you're going to choose for a compiled language every time
Well it's just that to support another language they need to make solutions for every problem in that language to test that it's actually possible and they don't want to do that.
and on that page it says:
Each submitted source program must be written in C, C++ or Pascal, it must be smaller than 100 KB, the evaluation server must be able to compile it in less than 10 seconds and at most 256 MB of memory. No other extensions different than the ones listed above will be run.
They put Python and Ruby on the machines so you can write a script to generate testcases, you can't submit programs written in those languages
The described behavior is the default behavior. You can change it to load all tabs after restart in the options†.
To always load all tabs after (re)start, go to Preferences > Tabs and uncheck "Don't load tabs until selected". ("Preferences" may be called Options or something on Windows or Linux, I can't recall right now.)
I would argue this is a sane default setting (it trades some waiting time when switching to a different tab for snappier start-up). Regardless, Firefox gives you the option to choose your behavior, which I would argue is the non-lazy thing to do (however simple).
† Note I am on Nightly, so it's possible this preference is not yet visible in the release version. It probably is, but just to be clear.
I looked into doing something like this a couple of years ago, the regulations in Sweden are quite strict.
First you need to send an application [1] to the Swedish transport agency (Transportstyrelsen) and have it approved at least 30 days before the release of the balloon (the application alone will set you back about $200 US).
There are a bunch of regulations for the aircraft as well [2], radar visibility related for example. And for the time of the release; at most 2/8ths of the sky can be covered by clouds, visibility must be at least 8km. It's illegal if these conditions aren't met.
If you have a camera on board, you will have to get all footage vetted by the military to make sure you haven't photographed any secret installations or similar. As best I could find out, you send them the complete raw footage of everything and they give you back whatever's cleared by them. (I didn't ask official questions regarding this, so it may be I misinterpreted the information I did find.)
This idea can be extended even further, to users who do not know how to (or cannot) build the software in question.
One example of this is mozregressionfinder [1] that was created by Heather Arthur [2]. The tool automatically downloads Firefox nightly builds (in the same binary search pattern of bisect) and lets the user check for the bug they observed in each version. Once the nightly build where the bug was introduced is found, a Mercurial pushlog URL is displayed which can then be pasted into a bug report to aid developers in chasing down the bug.
Per-window private browsing is implemented and available in Nightly according to [1] (so, most likely in Aurora after the release shift this week). So hopefully it'll be in Firefox 20.
Meta-bug for per-window private browsing in Bugzilla is [2].
I has been shown [1] that the risk of being affected by narcolepsy among children vaccinated with Pandremix is 4.19 times higher than the risk among children that were not vaccinated with that particular vaccine. This in Sweden, related to the H1N1 mass vaccinations.
69 verified diagnoses of narcolepsy were found among vaccinated children. It has not been proven that all cases of narcolepsy were directly caused by the vaccine.
Your claim that this Finnish woman's assertion that the Swedish gov't in cahoots with the US gov't wanted to "get rid of young people" is somehow not "balooney" is patently ridiculous based on the simple facts.
[1] http://www.lakemedelsverket.se/OVRIGA-SIDOR/Den-nya-influens... (Swedish)