That isn't really comparing like for like though is it, given LightPaper is _only_ available for the Mac, is a paid app (inexpensive, yes, but not free, and the site says nothing obvious about future update policies), and not open source.
If I want to make chips, fries, wedges and jackets, the fact that a cucumber has far fewer calories and goes really well in a tuna sandwich is, while true, hardly relevant!
Lightpaper looks like a fantastic markdown editor! But the landing page makes me feel like it isn't getting much love from the developers. The copyright notice at the bottom, for instance, says 2019.
Gtk isn't tied to C++ or Java in any way. While Qt and wxWidgets are written in C++, they aren't heavily tied to C++ either. For all these toolkits, bindings for many languages exist.
Is there something wrong with running a local web server and opening the app in a browser tab? Not my area of expertise, so maybe it would have its own set of issues.
The issue for Electron is making sure the right version of Node and Chromium are available which is why each app is so big: each apps includes the version of both that they were last dev&tested against. That is why running several eats a fair amount of RAM - they have full Chromiums running, not sharing anything between them even if they are the exact version.
> Is there something wrong with running a local web server and opening the app in a browser tab?
For the average user, probably. Though for a developer targetted app probably not IMO.
For a dev, running a new enough version of Node (but, for not well maintained apps, perhaps having one that is not _too_ new around) and making sure you have a recent enough browser, is not an issue, but for beginners or completely non-technical users that is a barrier to using the app.
As access to local resources from within the browser is getting practical, I think the best common ground will have to be two versions from (mostly) the same source: a pure JS version that someone who can follow the instructions can run using already installed node and the same browser instance they use for everything else, and a memory hungry Electron version for others to install just by downloading the huge installer. And of that first version can be run as a service, or perhaps there would be a third version with extra parts not needed for either local version for that, for those who don't want to install at all.
Maybe at some point OSes/distributions/appstores will go with “we have this LTS version of Node and this LTS version of Chromium, otherwise provide your own”. That way devs could release a full cross-platform version of their app (Electron with all the baggage), and streamlined versions (no Node, no Chromium, just the app and any extra supporting libs) for Win10, Win11, Debian11, Ubuntu20.04, ..., that have been tested against the versions included with those OS options. Appstores would always get the streamlined versions because they can make sure the right version goes to each OS version they service. Perhaps there would be a combined installer: still huge as it contains everything, but it only installs and runs the app+libs if the target's standard backend & browser are found to be compatible.
You wouldn't need to use Node if you're running it locally. It could be in any language, and in my experience, Node is in the tail for being bad about requiring specific versions. If you write it in Go, for instance, you don't have those problems.
No, I would argue you're not. The runtime destributables for .NET and Java are not bloated like Electron. Python is worse however it's a already a built-in part of many system's package ecosystem.
Unfortunately this doesn't seem to be actively being worked on and isn't complete enough for me to use personally (custom themes aren't implemented, for example).
These are the WYSIWYG Markdown editors that I am aware of:
I know it's quite heavy but for performance, consistency, and attractive rendering (surprisingly important) having tried many options, including my personal runner-up Byword which hasn't been mentioned, I settled on the usual suspect of VS Code. Usually with the Github Markdown extension switched on due to liking their theme, but obviously that isn't a requirement.
Open a Markdown file and use your platform's Markdown Preview hotkey (eg Cmd+K,V). Simple.
I wish I could consolidate a lot of the apps I use for Markdown:
Blog: I used Vim for a long time, now I use the online editor https://stackedit.io. I found that composing blog posts involves cutting and pasting big blocks of text a lot more than coding, which is better done with a mouse. Stackedit has a side-by-side view and WYSIWYG.
Github wiki: Good for sketching ideas for blog posts, and documentation. Editable by others. (wish list: I kinda want the Roam Research bidirectional link thing, I often have that problem)
Github issues: similar to a TODO list for many people.
Zulip: Good for chatting with others, and for brainstorming ideas. So it overlaps with the Github wiki for that. Not good for a TODO list.
So there are all these apps that use Markdown but they are a bit disconnected.
Is that what Notion is supposed to be? A bunch of apps that interoperate and are unified? I haven't tried it since I mainly stick to open source stuff (with the exception of Github, though it is built on git)
I've been playing around with it this morning, and ended up spending $14 on the license. Used it to go through some of my README.md files that I had some mistakes on. https://typora.io/
Edit: A commenter below says this is no longer free
Since we're here: I highly recommend Typora for macOS. Truly minimal and well-done macOS-native Markdown editor. Previews final output inline as you edit without separate markdown/preview panes. Beta is free. (Not my project)
No, Typora is an Electron application, occupying more than 200MBs on disk (and similar amount of RAM upon start with no documents opened). See this announcement for example: https://support.typora.io/What%27s-New-0.9.66/
Visual Studio Code is a fantastic cross-platform Markdown editor, especially with a few extensions: markdownlint, Spell Right, Word Count, Markdown All in One, and docs-markdown.
Isn't the point of Markdown that it is supposed to be regulartext, formalising conventions that have been used for traditional ASCII text files for decades?
Sure, but the point is also to render said ASCII into something a bit more slick and dynamic. These editors let you work with the underlying markup, while showing you the final product. In fact, this is the way I wished all word processors worked—the worst thing about MS Word in my opinion is the invisible hand of the phantom formatting characters.
Leaving aside the well-known and commented "features" of Electron, out of interest, I looked into the most prominent Markdown file in the repository, README.md. Huh? Where is the markdown? Scroll, baby, scroll… This is disturbing for a Markdown editor and does not leave a good impression, again, feels like more emphasis is put on appearance than substance. Which brings us back to my entry sentence, Electron and its reputation...
Personally Obsidian has my heart. Not only does it support HTML and CSS snippets but the community behind it is insane. They're lovely people and the shit they do with Obsidian is absolutely incredible. The plugins are absolutely amazing as well. They basically make Obsidian what it is.
I don't mean to derail the thread, it's just that when I see "Markdown" I think "hhhhh obsidian my beloved"
What I'd love to see is an extension for VSCode that can do wysiwym/wysiwyg Markdown editing while keeping the same keyboard shortcuts of VSC.
There is a "Typora" knockoff extension for vsc that does some of what I want, but it has its own keyboard shortcuts, so multiline editing, etc. don't work.
