DavidTheWin

You do want a top exhaust since dust falls down on top of it and through the cracks

There's no set standard for versioning which is fine because not all software can be versioned in the same way. A common one like you said is major.minor.possibly another minor.revision. The major version goes up when you have a lot of changes or say a few very large changes, minor goes up when it's a few small changes and revision is just the revision of your code repo. The second minor revision is for tiny changes like hotfixes. The revision of your code repo is very important because by looking through the revision history you know exactly what code you deployed.
This style is very common because it works for a lot of software projects. However it differs between companies and teams within those companies. For example, there are some teams within my organisation that seem to just use 1.major (stupid IMO) and one of the applications my team develops is year.month.revision, e.g. 15.6.49607 is the June 2015 release at code revision 49607.
 
Alpha and beta are very different and well defined terms. Alpha testing is carried out by the testers (this could be another role of the developer) within the company in a controlled environment to test for functionality and any low hanging bugs. It's not open to anyone outside the organisation. Beta testing on the other hand is performed by the end users of the product. This might be an open beta for a game where anyone can try it out, or it might be a group of developers at the customer trying it out. At this stage it will undergo testing in something that is supposed to approximate a live environment although you can rarely get close to that, think about how many games have server issues on launch because you can't stress test your servers with that many people in a beta.

kerblam
 
http://www.newegg.com/Product/Product.aspx?Item=N82E16814125680&nm_mc=KNC-GoogleAdwords-PC&cm_mmc=KNC-GoogleAdwords-PC-_-pla-_-Video+Card+-+Nvidia-_-N82E16814125680&gclid=CjwKEAiA8qG1BRDz0tmK0pufw3QSJACfn6olEjM_nsLdBXiWIwC_uZKyJibOzOQNasnX0rMMUo639xoCogHw_wcB&gclsrc=aw.ds

The encoding is done on your CPU so you want to upgrade that to improve the encoding of your stream. If the pentium G3258 supports Intel Quicksync you can use that to use the integrated GPU on your CPU to do the encoding for you thus freeing the load from your CPU but only if you have the setting in the BIOS to disable the iGPU when a dedicated GPU is available is turned off.
 
The G3258 is 2 core 4 thread right? If you want to run a quality stream you'll want at least 4 physical cores, preferably with hyperthreading. I'm assuming here you're using a reasonable bitrate such as 2000 and not anything crazy like 4000+. If you aren't already run your stream at 30fps and if you're stuggling at 720p you can drop down to 540p which is a happy medium between 480 and 720.

Don't give idiots like this attention. That's all this video is; attention seeking.

Looks to me like the back of some contact points for an mPCIe connector:
 

The 970 is worth it now if you can pass it down to another system. Otherwise wait.
 
This is what I am doing, getting a 970 now to hold me over till pascal. 
 
But that's only because I will put in a lower powered system to make it game even better. 
 
If you don't plan on selling it or handing it down, don't waste the money. 

You can even install freenas on a bootable usb drive and run it off that.

You should define schoolwear as an enum so you can say 
switch schoolwear{ case Uniform: stuff case Gym: stuff} Makes it more readable.
 
I'd also pass all the assignments you're making to a function that takes 3 arguments looking like
function(arg1, arg2, arg3){ MyRenderer.materials[0].mainTexture = arg1; MyRenderer.materials[1].mainTexture = arg2; MyRenderer.materials[2].mainTexture = arg3;} Then you just call that function instead of writing it out 3+ times.

You should define schoolwear as an enum so you can say 
switch schoolwear{ case Uniform: stuff case Gym: stuff} Makes it more readable.
 
I'd also pass all the assignments you're making to a function that takes 3 arguments looking like
function(arg1, arg2, arg3){ MyRenderer.materials[0].mainTexture = arg1; MyRenderer.materials[1].mainTexture = arg2; MyRenderer.materials[2].mainTexture = arg3;} Then you just call that function instead of writing it out 3+ times.

The 960 is a very low powered card so doesn't produce much heat to dissipate anyway. That card looks to have a cooler that at least isn't shit ignoring what that guy above me said (fair amount of metal and 2 big fans). Gigabyte make and sell a lot of graphics cards. Don't you think you'd have noticed a lot more complaining if they were prone to overheating? The fact your friend had 3 overheating graphics cards from them suggests your friend is the problem not the graphics card.
 
Edit: that said, there is a review of that card that hints that there's an issue with the fan speed profile but it seems to be relatively uncommon and I doubt your friend was unlucky enough to get 3 graphics cards with a faulty fan speed profile.
 
You also can't take experience with one version of the graphics card and apply it to the entire brand. EVGA had issues with their ACX cooler on the 970. Does that mean all EVGA coolers are bad? Of course not, especially when they fix their mistakes.

The 960 is a very low powered card so doesn't produce much heat to dissipate anyway. That card looks to have a cooler that at least isn't shit ignoring what that guy above me said (fair amount of metal and 2 big fans). Gigabyte make and sell a lot of graphics cards. Don't you think you'd have noticed a lot more complaining if they were prone to overheating? The fact your friend had 3 overheating graphics cards from them suggests your friend is the problem not the graphics card.
 
Edit: that said, there is a review of that card that hints that there's an issue with the fan speed profile but it seems to be relatively uncommon and I doubt your friend was unlucky enough to get 3 graphics cards with a faulty fan speed profile.
 
You also can't take experience with one version of the graphics card and apply it to the entire brand. EVGA had issues with their ACX cooler on the 970. Does that mean all EVGA coolers are bad? Of course not, especially when they fix their mistakes.

Have you tried turning off the multi frame sampling and seeing if it went back to 60?

2ms, damnit I should upgrade
 

2ms, damnit I should upgrade
 

That's a pretty good build. You should probably drop the wattage on the PSU though, you won't need 750W to run a 6600k and a 980ti, you'd only need 600W at the most. You might want to stick with it if you have plans in the future for SLI if you change your case and motherboard.
 
Only thing I'd maybe suggest is waiting for Pascal which we hope should be soon and should have a tangible benefit over Maxwell. On the other hand, it might be a while before a Pascal 980ti equivalent comes out.

That's a pretty good build. You should probably drop the wattage on the PSU though, you won't need 750W to run a 6600k and a 980ti, you'd only need 600W at the most. You might want to stick with it if you have plans in the future for SLI if you change your case and motherboard.
 
Only thing I'd maybe suggest is waiting for Pascal which we hope should be soon and should have a tangible benefit over Maxwell. On the other hand, it might be a while before a Pascal 980ti equivalent comes out.

Are they standoffs that you put a screw in or do they have a nub at the top like this?
 

 
If it's like that then the nub at the top goes through the hole on your motherboard, you don't screw anything into it. It's there to help keep the motherboard in place while you screw in the other standoffs that need screwing in. I haven't heard of a case having 2 of these though.

Javascript and Java are entirely unrelated

*nodnodnod*
 
Thankies. Much appreciate the help from everyone , special thankies to David for managing to explain it in a way which I understood ^.^
 
 
Happy holidays guys <333

It's got an "automatic" movement. That means there's a rotor in the back that swings with the movement of your arms (like when walking) that winds the mechanism to keep it working. In theory it will never need winding since the power reserve is 40 hours and that will be "charged" (mechanically) with surprisingly little movement. If you leave it longer than 40 hours or so the power reserve runs out and it will stop ticking and you'll have to get the rotor moving again for a little while to build up some power so it ticks again at which point you can re-set the time to the current time. Most automatic watches allow you to wind using the crown but Orient (and Seiko I think) watches use movements that don't have a winding function in the crown so you actually have to wear the watch and move your arm as though you were walking to wind it properly.
 
Extra word of warning, don't change the date between 6pm and 6am. At any time between those times it's likely that the gears for the date mechanism are engaged and trying to adjust the date between those times could damage them. Another thing to note is that you should get the watch serviced every 5 years or so to keep the movement working properly because it needs re-oiling by a professional and the gears wear down due to friction and need to be replaced.
 
Edit:
This is an example of a rotor from a watch with a display back. The big semicircular chunk of metal swings with your wrist movement to wind the watch rather than using the crown to wind it.
 

I'd avoid objective-c. There's a reason Apple has abandoned it in favour of Swift.

OS, all programs and your most frequently played games. If you can't fit all that then drop the games.

Few code quality things
* Remove all the unnecessary whitespace, i.e. lines 10, 13, 16, 18 and 19
* The variable m isn't necessary at all, just pass i * t into the print function. If m was required (for example if you were using the result of i * t more than once and don't want to calculate it twice) then you should declare m inside the loop rather than putting the declaration outside the loop.
 
For making the output prettier, rather than using WriteLine you want to use a StringBuilder and append to it the number followed by a space, so you start with an empty string "", append "1 " to it giving "1 " then add "2 " to that giving "1 2 " and so on then print it at the end of the inner loop with a new line character.

Few code quality things
* Remove all the unnecessary whitespace, i.e. lines 10, 13, 16, 18 and 19
* The variable m isn't necessary at all, just pass i * t into the print function. If m was required (for example if you were using the result of i * t more than once and don't want to calculate it twice) then you should declare m inside the loop rather than putting the declaration outside the loop.
 
For making the output prettier, rather than using WriteLine you want to use a StringBuilder and append to it the number followed by a space, so you start with an empty string "", append "1 " to it giving "1 " then add "2 " to that giving "1 2 " and so on then print it at the end of the inner loop with a new line character.