You shouldn't feel embarrassed about how you pronounce LaTeX. In the words of its creator Leslie Lamport:
> One of the hardest things about LaTeX is deciding how to pronounce it.This is also one of the few things I'm not going to tell you about LaTeX, since pronunciation is best determined by usage, not fiat. TeX is usually pronounced teck, making lah-teck, and lay-teck the logical choices; but language is not always logical, so lay-tecks is also possible.
> Insiders pronounce the χ of TeX as a Greek chi, not as an ‘x’, so that TeX rhymes with the word blecchhh. It’s the ‘ch’ sound in Scottish words like loch or German words like ach; it’s a Spanish ‘j’ and a Russian ‘kh’. When you say it correctly to your computer, the terminal may become slightly moist.
Tuple is a mathematical term predating computers, and the "-tuple" suffix is older again, so pronunciation shouldn't be as ambiguous as the other, newly invented terms.
(It's historically rhymed with couple)
On the other hand, a lot of Latin-originating words have had their pronunciations changed in US English, the canonical example being data (from UK English "da-ta" to US English "day-ta", which has now begun to become standard everywhere due to the tech industry) so I guess other words could go the same way.
Your experience could be fact, but in about 10 years of using MacBooks for work, it has effected me about 2 times, yet I had way more issues with sound/graphics/sleep/projection/skype/internationalization on the Linux distros I have tried. I don't mean to start a flame war, but there is probably a reason you see MacBooks at linux conferences, and FS bugs are not a huge factor.
Those things preventing the system from being usable one way, or another. So, for my experience, worse than paper cuts. Not to mention there is a great idiom about death by paper cuts.
> HFS+ problems are a disaster. I lost 2 10 hour days of video edits and work and my backup were also garbage.
I haven't. No one else I know has. You're missing my point that this is anecdotal data. It's not a disaster if it's not impacting enough users.
> You know you are not seeing things clearly when you say statements like that.
You know you are not seeing things clearly when you think you know how clearly someone is seeing things. I know, for example, not to store Cyrillic music names on my MBP after I hit a bug. I have also read how bad HDF+ is, legacy wise. However, that's one factor of usability, among many. I've lost more raids than hfs+ files. Every filesystem has bugs, whether it's a huge factor or not is whether enough people encounter them or not.
Just do a little research on HFS+ issues. It is not a small problem. This was one of the reasons why the OS X server was killed.
Some limitations that really do have a major impact on people: (Features Missing)
data checksums
nanosecond timestamps
concurrent access (let more than one process at the time access the filesystem)
checksumming
snapshotting
longer time frame (February 6 2040 for HFS+)
sparse file support
real hard links
You lost a few hours of work because of Apple's probably-legitimately terrible filesystem. I lost days and days and days of work trying to configure Linux to just act sane and normal and do the right thing with my hardware. And I lost years and years of our only backups of family photos. We are missing all photos of our eldest son from birth until age 4 or 5, or our eldest daughter until probably 2 years old. I take some blame for trying to use Linux when I should have accepted the fact that it's only to be touched by gods-among-men, and this was back in 2007 or so. But Apple has not failed me nearly as badly as Linux has.
Well, not trying to be snide but your first problem is that you only had one backup of irreplaceable information. Storage is cheap enough nowadays that just about every computer should have some form of raid 1 or alternatively a NAS with raid 1 along with at least 1 or 2 offline backups.
$200 for 4 hard drives and some hardware in exchange for a near guarantee that data is never lost is worthwhile in my opinion.
Hell, for the more frugal there is an excess of cloud storage options out there that will be near impenetrable vaults for data. (that's not sensitive at least)
Basically, while the faults that both OS X and Linux have are definitely profound and problematic, they can be almost entirely avoided with nearly any data replication system, even just syncing to the cloud.
This happened over 10 years ago. I had three drives one with the archives one with the working files and one of the edits (Edits failed me). I had it in double redundancy backup and a on a second NAS. I even at the time copied to DVD. The problem was it happened right away but since my work was in memory it wasn't something I would see till the third day of pulling everything together for the final cut I found out that file system had failed.
I assume the OP strongly dislike HFS. I don't know enough about it myself, but I have relatively low standards for my dev machine - HFS has never failed me.
That's the official Vim repository, yes. There are a lot of contributors to Vim, but for consistency with the way Vim patches were handled before it had an SCM, changes are sent as diffs to the mailing-list and manually committed by Bram, rather than just being slurped into the repository with the original author information intact.
