Need advice about which tool to choose?Ask the StackShare community!
Markdown vs VBScript: What are the differences?
Markdown: 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; VBScript: An Active Scripting language that is modeled on Visual Basic. It is an Active Scripting language developed by Microsoft that is modeled on Visual Basic. It allows Microsoft Windows system administrators to generate powerful tools for managing computers with error handling, subroutines, and other advanced programming constructs.
Markdown and VBScript can be categorized as "Languages" tools.
What is Markdown?
What is VBScript?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose Markdown?
- Intuitive194
Why do developers choose VBScript?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Markdown?
What are the cons of using VBScript?
What companies use Markdown?
What companies use VBScript?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with VBScript?
Sign up to get full access to all the tool integrationsMake informed product decisions
CodeCarrot
Jekyll is an open source static site generator (SSG) with a Ruby at its core which transform your plain text into static websites and blogs.
It is simple means no more databases, comment moderation, or pesky updates to installโjust your content. As said earlier SSG uses Markdown, Liquid, HTML & CSS go in and come out ready for deployment. Lastly it's blog-aware permalinks, categories, pages, posts, and custom layouts are all first-class citizens here.
For Stack Decisions I needed to add Markdown in the decision composer to give our users access to some general styling when writing their decisions. We used React & GraphQL on the #Frontend and Ruby & GraphQL on the backend.
Instead of using Showdown or another tool, We decided to parse the Markdown on the backend so we had more control over what we wanted to render in Markdown because we didn't want to enable all Markdown options, we also wanted to limit any malicious code or images to be embedded into the decisions and Markdown was a fairly large to import into our component so it was going to add a lot of kilobytes that we didn't need.
We also needed to style how the markdown looked, we are currently using Glamorous so I used that but we are planning to update this to Emotion at some stage as it has a fairly easy upgrade path rather than switching over to styled-components or one of the other cssInJs alternatives.
Also we used React-Mentions for tagging tools and topics in the decisions. Typing @ will let you tag a tool, and typing # will allow you to tag a topic.
The Markdown options that we chose to support are tags: a, code, u, b, em, pre, ul, ol, li.
If there are anymore tags you'd love to see added in the composer leave me a comment below and we will look into adding them.
#StackDecisionsLaunch
I needed to make stack decisions accept a subset of Markdown, similarly to sites like Reddit or Stack Overflow.
I used the redcarpet Ruby gem for parsing, and Rails' sanitize helper made it very easy to only allow certain tags: links, bold, italics, lists, code blocks, paragraphs.
Problem solved! #StackDecisionsLaunch
Samosprava
More than year ago I was looking for the best editor of Angular 2 application and I've tried Visual Studio Code and Atom. Atom had performance issues that put me off completely to use it again. Visual Studio Code became my main editor #Typescript files (and partly editor of #Java files). I'm happy with Visual Studio Code and I've never look back on Atom. There wasn't any reason to try Atom again, because Visual Studio Code fulfills my requirements very well. I use it for editing of TypeScript, #HTML, #Sass, JSON, Docker and Markdown.
MarkdownWeโre using Markdown parsers for Reviews, Blog Posts, and Stack Description (the text youโre reading right now). Weโre using Bootstrap Markdown for content input (except for reviews) and RedCarpet for rendering in certain places.
MarkdownMarkdown 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.
MarkdownWhat 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.
MarkdownBecause 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.)
MarkdownUsing 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.