at home i only use linux (debian) at work i have a windows 7 machine with debian VM, i just spend all my time in the VM and i rarely ever have to even know windows 7 is there. between linux base with windows vm vs windows base with linux vm i would say...it depends on what you want windows for. if you want to play games, windows base. if its just dev linux base. i have a windows XP VM on my work machine as well which i use for windows development, its served just fine, dev isnt all that resource intensive nor graphic intensive so a VM can do it just fine

i like c# to an extent. likes: * its kinda like c, i like c. i can use my knowledge of c to divine ways of doing things in c# to an extent. * it's managed-ness makes intelisense work nicer...to an extent (then it starts to drive you insane to the point that you turn it off, like the passive aggressive spellchecker on your browser. dammit i will add that function later, I'm working on this! stop with the judgmental squiglies!) hates: * JUST LET ME MANAGE MY OWN MEMORY PLEEAASSEE! not to long ago we hit a wall where we needed to use 3.5 over 4.0 framework for compatibility with a linux server, but we needed bigINT to manage really big bits for integers, with memory management i could have used malloc to allocate the appropriate bits, then implemented the arithmatic using bitops on that memory block creating a bigInt class. but not being able to malloc that was impossible.not to mention the lack of control over when an object is unloaded (making the destructor nearly useless) * the need to use a third party obfuscator. its generally true that machine code is readable for code compiled in c++ or most any language compiling to machine code, but that requires someone well versed in machine code...CLI can be read by a decently well versed 3rd grader. where you gonna put that decryption key now huh? if you work in any language that compiles to CLI, you have open sourced your software. * everything throws errors when it fails! maybe i dont know if the website is available before connecting, if i dont want my program to crash i have to enclose it in a try catch, opposed to how c does it, return -1 and set stderr, i can just check for -1 and check stderr for the reason if i care. and maybe try catch wouldn't be such an issue if it weren't so frikken slow, my program has the choice of crash or put try catch everywhere, and just about everything throws errors for the stupidest reasons and if you have a large section in a try catch block, enjoy only getting half way through the block so you have to litter your code with try catch for any significant activity slowing it down ridiculously. * their general "we know what's best for you" approach that permeates the entire language. these arent minor things that can be fixed but underlie fundamental design decisions in the language. c# is great up to the point that you are doing something microsoft didnt consider you doing, then its just a big "NOPE!"

i use shift+insert all the time because im a linux user so im used to pressing shift+insert to paste into a console. as for microsoft's arrogance, they keep claiming they are the most HTML5 compliant web browser, but only get a 135 on html5test.com, mobile browsers score higher. all other current browsers score higher. hell most of the last generation browsers scrore higher. MS, just open source your browser already, seriously we can fix it...we have the technology. better than it is, faster, stronger, more reliable.

oh much too often do i do that. and trying to send an email with ctrl+d in kmail or outlook(if im at work)