4 ms·
Why not just build an editor that works off git? Then you could abstract it from the user and leverage all the existing ways of sharing text like github and bit
by newishuser 14y ago
Why not just build an editor that works off git? Then you could abstract it from the user and leverage all the existing ways of sharing text like github and bitbucket.
"But even as a developer it’s full of headaches." is also just plain not true.
- droz 14y ago> "But even as a developer it’s full of headaches." is also just plain not true. OP's statement is a subjective assessment. It's neither true nor false.
- alaskamiller 14y agoSee: http://prose.io/ http://prose.io/ Text editors is new hip. Saw ten launch the past few weeks. Before everyone made todo lists apps. Having that Bijan quote for social proof also rubs me the wrong way. Startuping is more insidery politics these days.
- nate 14y agoOh man, really? Sorry about that. It's just been very exciting to work on this. And that Bijan quote came from the very first user test I did on this with a complete stranger. I've had a lot of stumbles on new projects recently, and so that quote and other feedback I've gotten on Draft have been some very much needed motivation. And I definitely hope my stuff doesn't feel very insidery. I'm pretty open about stuff going on my blog.
- karthik_ram 14y agoExactly. I'm an academic who uses and promotes git (for research, analysis, and writing). My colleague and I are building a markdown editor with git support. We're going for exactly what you describe. git is abstracted from the user and they just provide GitHub credentials to have everything stored in a repo. Non programming types use the gui and programming types can directly interact with the repo. See (super early version) here: https://github.com/yoavram/markx https://github.com/yoavram/markx
- ef4 14y agoThat sounds great, I would love such a tool.