Not enough, as I want other things to be indented. Also, the delete key in the leading whitespace doesn't fully emulate the correct behaviour.

Of course, the correct behaviour appears naturally and without any emulation if you use the right tool: the character.

That's part of the problem, not the solution. These half-functional 'features' makes people believe that somehow it's acceptable to indent with spaces instead of tabs.

Fact is, no editor can correctly read my mind as to when I want to indent and deindent when it's using spaces instead of the single character that was invented for the sole purpose of indentation:

unison (http://www.cis.upenn.edu/~bcpierce/unison/), BTSync (http://www.bittorrent.com/sync).

neither of these needs any "cloud" storage, just transfers efficiently between your machines. The first one is Open Source and easy to use: GUI, CLI, cron... The second one is free but closed, runs as a daemon and can be installed on several NAS boxes.

you mentioned: Blender, Maya, 3DStudio Max, Lightwave none of these is a CAD program. these are 3D modellers, great for creating images and animations, but not CAD

AutoCAD, SolidWorks, OpenSCAD and FreeCAD are CADs. that's two different software categories. The fact that both can be used to create 3D models is irrelevant; the kind of elements used by each category is different, so the production cycle is totally different.

it's more embarrassing to dream-type the commit message and get just wake enough to do "git push" so everybody can see it. (real story, less than a week old)

or Turbo Pascal

In '83 the Mac was anything but closed or 'narrow vision'. I was a huge leap in usability and programability. It was open to anybody who got the three-volume (soon expanded to 5 books) "Inside Macintosh", a great resource not only on the API but also a good primer on UI design.

Now, the last couple of Mac OSes, which are progresively tied to the app-store... and windows isn't far from that... currently, the easiest OS to install and configure applications is Linux, by a wide margin.

SMTP / IMAP. that's all.

As for software, it's usually CommuniGate or Zimbra on the servers. For clients, I support Thunderbird, apple's Mail.app, kontact, Eudora, and the included clients on iOS and Android and even Blackberry. all of them work perfectly together when using standard protocols.

There are a couple of big bosses that insist on using Outlook, even though they can't say a single reason to prefer it, it's usually just "i'm too old to learn something new". One of them creates by himself easily more trouble than the three companies where i'm involved in support. What seems to be helping a little is that we created an isolation server running Fetchmail to keep a copy of all his mail and accessed exclusively from his one Outlook machine. all his other devices (two iPhones, an iPad, one Blackberry and a MacBook) work without a hitch directly on the CommuniGate server.

that started reasonable enough, citing real issues that make it the only option to use Windows, Word and Excel. That much, I concede, it's not worth it to fight.

But I draw the line, and Exchange and Outlook are way past it. No way I would support either on my networks. Simply put, these are the real implementations of the first Halloween document. in other words, it's baitware that works "nicely enough", and with several well-researched features to make them attractive, but as soon as you want anything non-microsoft in your setup, they create all kinds of obstacles and hoops you have to jump. It's not that other systems don't "work nicely with all the above" it's that these specific programs were designed from the start to create those problems.

I agree that MS isn't the 'evil' it once was, but in the email space, it hasn't changed a bit. And it's up to us not to tolerate it.

huh?

https://www.google.com/search?...

30.0500 N, 31.2333 E
Cairo, Coordinates

Where I live we prefer our buildings not to fall down every couple of years. Granted, there are few ones more than 30 stories high, but those that are there have survived several sizable quakes.

note, these aren't brick and stone; reinforced concrete is all the rage... and not too good for wifi, even at 2.5Ghz That's why I make sure my wireless phone is 900Mhz and not 2.4Ghz

not only older houses, but also every solid house on places where the earth keeps moving.

yes

It _is_ quite reliable, even on the face of hardware failure.

Several years ago, I hit the 8TB limit of ext3 and had to migrate to a bigger filesystem. ext4 wasn't ready back then (and still today it's not easy to use on big volumes). Already had bad experiences with reiserfs (which was standard on SuSE), and the "you'll lose data"warnings on XFS docs made me nervous. It was obviously designed to work on very high-end hardware, which I couldn't afford.

so, I did extensive torture testing. hundreds of pull-the-plug situations, on the host, storage box and SAN switch, with tens of processes writing thousands of files on million-files directories. it was a bloodbath.

when the dust settled, ext3 was the best by far, managing to never lose more than 10 small files in the worst case, over 70% of the cases recovered cleanly. XFS was slightly worse, never more than 16 lost files and roughly 50% clean recoveries. ReiserFS was really bad, always losing more than 50-70 files and sometimes killing the volume. JFS didn't lose the volume, but lost files count never went below 130, sometimes several hundred.

needless to say, i switched to XFS, and haven't lost a single byte yet. and yes, there has been a few hardware failures that triggered scary rebuilding tasks, but completed cleanly.

Supermicro