When comparing LightPaper vs IntelliJ IDEA, the Slant community recommends LightPaper for most people. In the question“What are the best Markdown editors for OS X?” LightPaper is ranked 21st while IntelliJ IDEA is ranked 23rd. The most important reason people chose LightPaper is:
Can be extended to support Multimarkdown, GFM-style code fences with syntax highlighting and even math rendering.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Extended markdown support
Can be extended to support Multimarkdown, GFM-style code fences with syntax highlighting and even math rendering.
Pro Advanced file-management built-in
Can browse and open files and even has a built-in fuzzy file search.
Pro Built-in preview
Pro PDF & HTML export
Pro Your own preview template is supported
You can create your own template that is aligned with your branding.
Pro Great Java Support
Pro A good editor for test-driven development
IntelliJ IDEA is really easy to work with when it comes to test-driven development in Java and JavaScript/TypeScript.
Pro Great JavaScript support
Pro Markdown support with preview
Pro Supports PHP quite well
Pro Great TypeScript support
Really good support for importing classes, libraries, etc. into a typescript class. Making it easy to do TDD.
Pro Good BASH script support
Pro Angular CLI support
Pro Made by developers for developers
It can make one more efficient, but also can get one way too used to shortcuts, autocomplete, and easy debugging.
Cons
Con Crashed repeatedly and refused to open without crashing after theme installation
Con Spell checking needs to be activated every time you open a file
In order to activate the spell checker you have to do so every time you open a file in LightPaper. There's no way to leave this setting on by default.
Con Is not free
But it does have a free version (Community Edition).
Con Heavy
Consumes more resources than VSCode etc. But depending on your use-case, it can still be worth it for the benefits you get with this editor.
Con Autocomplete does not work while IntelliJ is indexing
But this, in general, is not much of an issue. Usually after npm install, etc.
