Now you just need to get OSX86 on it for a triple boot, but support for things like graphics and network cards are a bit iffy for laptops at the moment. It is always fun to confuse those around you while booting up Mac on your PC though.
That may be a viable idea with a HDD as big as mine, but messing with it is another story. I already had to reinstall Windows once (after the initial installation) due to a GRUB error 18. That basically means my Linux partition was too large for my BIOS to handle. Old BIOS is the most likely cause, because a few years ago when my laptop was made, hard drives that large were rare if not nonexistent. Anyway, I finally got it running, but only on a 50 gig partition. W*ndows has the rest.
This post brought to you by Ubuntu Linux. 
Kubuntu and KDE is better. You’ll be switching to KDE once you discover that for yourself. 
There are two sides to every coin, Ivan.
When one goes through great pains to develop highly efficient code, it often ends up being quite unreadable to another engineer… many comments and much documentation are needed for the code to have any hopes of being maintained by another person.
Software isn’t just a write-once-and-walk-away animal. Software needs to be written in such a way that people can come back to it and modify it as needed. And cryptic software is much, much more difficult to maintain than simple, elegant software. It’s not laziness, it’s efficiency, readability and maintainability.
Have you asked a graphical engine developer about how he writes his code? They’ll use any and every trick in the book to streamline their software. Critical sections of code will be written in assembly language, targeted at a specific processor… while in other places, sure, you might find recursion.
As JC mentioned, programming is only one step in the process. Selecting the right compiler and using it to its full capabilities is just as important as writing “good” code.
As long as you continue hurling generalities and misconceptions, I’ll continue knocking them down, TYVM.
FTFY.
It’s not the tool, it’s how the engineer uses it… OSes, languages, etc. can all accomplish the same tasks.
You can waste eons of time configuring and re-configuring your system but you aren’t getting anything done until you open up an editor and start writing code… unless, of course, you’re aiming to work in IT. 
Get 'er done, Tyler!
Don’t be knocking us IT guys. If wasn’t for us you would not have anywhere to write your code. 
I’m not knocking the profession at all… IT has their role cut out for them in corporate America… but I beg to differ about the latter half of your statement.
My first coding was entering hex into a keypad attached to a Z80. No computer involved; prototype on paper, debug on chip. Not too much different these days… just using a fancier piece of paper (text editor) and keypad (USB -> JTAG adapter). Much better debugging tools, though…
IT does best in servicing the executives, the accountants, the contract writers, the salesmen, etc. I’ll give you that. But as for us engineers, thank you, but no thank you. We’re doing just fine on our own.
Is anyone here proficient at all in Casio Basic? I’m trying to make a simple factorial function on my Casio fx-9750G Plus…I’m using this code (I know it’s extremely messy, I’m still an aspiring noob):
"Number?"
? -> N
1 -> A
Do
((N*(N-1))*A) -> A
(N-2) -> N
LpWhile N>1
"Factorial is:"
A -> A
Any way to clean it up, you guys think? Or to make it so it would make the user re-input a number if they give a decimal or <1 answer?
Well…technically, the factorial function is defined for those cases as well.
Oh, and not knowing much about Casio BASIC, I can’t help with syntax, but a simpler way to implement the same approach would be:
"Number?"
? -> N
1 -> A
Do
(A*N)->A
(N-1)->N
LpWhile N>1
"Factorial is:"
A -> A
Wow, I was definitely making it overly complicated. 
Thanks, man. I love having those mistakes pointed out! 