We tested AeroFS and BTSync on a variety of data in shared folders, and consistently found sync issues with BTSync. We eventually abandoned BTSync for AeroFS, and while it hasn't been perfect, it's been considerably better at handling syncing issues.
Anecdotal, and just one case, but hope someone finds it helpful.
We have had the same experience. I loved the idea of BTsync, but we encountered too many issues. We tested sparkleshare and lipsync too. Unfortunately, none of them dealt with conflicts and merges as they were meant to.
BTsync would often not pick up changes (using osx and linux clients), and/or overwrite new files with an older version. It also had a slow latency when a file did change. As to the open source nature of it, you can supposedly limit its access to the shared servers through configuration, but this caused more sync problems.
These tests made us appreciate the Dropbox implementation even more.
Unfortunately, we need non-cloud syncing for our data, so I wrote a complex cron/rsync/inotify hack with its own issues - but at least we know the limitations and have custom workarounds. Personally, I hope BTsync will mature and be a feasible alternative.
That's starting to sound like a pattern on BTSync now.
What do you mean by non-cloud syncing? Have you tried Aero? I thought about doing a inotify/unison solution - apparently unison is good at dealing with conflicts and the like.
With all these syncing tools it's the uncertainty that causes issues. You're always worried about what data is going to end up where in the edge cases. As you say - at least with a few scripts glued together you know what's happening (and how to fix it if required).
Non-cloud = my clumsy way of saying operating on private servers with no 3rd party storage (and ideally no connection) necessary.
Looked into Aero, but I am pushing towards an open source alternative to be used, or at least where the implementation is fully controlled/configured by us.
I agree, unison is great and I think is the way forward towards a private dropbox solution.
Useful to know. I only tested btsync briefly yesterday and it wasn't picking up changes as quick as Aero. Again, single data point but I'd recommend Aero from what I've seen (and we use it all day every day).
This is correct. They also show when someone is a Vine reviewer (which is an invitation-only program), even if the product being reviewed was purchased, and not provided via Vine.
The conflict of interest argument will always carry some weight re: the Vine program, but Amazon seems to be handling it quite well. Anyone who doesn't like the program is given enough information to just ignore those reviewers.
• As a point of reference, the average price of a new car in August was $31,252. (That's a US statistic, but all I found.) The average cost of a bicycle is probably three-figures.
• Ownership of the two is not mutually exclusive.
• Usage habits of the two vary wildly, probably mostly favoring cars, not only because keeping an unused car is far more expensive and complicated than keeping an unused bicycle is, and because people don't tend to buy cars the first week of January to work off those holiday pounds.
On top of that, Apple's done more than any other single player (except perhaps Adobe!) to move the industry away from Flash, to open alternatives.
No, they don't always follow standards or always have open implementations, but their garden is arguably quite a bit less walled than the one in Redmond. Which makes your point a little confusing, at best.
Webkit was already open source before Apple started using it. ALAC was closed source until 2011.
Microsoft has released open formats as well, like XPS. And Microsoft does open source today as well. That's how the industry works today.
Sure flash is bad thing but if Sun had its way with the internet and Microsoft had not stopped them we be all doing Java applets by now.
However that's all beside the point, the point is that complaining against Microsofts closed culture and in the same sentence referencing Steve Jobs is like taking a bath in koolaid, regardless of Microsofts closed culture.
Sure, it had its roots in KDE's KHTML and KJS, but WebKit was started as an internal Apple project, and without their efforts it's highly unlikely that KHTML/KJS would have ever developed into the dominant layout engine.
According to the guy who implemented FFmpeg's ALAC encoder, there are power benefits to ALAC over FLAC. ALAC was developed when iPods were struggling to get 8 hours of playback, so it doesn't seem unreasonable that Apple's engineers wanted to be able to match the codec to the hardware as efficiently as possible.
I'd be interested to see your thoughts on each distro, even if it's just a sentence or two. Switching quickly, while obviously making some types of perspective difficult to develop in such a short timeframe, probably makes it easier for you to notice some things most people wouldn't through more typical usage habits.
I suspect there were other factors which prevented your success.
There were no measures to technologically limit one's ability to perform multiple installations from a purchased OS X install disc. You could buy two different Tiger installers and they'd checksum the same, and there were no serial numbers to be entered. It was an honor thing.
There was a restriction on VMs, but they've since eased up on that. I imagine it was because of the Hackintosh thing.
I'm reasonably confident the OS didn't actively try to detect that it was running in a VM, but VMware Fusion (and presumably other such software) would prevent you from installing the OS.
There was a relatively simple work around (a hack) that allowed you to install in a VM. I think it was as simple as touching the right path.
At the point that I was trying to solve this problem (and not getting paid as a result) I was unable to find anyone who had successfully gotten SL to run in a VMWare VM or Lion to run in a SL VM. Interestingly, I did find individuals who had Lion running in Lion VMs, but that didn't help me get back up and running.
Edited to add: You are correct, the technical restriction was on the VMWare side, but IIRC it was because of legal threats from Apple. Apparently earlier versions of VMWare would run SL without any problems, but the VMWare version I had would not not and I couldn't get a copy of the older version.
Anecdotal, and just one case, but hope someone finds it helpful.