Some want rendering-agnostic structure, like Wiki / Markdown / Org mode, that emphasizes structure and text, with things like links, tags, etc.
Other want to print centered headers on level 1, and left-aligned for level 2, and body text with a particular font, with fragments in a different color, and pictures with text flowing around them, etc.
These two camps command different design goals. A format that makes one of these easy adds complications and edge cases to the other.
The funny thing is, the same people periodically need one tool and the other, and even want to mix them. Many of them would consider having two tools for these jobs superfluous, especially if paid. They'd rather bend an existing tool, because how hard it is to add spans of colored text? or collapsed sections? It's, like, a hundred lines of code!
Hence the modern office formats, tolerably doing a huge spectrum of things, none of them brilliantly, and hopelessly complicated.
Also, you can export from Paper to Markdown or docx. I've written a few of my github READMEs in Paper and then exported to Markdown and they've worked just fine.
The examples you've mentioned (ctrl-i, ctrl-b, insert hyperlink) all work just fine, as does pasting markdown directly into the editor.
-- I have nothing to do with Dropbox, except as a happy paying customer and a happy Paper user.
That way you could build simple, easily distributable multimedia documents and web apps.
That is, until requireJS/AMD/angular/react/backbone/etc and those sorts of things started polluting the web. Thanks you JS developers.
So the problem is when I try to edit them on a new computer or even online, there's no way for me to do it in most cases, and in when I actually can install packages for all that, there's some dependency management I have to do. One more thing, since the output in HTML file, I have to again use a full-featured(which means slow to open) web browser to render the HTML file.
How should whatever tool you're using handle the case when another person is editing the document at the same time as you?
A quick google shows some results which look like pet projects of small business which have obviously failed (since I've never heard of them before)
All of these new document formats that are pushed by big companies (some are really great I actually love using Google Docs) try to tie the user as close to their eco-system as possible.
When ever I try to maintain documents for long term storage, markdown seems like the only good format. I've seen people talk about stuff like org-mode, etc, but they all lack the fluidity and the WYSIWYG nature of Google docs, docx etc. I'm talking about how markdown never actually stores pictures inside the document, but just links to them, and you'll have to use a specific application to view the rendered markdown, and a different one to edit or make new ones.
I'm interested to see that does everyone else use for documents? And please don't suggest docx+open/libre office. I'm still waiting for some of those applications to properly handle a big file and I don't want to wait so long for those applications to even open.
EDIT: Thanks for the replies. I think I should clarify something. I'm looking for a WYSISWYG tool, like google docs/docx. I don't really have time to spend doing the edit->render->see where you went wrong->edit cycle. This really hurts productivity when you're editing large documents and increases the barrier for new comers. I do use LaTeX but only when I need ultra sharp looking documents with specific needs. I really like it, but only pull it out when I need to write a paper and want the output in PDF. Other times, it's really not worth the effort.
So formats which require me to render to HTML etc, are a no go. I'm looking into ASCIIDOC but even that looks like it's very similar to markdown. And by WYSISWYG, I mean I want to type, and press Ctrl+B to write in bold, and Ctrl+I for italic and right click to insert hyperlink and so on. Not use asterisks everytime whenever I want to make something bold. Sure it transparently to that in the background, but I shouldn't have to worry about it.