4 ms·

Moving from Python to Go seems to be the thing that happens once you need your Python to be more performant.

by avbor 10y ago

rurban 10y ago
Same thing for ruby and perl also. I would have advocated to move to pony instead, since it is a much cleaner and much faster language than Go, and has guaranteed deadlock and race safety, unlike Go or rust. It also needs much less memory.
- jankiel 10y ago
  Pony is in alpha and seems to be overcomplicated at first glance
  - shakna 10y ago
    Pony doesn't feel alpha. I've spoken a little about it before [0]. The Actor model might feel verbose, but it gives you amazing concurrency, and with Pony's compiler, safety. Pony is fast, concurrent by default, and type safe. That's amazing. [0] https://news.ycombinator.com/item?id=13233607 https://news.ycombinator.com/item?id=13233607
  - rurban 10y ago
    Overcomplicated? Compare that to manual locking required for rust concurrency or c++ concurrency. Or the copying overhead you get with Go, which can still deadlock. pony does not need any locks, just proper types. And it can copy or share state in threads. And it has nominal or structural types. Old-style inherited or new mixin OO. It is far advanced over rust. Just distributed actors as in Erlang are not there yet.
crdoconnor 10y ago
This is what happens when you follow the fashion driven development merry go round: https://docs.google.com/presentation/d/1LO_WI3N-3p2Wp9PDWyv5B6EGFZ8XTOTNJ7Hd40WOUHo/mobilepresent?pli=1#slide=id.g70b0035b2_1_168 https://docs.google.com/presentation/d/1LO_WI3N-3p2Wp9PDWyv5... Re-implementing the hot path (which is likely to be a small piece of code) in a non-garbage collected language (C or ideally Rust) is a much more sane approach than the big bang rewrite: https://blog.sentry.io/2016/10/19/fixing-python-performance-with-rust.html https://blog.sentry.io/2016/10/19/fixing-python-performance-...

4 ms·

Moving from Python to Go seems to be the thing that happens once you need your Python to be more performant.

by avbor 10y ago

Moving from Python to Go seems to be the thing that happens once you need your Python to be more performant.

rurban 10y ago
Same thing for ruby and perl also. I would have advocated to move to pony instead, since it is a much cleaner and much faster language than Go, and has guaranteed deadlock and race safety, unlike Go or rust. It also needs much less memory.
- jankiel 10y ago
  Pony is in alpha and seems to be overcomplicated at first glance
  - shakna 10y ago
    Pony doesn't feel alpha. I've spoken a little about it before [0]. The Actor model might feel verbose, but it gives you amazing concurrency, and with Pony's compiler, safety. Pony is fast, concurrent by default, and type safe. That's amazing. [0] https://news.ycombinator.com/item?id=13233607 https://news.ycombinator.com/item?id=13233607
  - rurban 10y ago
    Overcomplicated? Compare that to manual locking required for rust concurrency or c++ concurrency. Or the copying overhead you get with Go, which can still deadlock. pony does not need any locks, just proper types. And it can copy or share state in threads. And it has nominal or structural types. Old-style inherited or new mixin OO. It is far advanced over rust. Just distributed actors as in Erlang are not there yet.
crdoconnor 10y ago
This is what happens when you follow the fashion driven development merry go round: https://docs.google.com/presentation/d/1LO_WI3N-3p2Wp9PDWyv5B6EGFZ8XTOTNJ7Hd40WOUHo/mobilepresent?pli=1#slide=id.g70b0035b2_1_168 https://docs.google.com/presentation/d/1LO_WI3N-3p2Wp9PDWyv5... Re-implementing the hot path (which is likely to be a small piece of code) in a non-garbage collected language (C or ideally Rust) is a much more sane approach than the big bang rewrite: https://blog.sentry.io/2016/10/19/fixing-python-performance-with-rust.html https://blog.sentry.io/2016/10/19/fixing-python-performance-...