I would argue that women are genetically predisposed to perform some tasks better than men, while the same is true for men as well. I know none of my girlfriends ever got me pregnant, or even given me a pregnancy scare!
It's a shame they differ. But let's face it, actually having Foo.bar and foo.bar, or worse still Foo.bar and Foo.BAR in the same directory is a silly thing to do.
I agree that it is not a best practice, but I have dealt with this issue before. Usually caused by someone who doesn't realize that they're dealing with a case-sensitive filesystem.
Downgrading an OS by a major version is asking to break it. The upgrade scripts will normally change various datafile formats and contents. That's not a reversible process unless there are equivalent scripts to go the other way. And what OS developer is going to put the same development and testing effort into going backwards?
Thats not to say that you can't in GNU/Linux. GNU/Linux lets you tinker with most things. But it generally offers no protection from breaking everything when you do so.
Of course the right thing to do regardless of platform is to make sure you do a complete backup before upgrading, so you can go back to that if you want to.
Go ahead and try to wipe the entire drive and then install an older version of MacOS. Put in a new drive and try to install an older version. They change something - I don't know if its in the SMC or something, but it will give you an error. I do not mean downgrading the OS on top of an existing install. I mean a fresh install of an older OS.
My Mac has been set up to be case insensitive. LS, GrEp, cAT, TAIl all behave as if they had been typed lowercase.
So? Why is this an issue?
Linux filesystems are, by default, case sensitive. I can have Foo.bar and foo.bar in the same directory. If my source control is set up properly, I can see and work with both files properly on Linux but not on Mac OS. You can use a case-sensitive filesystem in MacOS, but last time I tried the OS itself was very buggy and unpredictable when dealing with files. Perhaps this has been fixed since 10.8, I don't know, but the general rule of thumb is to NOT use a case-sensitive FS on MacOS.
These Ars OSX reviews have always been really impressive things, full of technical examination and as you can see, very long to write...
It made more sense to me back when you had to pay for an upgrade though, so you could see if it was worth getting. Now that it's free, the need for long technical examination seems to diminish...
That said I hope they keep doing them because it is nice to have a deep technical examination of what is new.
Apple makes it very difficult for the average person to downgrade after you upgrade OS. If you try and run, for instance, the Mavericks installer after having upgraded to Yosemite, it will fail and tell you to install a newer version of OS X. There may or may not be a way around this, I've never tried.
Good point. Now we need to exert the same pressure on Google for Android support for external devices and regular-ass USB storage device mode for connecting Android devices to hosts.
Google started requiring Android File Transfer for connecting Android devices so that the phone would not need to unmount the drive before allowing the host to mount it. I'm sure they could have come up with a better, more native adaptation to this, but it is what it is.
You cannot prevent an American citizen from returning home. However, a mandatory, no exceptions 60 day quarantine would have worked (60 days from departure of affected country).
Who is going to pay for that, the traveler? And do you realize that the absolute longest it would take to diagnose someone with Ebola is only 20 days from exposure? So why keep them quarantined for an additional 40 days? Perhaps you should do some research on the illnesses in question before you start suggesting solutions to prevent its spread?
Even with the best password, memorized or securely stored doesn't protect you against a password recovery process that's improperly engineered. Often an institution, even a BANK, will give you as a recovery password a choice from perhaps six possibilities, any of which can be divined from publicly available information or a little social engineering. Your password may be q4ot38yhewa;okl, but your password recovery phrase will be the street you lived on in high school or the name of your first dog. This is not secure.
No one says you have to be honest about these answers. I never put the correct answer for those questions, but have a list of fake answers that vary based on the question. Granted, if someone were to figure out one of my fake answers, they may be able to reuse that on another site, but at least they can't log into ancestry.com or look on something like an intellisus report to get my info!
How does one get the job of "editor" exactly?
It's only two more steps than those required to get an insightful post on Slashdot:
1. Forget Everything you know
2. Loudly opine on everything you think you know
3. Sensationalize everything
Not going to happen unless it's legislated. You can't trust the calculation given by the cars, and the automakers absolutely do not want every car to track this since they leave themselves open to lawsuits when the numbers don't meet whatever was advertised. For example, the readout on my car gives L/100km but it's rounded to the whole number! So it's useless even if it was accurate because the precision is gone.
The real issue here is that those numbers depend entirely on how the end user drives the car anyway. I used to own a Subaru Legacy GT LTD, with a turbo. The stock 0-60 time was 4.9 seconds. It could take off in a hurry. When I felt like being a bit on the sporty side, I would often get an abysmal 14-15MPG. If I were feeling a bit more conservative, I could easily get 24MPG in the same conditions. If I drove especially fast on the highway, I would get 21MPG. If I drove conservatively, I could get 28MPG. So you can't just use real world numbers because those can be fudged just as easily.
Just to run the OS requires 1GB of ram?
No. To run the OS and do anything meaningful with it, you need at least 1GB of RAM. If they listed minimum requirements of 1GB and that was strictly for the OS, you would not be able to do anything useful with the computer if you had the minimum specs.
The big issue is when you get to "1 cup of flour" or "1 cup of butter" - things that are much more easily measured by mass,
1 cup of flour is trivially measured by volume: Just grab the "1 cup" cup from your set of measuring cups, scoop up flour from your storage container, level. You're done. If you're using measuring cups, you can make a batch of cookie dough without using a scale or having to look at the actual measurement.
US recipes usually don't use "cups" of butter, they use "sticks" of butter. If you live where butter isn't sold in US sticks (113.4 grams), you're screwed.
You're so wrong. Some recipes require sifted flour. Some recipes expect you to pack that flower in nice and tight. It depends on how precise they need you to be with the flour. You can completely ruin a meal by not sifting your flour when called for. The volume in your measuring cup depends on exactly how much air is between each individual flour molecule.
A lot of comments here saying how Obj-C is "ugly", and so forth. I wonder how many commenters are actually using it to any great extent, on a day-to-day basis, rather than have just looked at it out of curiosity for five minutes?
I write in Obj-C every work day and I do think its ugly. The function syntax with crazy long names gets tiresome. If there were no tab complete, Obj-C would be one of the most time consuming languages to write in. I also wish that I could have things like pure virtual functions instead of or in addition to protocols. I also wish that I could make properties protected instead of either public or private. It's not the ugliest language, but it's not my favorite.