Is Lisp particularly suitable for sole developer or small teams?

• slite

  5 50 5.5 Common Lisp

  a SLIme-based TEst runner for FiveAM and Parachute Tests

But that's also what makes it worse for large teams: the same "immediate" productivity doesn't always translate to clean long-time maintainable code. Working in a large teams involves creating the right incentives to developers for long term maintability. For instance, if developers have a hard time testing complex code, they're more likely to write unit tests to test components. In Lisp, testing complex code is super easy interactively, so unit-testing can sometimes be harder. (Actually, this was an inspiration for one of my open source tools: https://github.com/tdrhq/slite, I wanted to make testing as easy as interactive development)

• Folly

  90 27,118 9.8 C++

  An open-source C++ library developed and used at Facebook.

  

vast swathes of dependencies have been shown to sometimes be huge liabilities in team-based settings. The biggest companies end up going as far as not depending on the standard library! When I worked at Facebook a decade ago, we couldn't use the C++ STL in a lot of cases, we had to dogfood and use their own in-house creation: folly

• InfluxDB

  www.influxdata.com featured

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

• pie

  10 671 10.0 Racket

  The Pie language, which accompanies The Little Typer by Friedman and Christiansen (by the-little-typer)

  

I really should read https://thelittletyper.com/

Suggest a related project