C++ vs. CoffeeScript vs. Clojure

Core linear algebra and optimization functionality for deep analytics and machine learning

The most latency sensitive parts are written in C++. Due to our interconnected services architecture, we use either Python or C++ for each service, with the performance critical parts being C++14.

Our online judge, 'Evaluator', is written in it.

legacy part

The Game Pencil Engine Editor is coded in C/C++.

Used in backend and clients for performance heavy tasks.

Performance, zero-overhead abstractions and memory safety of the modern C++ language make this the perfect language for the project.

High performance

The main programming language of ApertusVR. C++11 & CMake provides multi-platform targeting. The architecture is modular.

Used to write PHP extensions - AZTEC Decoder - License Driver scan - Axis2/C to PHP wrapper and Job-scheduler - Barbershop

std::cout << "Hello World!" << std::endl;

C++ is used in Shiro (https://github.com/Marc3842h/shiro).

C++ is a high performance, low level programming language. Game servers need to run with fast performance to be able to reliably serve players across the globe.

Javascript is a hell. We use coffeescript for its readability.

All front-end / back-end is driven by Coffeescript. For the main ReactJS functionality JSX is embedded with coffee in .cjsx files / handled by Browserify.

I use a lot to coding JS.

All our code is CoffeeScript, blending seemlessly in our JS stack

This is my language-of-choice for coding.

All frontend code written in coffeescript

See NodeJS once again.

CoffeeScript is good to write some utilities at front-end.

All of our Javascript code is first written in CoffeeScript for ease of reading / writing. It is compiled to Javascript before being minified and served to the client.

We like CoffeeScript because it's more readable, we use it because we have a lot of libraries and functions already (plays nicely with Rails, too)

We prefer typescript.

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.