puke

a language that is happy and eager to suck at many things in pursuit of low-boilerplate, low-noise, highly reliable, high performance state machines with enforced strict error handling and built-in fault injection.

puke may become a language that encourages users to write code that is usable by others and respectful to themselves by providing superior scheduling and concurrency facilities to what is generally available in current industrial languages.

puke should be an ideal language for building

• databases
• distributed systems
• multitenant infrastructure

puke does not aim to excel at

• building your own data structures
• intensive numerical processing
• short-lived CLI applications
• embedded programming

ideas that may or may not lead to puke

• erlang's terseness, focus on immutable message passing, explicit supervisor hierarchies, pattern matching
• celf's nondeterminism and linear logic
• prolog's declarative debugging, tables, provability of pure code
• total functional programming
• unison's effect systems
• rust's restricted linear typing

puke should excel at

• testability
  • built-in network simulation, fail-points, concurrent interleaving exploration, model-based testing support
• optimistic concurrency
  • shared mutable state regulated by optimistic software transactional memory, letting users avoid thinking about data races
• scheduling
  • the runtime tracks overall utilization and saturation
  • aims to maximize utilization while minimizing saturation (writes before reads before accepts for sockets)
  • infers contention causality encountered in the optimistic state layer and learns to step in as a traffic director, letting users avoid thinking about contention
• rich built-in data structures, first-class json support, first-class binary parsing support

puke is written in rust and takes advantage of things like

• io_uring
• simdjson
• sled
• software transactional memory

puke will have a gross name until it becomes something that is not actually gross