reusable

Meanwhile, it would be nice to have a reusable code of conduct written with the same attitude.

Example: you have a reusable 10 ton vehicle and you need to send a 150 ton mass to orbit.

We're currently working on a brand new responsive site with React, complete with reusable component library to facilitate our work.

Static typing makes it easier to write reusable code, provided the type language is sufficiently expressive.

As another poster already said, Ada fulfills all of the requirements, and you can trivially write reusable code in it.

However, I would not be as likely to use TeaBOT if I couldn't use my own reusable cup.

Do you have any plans to produce and/or market reusable cups to work with the machine, with the (seemingly) popular filter lid?

A simple type system makes it difficult to express useful invariants that are also flexible enough for the code to be reusable.

You could launch most of this stuff with reusable Falcon 9 rockets or equivalents.

I am sure there would be a lot of reusable pieces in the end he could re-use.

We're now working on a similar feature for reusable UI components.

Why does static typing make it harder to write reusable code?

Statically typed and simple generally means it's pretty hard to actually write reusable code and it's unlikely to "support multi-paradigm" very well.

Do you mean something different by "reusable" from "easy to reuse?"

(There's a pretty good book called "C Interfaces and Implementations"[1] that talks about how to write reusable code in C.) Classes are also possible to implement in C.