F# vs Markdown: What are the differences?
Developers describe F# as "Strongly-typed, functional-first programming language for writing simple code to solve complex problems". F# is a mature, open source, cross-platform, functional-first programming language. It empowers users and organizations to tackle complex computing problems with simple, maintainable and robust code. On the other hand, Markdown is detailed 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.
F# and Markdown belong to "Languages" category of the tech stack.
"Pattern-matching" is the primary reason why developers consider F# over the competitors, whereas "Easy formatting" was stated as the key factor in picking Markdown.
F# is an open source tool with 2.09K GitHub stars and 341 GitHub forks. Here's a link to F#'s open source repository on GitHub.
Asana, Code School, and GoSquared are some of the popular companies that use Markdown, whereas F# is used by Olo, Huddle, and Property With Potential. Markdown has a broader approval, being mentioned in 756 company stacks & 718 developers stacks; compared to F#, which is listed in 19 company stacks and 16 developer stacks.
What is F#?
What is Markdown?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using F#?
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
Visual Studio Code worked really well for us as well, it worked well with all our polyglot services and the .Net core integration had great cross-platform developer experience (to be fair, F# was a bit trickier) - actually, each of our team members used a different OS (Ubuntu, macos, windows). Our production deployment ran for a time on Docker Swarm until we've decided to adopt Kubernetes with almost seamless migration process.
After our positive experience of running .Net core workloads in containers and developing Tweek's .Net services on non-windows machines, C# had gained back some of its popularity (originally lost to Node.js), and other teams have been using it for developing microservices, k8s sidecars (like https://github.com/Soluto/airbag), cli tools, serverless functions and other projects...
I've used .NET for many years, but only in recent years, after Microsoft introduced .NET Core, I've found a new love and excitement for the technology again. The main driver for us using .NET Core is not that it is cross platform compatible, open source or blazingly fast (which it is!), but the fact that we can use (what we consider) the best programming languages (mainly F# and C#) to carry out our jobs without sacrificing the other benefits.
Today we run most of our web infrastructure on .NET Core in Docker containers, deployed into a Kubernetes cluster which spans across multiple time zones in the Google Cloud and we couldn't be happier. Due to the portability of the .NET Core platform we are even able to develop many new services as serverless functions with F# which has become an absolute game changer.
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:
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.
I needed to make stack decisions accept a subset of Markdown, similarly to sites like Reddit or Stack Overflow.
Problem solved! #StackDecisionsLaunch
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.
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.