Markdown vs webapp2: What are the differences?
Developers describe Markdown as "Text-to-HTML conversion tool/syntax for web writers, by John Gruber". Markdown is two things: (1) a plain text formatting syntax; and (2) a software tool, written in Perl, that converts the plain text formatting to HTML. On the other hand, webapp2 is detailed as "Lightweight Python web framework compatible with Google App Engine’s webapp". webapp2 is a simple. it follows the simplicity of webapp, but improves it in some ways: it adds better URI routing and exception handling, a full featured response object and a more flexible dispatching mechanism.
Markdown belongs to "Languages" category of the tech stack, while webapp2 can be primarily classified under "Frameworks (Full Stack)".
What is Markdown?
What is webapp2?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose webapp2?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using webapp2?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
Markdown represents a highly portable and lightweight text formatting. I had converted all of my Wordpress posts to Markdown prior to migrating over to Jekyll and eventually to Hugo. The fact that many generators support Markdown means that my content remains portable regardless of the platform/engine I use.
What you see is not what you get, never it is.
Documentation is better in Markdown format. You don’t need anything special to read it.
It is compact, portable, comparable.
Markdown is my text file format of choice.
Because it is almost an effortless markup language without ever having to write an HTML tag. Of course, you'll want to use it in environments that make it look pretty (GitHub, etc.)
Using StackEdit to edit markdown files for blog roll and about sections. MD files are stored in Google Drive and pushed to GH pages through StackEdit.