This could also be payback for the IE:Mac years...oh Jesus, the flashbacks.
Why, he's obviously Logitech's Mouse Evangelist
(3) The Windows APIs for device arrival notification suck and require polling rather than blocking a thread to wait
IS the funny part?
Somewhere in Apple is the notion that everybody everywhere always uses a mouse. By default, only certain controls in OSX are "tabbable" - as in highlighting a button or dropdown with the tab key. This can be changed in accessibility options, but it should be on by default IMHO. Your issue seems like it was an oversight - people who use Macs all day don't notice that Windows, by default, tabs to every possible control in the UI instead of just the "necessary" things, or they don't care. As mentioned before, iTunes for Windows is just crap in general, but Apple knew that there largest market was in Windows users because they don't see OS users or brand loyalty, they see consumers.
Or, it's just for convenience - I'd wager that about 80-90% of iDevice users expect iTunes to open when they plug-in. They likely have docks, chargers, or other such things that handle charging the device and are planning on doing *something* with their device and iTunes when they plug it in. This all stems from a very old MP3 Player (remember those things???) mentality that the industry had back when the RCA Lyra was something you could buy - plug in the device, open the software. When you can make your software open automatically, it means you're reinforcing the notion that the user should use your ecosystem for purchasing, syncing, etc. The only thing is, iTunes is the only thing that survived and Apple has continued to have the software operate in the same way out of 1) habit and 2) marketing knowledge. That whole "reinforcing the ecosystem" is a big part of iTunes - get your music, TV, videos, podcasts, apps; everything - here. It's not about them trying to say "we know better," it's them saying "we know we can open this automatically every time and you won't do a damn thing about it, heck, you probably won't even complain."
So, you have your opinion too - why not just disable the service and quit being so butthurt?
What about religious people whose lives revolve around the religion and they try to convert others to the religion?
The same answer applies:
In short, you can like Jesus all you want. But when you go so far as to modify your life such that it now revolves around that person, and you feel compelled to convert others to your religion, then there is a problem
Windows Blue Screen Death?
I think "of" is, technically, a word.
Well, for those with anxiety, the causes and roots are many. The "hopelessness, burden to others, loss of sense of dignity, desire for death or loss of will to live and threats to self identity" can be common to people with symptoms that affect their anxiety - paranoia, for example, can create a feeling of hopelessness that breeds anxiety over obsessive thoughts such as "I'm terrible at my job" or "I'll never get better" - these thoughts can be attributed to the paranoid delusion that there is an active force of the universe out to get you - these thoughts feed more anxiety and a loop is created.
Anxiety can readily be triggered by external forces and perceptions, existential distress is by no means exempt from that.
Some of the best self-discovery I've had was using
Good luck with the book! Keep me posted if you would, I'd like to give it a read.
I don't know if LESS has this, but with SASS and Compass, you can tell Compass to "watch" your SASS folder - when any files change, it automatically rebuilds your CSS. Quite nice for actively working in the SASS without having to go back and recompile every dang time you change something.
On the dev side, all of our SASS is compartmentalized into partials for that particular section "_toolbars.scss, _article.scss, etc" Our local configurations are set to compile the SASS to expanded CSS, complete with annotations and line numbers so we know which rules originated in which source files. When we finally deploy a project, the build script tells compass to generate a compressed CSS file, as well as splitting our our media-query specific styles and styles just for our subsites and IE.
We looked at LESS, but we wanted more. *ba-dum*
It's crazy, but SASS and LESS also deserve to stay in their own separate play-place for now. It's important for these to continue to expand and develop, but in both camps there is constant movement and redesign, no clear stability, and no clear path of where certain features will lead. CSS, on the other had, is generally solid and not often updated. It has to remain rather slow and boring in order to maintain support for all the browsers and designers and companies who are relying on said stability. Variables would be nice, but even adding something simple like that has the potential to raise a ton of questions about implementation, and we all know that the W3C isn't the fastest on the planet when it comes to that stuff...
The only way we aren't running out of oil is if we stop extracting it or can't extract it because it's just not accessible. Given enough time and resources, we can exhaust all of the oil available to us on the planet. If we develop alternative methods of energy production that don't break the bank and they eventually replace oil-based energy, then we may not run out of oil but we won't need to worry about it either. Of course, the old rule applies:
Q: What if we don't run out of oil?
Started on a 486 with win 3.11, upgraded to '95 (had to buy a new gfx card to support all the colors!). Dug an old Mac out of the trash at my middle school, didn't get far. Then, 95, 98, lots of Linux, XP. Used Linux throughout college, ended up on OSX after getting a hand me down iBook and eventually piecing together an old MacBook.
I recommend Linux to everyone I can unless they *need* to spend the money, and then I suggest OSX. If its gaming...get a console ZING! Even the 360 is great compared to the general "ugh" of Windows.
...and if the connection breaks or anything happens, you'll have to restart copying everything from the beginning.
Interestingly, rsync can even resume a transfer that was started by scp but then interrupted - neat!
rsync only does incremental copies when you tell it to, and, technically, the same thing could be achieved through ssh and scp (using ssh to check for the destination file first and then copying with scp if needed). Of course, rsync does make it easy; just because it's easier doesn't mean it's not technically possible with scp