HN Gopher Feed (2017-08-12) - page 1 of 10 ___________________________________________________________________
Pony Performance Cheatsheet
27 points by spooneybarger
https://www.ponylang.org/reference/pony-performance-cheatsheet/eet/___________________________________________________________________
bhauer - 1 hours ago
This is a great summery of performance-oriented tips that in many
cases are generally applicable, even beyond the specific context of
Pony.
CJefferson - 1 hours ago
I'm disappointed (in pony) that one suggest is to use tuple instead
of a class, and in general avoid naking little clases.One often
overlooked benefit of c++ (and I am sure other langyages) is that I
can wrap one or two ints in a class, add some constructors and
little member functions, and be fairly confident the whole lot will
get inlined and compiled away.
trishume - 34 minutes ago
Indeed, this is a good document for Pony (and a lot applies to
other languages like OCaml as well!) but it shows what
programming in a language like Rust or C++ that has many zero-
cost abstractions gets you.In Rust I can always use wrappers,
aliases and union types, and idiomatic error handling. And since
the abstractions are either zero-overhead or will reliably be
optimized away by LLVM, I don't have to worry about sacrificing
performance.