Markdown vs. Go vs. Rust

All documentation and blog posts are written in Markdown

We use Markdown primarily for documentation and other forms of writing.

We’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.

Users can format their contributions with Markdown. Great way to post tutorials with code.

Authoring of content

News articles consumed in markdown and injected into React components using Showdown with an XSS filter.

Define the project pages.

By now, almost all my text content is created in (some dialect of) markdown. It's easy to process and extend in javascript.

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.

For when you need to write.

Project documentation.

Documentation and tutorials about the app

Markdown is how I format all my posts. Uses the "smart" and "footnotes" options.

Update with Parsedown

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.

We use this internally, but there is also Markdown CMS plugn-in for Agile Toolkit.

We use NimbusKit/markdown as a convenience wrapper around NSAttributedString

저는 markdown 덕후입니다

Almost everywhere except Python documentation.

wiki notes, internal how-to guides, technical docs, change-logs, release notes

All specifications

Writing README.md's is very important to us. Also a lot of our content is maintained in Markdown (using contentful.com). We are also cool with org-mode.

We use Markdown to write posts for our blog, and also document our processes.

Huge fan of markdown

Mainly for github Readme files, and occasionally for other documentation as desired.

간략한 문법을 통해 깔끔한 문서가 나오는것에 매료되어있습니다.

Write Blog Post @ Github Pages, Documentation like API Blueprint

Use it on a daily basis to create beautifully formatted documents / pdfs.

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.)

Code documentation.

Markdown is awesome and becoming more well-known. It is also easier than using some proprietary markup language.

Yes, we have a README

Standard for editing readme markdown files.

For notes and documentation

For READMEs in code respository

Web services for http://muzeighibli.net

Go is used for the server side code that harvests data, generates reports, and hosts the API for interacting with Social Harvest. It is the major piece of technology used to make Social Harvest possible.

The majority of all code written at Apcera is in Go!

We wrote our own image processing, resizing, and snapshotting service in Go to allow our clients to send photos and GIFs to each other. Files are stored in S3, resized on the fly using OpenCV, and then cached in GroupCache before being served to clients.

Go allows it all to be quite fast and efficient, and entirely non-blocking on uploads!

The first time I actually started using Go was for software on our devices. So on our hotspots we have some custom software running in the firmware. For the first device, that was actually completely built by our manufacturer. But for the second generation most of the parts are built by us in-house and we needed a way to quickly develop software for the device. But we don't have any C programmers in-house, so we were actually looking for something that basically sits in between the friendliness of Ruby, but the performance and the ability to be deployed on an embedded system which you get with C. That's basically what led us to Go and it's been awesome for that. It works so well and so great. Since it works so great, it pushed us into looking into whether we should start using this for some backend services as well.

We're huge fans of Go. We've been porting code into Go for performance and correctness reasons, and most new development is done in Go.

We are prototyping custom API services as custom Go programs.

Creating high performance servers and server software.

Most new projects I start are written in Go.

For some of our more taxing parts of our applications, something able to handle high I/O load quickly and with fast processing is needed. Go has completely filled that gap, allowing us to break down walls that would've been completely impossible with other languages.

Frontend (compiler)

A handwritten Go parser takes the human-readable representation and generates blacklight bytecode out of it.

Backend (VM)

blacklight leverages the concurrency and garbage collection features of Go.

Language of choice. No question.

High performance backoffice integration systems, with more than 70 millions of dayly synchronizations and peaks over 100k synchronizations per minute.

Go powers most of our backend. We primarily like Go due to it's memory efficiency, fast compilation times, excellent concurrency support and great tooling.

Simple but powerful language to create system and network tools that we utilize. Compiled program makes it easy to deploy due to no complex dependencies.

We use golang to create image and video preprocessor, utility for health check + autoscaling and many others

Backend API and command line utilities

I'm a big fan of Golang. I use Golang in most time. In addition, The most software projects of me are written by Golang.

The core language we develop the itzMe platform in.

Most of the building blocks of our microservice platform are written in Go

Quick prototyping and development of microservices for side projects.

The large majority of the microservices and workers in our latest product's architecture are written in Go.

Go was used as the language for the backend. It's fast, fun to write and proved really useful throughout the entire project.

All Lambda functions are written in Golang, managed via https://github.com/apex/apex.

Compact web applications, more secure and faster processing, building sophisticated multifaceted applications with multiple servers working together.

Processos de DevOps

Our platform is developed in Go.

We use Go to build and scale our application API

Would love to use more professionally!

It's my main dev language now.

We use go as our main backend language

Our backend API server and proxy server are written in Go, because it scales very well with the number of incoming or pending requests.

Cirrus CI agent that executes tasks on a host VM or a container is written in Go so it is a self-contained static executable that can be executed on Unix and Windows.

high concurrency and dead simple to write

Go is great for realtime. The gorilla websocket library is excellent. Also the low memory consumption of a single goroutine means you can easily handle many WS connections on a single node.

Go provides the backend of Gofus

Our main web scraping engine is built usign Golang because of the way how efficiently and fast this language is. Also out compilation facility let people who dont know Golang build fast as flash scrapers to run ourside of our platform without any knowledge in programming in Golang.

The following basic API endpoints are implemented on the server written in Go:

• Authorization (Sign Up, Sign In)
• Update user profile
• Community: add post, like post, add comment, delete post, add reply to comment
• Self-diagnosis: send data from the app to the server
• Journal: send user data from the app to the server
• Add groups of community
• Report post, report comment, report reply
• Block user

We’re using go to create fast, massively scalable data ingestion pipeline from IoT edge devices.

We love gopher!