What you haven't realised is the difficult part is automatically resolving sync conflicts.
Well, it doesn't seem to be a problem in the solution I'm currently using. Mind you, sarcasm>I probably have no clue how it works, given that I implemented it/sarcasm>. But you go right on ahead and keep telling me it's a hard problem. Difficult for you, perhaps, but not hard; there are a finite number of possible solutions and it should not be difficult for a well-built system to solve. True, Git (which I used as the basis for my solution) doesn't do a very good job of this natively; it took some creative and well thought out commit and merge hooks to accomplish it, a good day's work, for sure.
You are correct, though, that there is no one-size-fits-all solution for what to sync and how to handle merging of whatever does eventually get synched. But, then, I never claimed that there was; my claim was that the transport part of the equation is, and has been for decades, solved. Can you argue that point?
Earlier, you said:
They are file formats. They are not methods of handing off open documents between different devices without first saving them somewhere. Completely different thing.
And I didn't disagree. I did, however, point out that the documents are, in fact, saved somewhere (e.g. a temporary file, at the very least), out of necessity. I also pointed out why this was necessary, e.g. if you at all care about data consistency and preventing work loss in case of loss of power or a software or system failure. Can it be done without a temporary file somewhere local? Sure, and without issue, as long as you never lose connectivity or power while working, and your software and system never crash. If you live in a perfect world, you are correct to say that a temp file provides no benefit; however, neither I, nor anyone else I know, live in such a world. When you're using an all that utilizes cloud storage and the app crashes or you close it while you happen to not have any connectivity, it is able to restore your work only because it stored it in a local temp file somewhere.
What application(s) are you involved in. I would like to avoid them.
That you can't boot OSX on commodity PC hardware, which hasn't been blessed by Apple, is an artificially enforced a shortcoming of OSX, as Apple does actively work to prevent that. Were apple to remove the "genuine hardware" checks (which Chameleon bypasses) from the kernel, OSX would boot just the same on any PC build with supported (whether blessed or not) hardware. And, before anyone jumps on my for trying to make this a religious issue, I'd like to point out two facts:
A) I'm a Mac user and
B) "Blessed" is Apple's own term.
As I said in a different post, I don't seen an issue with their font choice, it renders fine, to my eye, on my 17" 1920x1200 display, but a number of other posters have expressed their displeasure; I was simply providing a viable workaround.
And no, the Mac Pro was not designed for video, it was designed as a high-end workstation which, yes, can be used for video; however, let's not limit its use-case to that. It can be used for whatever the displays and other peripherals you attach to it allow it to be used for. I've been eyeballing a Mac Pro since the new ones came out, and video is but one thing I would use it for.
The fact that the green button now fullscreens an application is another change I don't like.
Agreed. My workaround is an app called BetterSnapTool. I use the green button now when I want to fullscreen an app, but if I just want to maximize it, so I can still CMD+TAB switch applications, I just drag it to the top of the screen and BST does the rest. BST also lets me snap windows to one side, or corner, of the screen. I started using it when I got an LG UltraWide display, with plenty of room to have 2 windows side by side and retain usability, and have been finding new ways to make the app useful ever since.
Creatives will naturally gravitate to the best available displays, which means either the retina-class iMac or MBP, or the Mac Pro and whatever their display of choice happens to be, and Apple definitely has them covered. Helvetica looks just fine on retina displays (honestly, I think it looks just fine @ 1200p on a 17" display, too), so these users won't be likely to complain.
They sell the most expensive hardware to the group least likely to buy a lot of apps and media from Apple, and I agree, that's the way to go. Users of iOS devices have voiced that they want the look and feel of their iPhone, iPod, and iPad everywhere they can possibly get it. Well, those use Helvetica, they also use flat neutrals, transparency, and blur. Apple catered to those users, who are likely to buy the cheaper computer and spend more on apps and media, without a second thought.
If you're not in those two categories or, at least, don't follow either of those spending patterns, I won't say Apple doesn't care about you at all; they certainly care about anyone who wants to give them money, just just don't care enough to give a shit what you want.
Again, I fully agree with this from a business perspective. Unfortunately, I have my own business, which comes with its own perspective, and if that's the view Apple wants to take, it's sadly incompatible with reality for a lot of professional users. It really saddens me, as they were making strides toward developing a huge presence in professional fields before Jobs passed; that has not only slowed, but reversed, since then. It doesn't seem to be hurting their sales, yet, but I imagine it will when they start making more obviously negative changes to OSX's UI. They'll still sell to iOS users and creatives, and they'll probably remain the college student's PC of choice; but, by crapifying the interface (observation of others in this thread, which I've already stated I don't necessarily agree with -- but, me vs them, they're the majority, so I'm using their opinion for my point) on lower-end-but-still-current hardware, which the mass market is more likely to be able to afford when they choose to buy Apple, they're removing much of the allure of their platform. This can't be a good thing.