It doesn't let you use Markdown by default as a seamless input method like Typora[1]. This editor seems much less productive as you are forced to use your mouse to click on GUI elements.
It does not force you to use mouse click on GUI elements. You can use `⌘`+`/` (or `Alt`+`/` on Windows) to switch between WYSIWYG/Markdown modes. Actually it's the preferred way unless you are on mobile devices.
The default mode is WYSIWYG since Markdown syntax frustrates people who don't know Markdown well.
Thanks for mentioning Typora! It's an interesting implementation. I've thought about that approach (in-place real-time preview as you type Markdown text) before, but inside a browser, it's too cumbersome to fight against the inconsistent contenteditable behavior.
Yeah, European keyboard layouts are annoying like that. Too bad that it seems unlikely that they would ever change even if there is some talk in France that they want to reform their keyboard: http://arstechnica.com/tech-policy/2016/01/france-says-azert...
There was a project in Finland to reform keyboard layout ("Kotoistus"), only thing they managed to do is to add more dead-key accents and make the keyboard even more annoying to technical users. In all their great wisdom they decided to add non-breaking space character to altgr-spacebar key combination. In isolation that might seem like a good idea, but when also | character required the use of altgr-modifier it was a mess: working with the command line, you tend to have stuff like ... | grep foo. Soon enough there were plenty of users wondering why bash complains that grep is not found: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/218637
Personally, I have abandoned national keyboard layout and adapted US layout instead. Makes both programming and general use much more comfortable. Its amazing how much less I need to use modifier keys now, especially the painful altgr.
The French project would be even worse for us French coders.
Symbols used for code would be hidden behind several layers like altgr combinations. While, imo, archaic symbols (ÇÀÉÈàçê, etc) would be on the first layer.
I'm planning on doing the same as parent, using the US layout, but I can't change my keyboard at work, and although I can type in qwerty, I don't know all the layers like I do azerty, so I can't just type without looking.
The default mode is WYSIWYG since Markdown syntax frustrates people who don't know Markdown well.
Thanks for mentioning Typora! It's an interesting implementation. I've thought about that approach (in-place real-time preview as you type Markdown text) before, but inside a browser, it's too cumbersome to fight against the inconsistent contenteditable behavior.