MacDown holds its own ground now, and should continue to survive as an free (as in freedom) option toward Markdown editing. I don’t have (more) “philosophical axe to grind with the author of Mou”, and the author of Mou did not tweet the specific tweet mentioned. At least my own crappy clone has unique features Mou doesn’t offer, and they are useful to some people, including myself. But so are a bunch of other softwares-Just search for “Markdown” in the App Store. MacDown is still fundamentally the same with Mou-they are both macOS-specific Markdown editors with an instant preview pane that can be styled with CSS, and offers syntax highlighting in the editor. They should change their descriptions to “Stole the idea from XXX, and let everyone make crappy clones.”Īnd changed the project description accordingly.Īnd that’s the end.
Literal translation: Those who clone and open-source softwares “inspired by XXX” should all go eat shit. 那些 “Inspired by XXX”，克隆，并开放源代码的人都应该吃屎。他们应该将 Description 换成 “Stole the idea from XXX, and let everyone make crappy clones.”- Sean Cheng July 4, 2014 So I took this advice (which is not tweeted by Chen Luo, the author of Mou, I should note): Now, nobody would be happy being called a copycat, but I did copy his idea. Obviously he felt offended, accusing me being a copycat. Things went well until Luo found out (if that’s the right expression) about MacDown. But I didn’t think that much at the time, and just went on publishing the initial version of MacDown. Looking back, maybe I should’ve been more explicit. I was asking about editor styles, but Luo’s said CSS which is used in HTML.I mentioned that I was building a Markdown editor, but not exactly what I intended to do.Luo: Yes, you just need to put a notice that the CSS came from Mou, and attach a link to Mou’s homepage. Me: I’m building a Markdown editor, and I like the PEG highlighting styles in Mou a lot. So I contacted Chen Luo and asked whether I could re-distribute his themes and styles. Most things went smoothly enough, but I still lack some good-looking editor highlighting colour schemes and CSS for the HTML output. I spent two weekends putting together MacDown. (Well turns out it’s not easy either, and MacDown still isn’t as good as I wish. It’s just a text view, an embedded web browser, a Markdown-to-HTML engine (there are tons of those available on the Internet). I looked for alternatives to Mou, but there are none (no free ones, at least), so I decided to roll my own solution. There aren’t further campaigns trying to sell Mou after the initial failures, and according to various tweets on this issue development is now alive again. Some supplemental comments might be necessary here.
MOU VS MACDOWN UPDATE
Mou didn’t (still haven’t) receive an update since September 2013, and there were efforts made trying to sell it. You know what happened next (take a look at if you don’t). Which made Mou far from ideal for technical articles. I illustrated some problems I had in a blog post (in Chinese) when I launched MacDown: I included a Markdown-based publishing system inspired by Logdown and Ghost, and started writing even more Markdown documents.
Last year (2013) I built my personal website/blog. The more I write on GitHub, the more unsatisfied I became. But that was also the time when I started using GitHub. It was fine for the most part, being standard-compliant, steady, good-looking, and simple. I was a long-time Mou user (since late 2011, I think) before starting MacDown. I’ll try to go through some things that happened in chronological order so that you might get a better idea why things are how they are now. There seems to be some confusion about the origin of MacDown, and its relationship (if there is one) to Mou. Ah well, I get the clicks, and that certainly isn’t something to complain about.Īnyway.
This time as a Show HN-Wait, I though Show HN is for sharing something that you’ve made? I don’t recall myself posting anything on HackerNews. MacDown showed up on HackerNews yesterday again.
0 kommentar(er)
