C# vs. Go vs. Clojure

C# is the most productive production language - it exposes a lot of functional conveniences along with the robustness of strong typing. And they're finally embracing the open source community - a huge plus.

#Language Features We use the basic syntax (for, foreach, if,while) and object oriented constructs (classes, very simple inheritance).

We also use lambdas and block methods extensively, an intermediate level programming construct, but in a very formulaic and predictable way.

Primarily for game and VR development. Also for one off windows client applications.

Used the MongoDB's C# driver to parse large dataset in .csv files and insert into MongoDB.

All of our code is in C#

The main Carbonmade backend / API is written in C# and is ready to run on the CLR. We currently host on Windows but are preparing to migrate to Linux when the CoreCLR stabilizes.

Running the server side API

One of our primary languages.

Programming language

Most of our codebase is C#

Server side development language and frameworks: ASP.Net MVC 4, Asp.Net WebApi 2, Razor View engine, Moq, Entity Frameworks, etc.

Language of choice for Windows desktop and mobile apps

Base language to develop all the features

Out of necessity

Backend code

originally used c# a decade ago when writing the tools for superman returns at my stint with electronic arts, have used it again recently for developing in unity.

sdas

Backend language of choice

Exclusively for Unity. No .NET sorry :/

Developing programming skills. Algorithms and data structure techniques. working in various types of project from windows forms to asp.net core

C# is our language of choose. Who really uses VB.NET?

C# is my most well-known language. I work with it since my university studies.

Heavily used in front-end client scripting and backend infrastructure; we've been progressively migrating all our infrastructure to be written in C#/.NET Core.

For the alexa skill intents and importing/indexing song data

General purpose API code

No need for this anymore. We use nwjs/elecron instead.

PrometheanTV has used .NET and C# for several back-end applications and services including the Morphic Video Task System utilized to stream video assets to a variety of video delivery platforms including, Akamai, Brightcove, and others.

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.

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!

Backend is based on boltdb for storage, gRPC for communication and Go standard packages.

Have worked on the c2go transpiler and on Joker, a Clojure interpreter written in Go. Used the former to do performance analysis of Go versus C.

Fast and easy to build complex pipelines, the main component of this project.

We use Clojure mostly for its "Minority Report"-like interactive development in situations that require 'semi-automatic programming' (data inspection, admin tasks, API exploration, scrapers, etc.). We have also used Clojure successfully to build some components of our stack very quickly and reliably, in the backend and the frontend.

We are deeply invested in Clojure - all the power of Java with the simplicity of functional programming.

We use Clojure in several places, most often as a wrapper around other libraries and frameworks (e.g. Hibernate, HAPI, etc.) Our HL7 parsing workflow is heavily based on Clojure with files that look almost like configuration, but actually offer tremendous power and flexibility.

The server-side components are 100% Clojure, and the client UI and server communication logic is written in ClojureScript

The site, while running on the JVM is actually implemented in Clojure

Clojure is our main language for building out both the web service that powers the user interface of Lumanu and the web crawling that provides all of our data.

Our main machine learning service is written in Clojure.

just started learning clojure, maybe around two weeks or so. i'm addicted. this is what i want to be working with and learning for the foreseeable future. the elegance of the language is refreshing. the community is really amazing. i've finally found a language that fits my passion for programming.

Cloure is a high level language that provides access to both the JVM (for server-side development) and javascript (for client-side development) with largely the same language. This is important to limit context switching and enable code-reuse during fast product cycles. Clojure is ideal for rapid prototyping and has a strong focus on stability, correctness, and concurrency. Tools like Schema and Spec enable well-structured development and high code confidence.

To complement Java. The REPL lets me interactively exercise Java code. I can write performant and safe libraries in Java, and then use them in Clojure. I also find the data-centric aspect of Clojure (excellent build-in structures, literal syntax for easily creating those structures, functions that act well on abstractions of those structures) good for data processing.

This fits a sweet spot between Ruby and Java.

Clojure simplifies and reduces the coding efforts involved in creating CloudRepo. The fact that it runs in the JVM gives us access to all the libraries that we could ever need. Our code base is much smaller and easier to reason about than it would have been had we gone with pure Java.