Darkfeign

I recently purchased the Dark Rock Pro 2, having almost gone for the Noctua NH-D14, but Be Quiet!'s heatsink comes with PWM fan control which really does make a difference, as a fair few boards don't seem to control 3-pin fans on the CPU socket.

Sublime Text 3.

Search engine bots, or 'web crawlers' that visit the site and attempt to harvest data from it. Google, Bing, Facebook etc. In order to validly crawl the forum's data, they often authenticate themselves with forum software so they aren't assumed to be malicious.

MKV is a crazy format, I was dumbfounded when I realised how well it compressed files and retained quality. There's a nice program called MakeMKV that will sort you out for generating MKV files. There's also handbrakefor all your compression needs. Handbrake is free, MakeMKV I believe is trial based.

You guys really don't seem to get the application of Noctua's black fans. They really won't suit a standard PC case, so if you think you'll be getting the same old, quiet noctuas running in your case, but in black.. I suggest you look elsewhere.

Well Be Quiet!'s fans are extremely quiet and obviously have been matched with the scenario of heatsink cooling, so they're going to be pretty well tuned for static pressure. Of course, any high static pressure fans can effectively do the same job, but you are limiting yourself to decent quality, quiet fans that can supply the same amount of pressure with that colour scheme I guess. You also need to keep in mind that the Dark Rock 2 and Pro editions use PWM fans from Be Quiet! which helps to reduce the noise a lot at idle. You may want to look at getting fans that can be PWM controlled, or at least come with noise adapters.

This is true of practically any dynamic language, though. C++ is compiled, so it will inevitably produce high performance for HPC applications. Python can be used with a JIT to speed it up, but Python provides speed of writing for projects that C++ hinders. They all have different benefits/drawbacks.

My girlfriend was brought up a Muslim and struggles with the thought of any type of non-religious marriage. She believes that people should do what they want, and if they want to enter a civil partnership then they should be free to do so, but she also believes that marriage should be strictly reserved for a religious bond between a man and a woman, and I'm kind of inclined to agree with her. Marriage is, and always has been, a religious joining of two people. Civil partnerships are a different matter.

I have some NF A14s and at 12 volts, in the front of my case, they blow like crazy. I mean, that kind of airflow is ridiculous and understandably the noise is apparent too. At 7 volts they move a really decent amount of air and are pretty much inaudible unless it's the dead of night and you're not doing anything, but its the best you'll get by far. At 5 volts, there is a slightly strange hum and they won't start at 5 volts (A14 specific, as my P14s do). So 7 volts is almost the standard I'd use my noctuas in (I used my P14s with the LNA on my CPU and was getting 75 degrees C for an ivy bridge i7 at 4.2Ghz. Which I think is great for undervolted and only a C14, not D14.

Noctua puts all of that on the fan's packaging, and they're usually pretty accurate.

Get yourself a solid book to learn from, as nothing beats the vast information you can constantly flick back and forth for in a text book. Something like Java: How to Program will teach you programming generics using the Java language.

It's probably more important to bring in fresh cool air btw, so you might need to look at increasing your intake fans. The graphics cards usually blow air out the back of the case if they can, in which case fresh air via intakes is more important.

The NF-*14 series are successors to the NF P14, so that includes both NFA15 and NF A14 as the NF P14 is a CPU fan. The NF-S12A is the successor to the S12B and is their main case fan for airflow optimisation, but at 120mm. I'd go with the NF-A14 over the P14 as the A14 has been designed to succeed the P14 in both pressure and airflow/noise ratio.

The only issue is that for their airflow-specific fans like the S12A you're restricted to 120mm (hence 12) so you could take a look at this: http://www.noctua.at/main.php?show=which_fan_is_right_for_me&lng=en But I guess to maximise your performance, the NF-14 has higher airflow/noise ration than the NF-P14 so I guess it's their ideal 140mm fan for airflow. if you get the flx version you'll get the noise adapters.

The Corsair AF series (low noise versions) are perfectly fine to move some air out of the back of the case. If you're alright with noctua, then I've been using NF-P14s to move air out of the back. Oh, also they have a more AF optimised fan, the NF-S12A (http://www.noctua.at/main.php?show=productview&products_id=55&lng=en) that might be worth a look if its sole purpose is rear-venting. To your point about the shroud, do you have a single fan in the front? If so, what size is it currently? I'm not familiar with the case fan. If you have an option to put a second in the front I would definitely opt to do so. The shroud I guess does help to hide the cable mess and it shouldn't impede airflow too much since the cables would disrupt it anyway.

testClass method2obj = new testClass();method2obj.method2(a); What exactly are you trying to do here? It's stating a cannot be resolved to a variable, because in this code the variable a has not been set, and so it does not exist. If you're attempting to use the value of a inside the class, then you need to reference it, such as: method2obj.method2(method2obj.a); Though I haven't touched java in about 6 months now so I might incorrect in the referencing method used, but you need to ensure that the variable is public and accessible outside of the class. That, or you need to simply define a before calling method2() in your main function (or wherever you're calling it) as without an object-specific reference, Java does not attempt to retrieve the instance variable, and instead looks for a locally scoped variable, a.

The black fans aren't meant for replacements with better colour schemes, though. People don't seem to understand that they are meant for industrial applications with much higher RPMs than their regular fans.

I would agree with this, so it's a shame you so adverse to Noctua's colour scheme. It really like it in person, it has real character. I have both P14s for case fans and A14s for the front intakes (would have swapped but the round frames don't align with the screw holes.

What?! Toilet paper will create its own fluffy dust.. you might as well just go without for better airflow, and optimise for positive internal pressure.

I ordered one of these, reluctantly due to the price, for a 140mm intake for my Define R4. While I ended up using the windowed side panel as I was happy enough with the case's airflow after filling the base fan slots with noctuas, I have to say it was really good quality, and being magnetic you can just stick it on the outside of your case without the need to open the case to clean them. They have a fine mesh but seem okay for airflow too. Specific to the topic: Always filter. I had a semi-filtered Corsair Carbide 400R and with front and bottom filters, the double side-intake was still dragging in too much dust for my liking.

2011 boards allow for more memory placements as well as higher-performance CPUs. But they come at more of a cost, obviously.

I had the Noctua NH-C14 and was getting about the same results as my newly upgraded Dark Rock pro 2, so despite the smaller surface area over the D14 you can't go wrong too much with a thinner profile cooler if necessary. However that was a dual-fan down-draft CPU cooler (C14) so it might make a little difference. Not too much though,

Welcome to the programming section. Glad to hear you're interested in getting started with some programming. Like the guys above have said, there's never a right language to pick. Pick one that interests you, maybe do a bit of reading on generic programming terms, as well as the comparison between imperative and functional programming languages, and then follow other stuff like strong/weak typing. For stuff like this it can be helpful to get a proper programming book, but if you want to research online first without committing, there are a few options for you. First, i'd take a look at the programmer resources thread that's pinned. This has a bunch of good resources compiled by frequenters of this section of the forum. I'd then suggest looking at a couple of the language resources there and seeing which you might prefer. Python, for example, is a great starter language as it lets you interact directly with the interpreter if you so wish, and you can avoid the need to learn specific syntax rules (another programming term you might need to look at). If you fancy getting straight into other popular languages, Java is often a popular place to start, though some people feel different about Java (C# could be your alternative). C++ is often a popular language for anyone looking at serious programming, but be aware that you'll be introduced to memory management almost immediately when getting into the language. Memory management can be a pain and is avoided entirely in languages like python and java, so i'd suggest leaving it for A-levels, and picking it up after some introductory programming. I started with a little PHP but quickly grew to dislike its... messiness. Python was the first proper programming language I used and it's great! Vast amount of help online, and great resources for UI and graphics etc. Then I moved onto Java. Really good for developing decent software while avoiding memory management, but there are always countless issues with Java's VM that people come to dislike it for.

In my final year project, I worked with OpenSceneGraph to develop and test a line-of-sight strategy. Very basic 3D rendering performed by OSG and computation for line-of-sight programmed ontop of the graphics layer to give me full control. I only had about 7 files of code, totalling maybe 2k or so, but with the inclusion of many library and header files from OSG itself, compilation time on a core i7 3770k was at least 3 seconds by the end, and that's just a few linked files and OSG's dev files. So I can understand why much larger-scale projects demand some compilation time. However the guy writing xkcd is probably referring to a few years ago, maybe. Or the fact that compilation in a workplace often utilises the network's central servers for compilation, which may require several time-allocations of the process to complete the job.

If you've already made a start with Java, it wouldn't be a bad decision to stick with that as you should be comfortable with the compiling stage and the libraries, etc. My suggestion, therefore, would be 'Java: How to program' (Deitel). It's a full programming guide with a concentration on Java, but is very thorough.