2 ms·

I'm a C++ programmer and a python programmer. I assure you your conclusion is incorrect. Python with type checking is by far more productive. Many people who kn

I'm a C++ programmer and a python programmer. I assure you your conclusion is incorrect. Python with type checking is by far more productive. Many people who know python and another language can testify to this general truth.

simiones 5y ago
C++ is probably the least productive non-joke language ever created: it has deterministic destruction which requires (manual) ownership tracking, it has an extremely slow compiler with horrible error messages, it has massive performance differences between debug and optimized builds, it's focus on performance brings lots and lots of extraneous concepts to its libraries when just seeking to get something working (std::allocator, std::string_traits and many other similar examples). Comparing Python to Java, C#, Haskell, Erlang, Go, maybe even C or Rust, would show a much smaller performance difference.
- shepardrtc 5y ago
  > requires (manual) ownership tracking Have you tried RAII? Would you like to know more? https://stackoverflow.com/questions/2321511/what-is-meant-by-resource-acquisition-is-initialization-raii https://stackoverflow.com/questions/2321511/what-is-meant-by...
  - simiones 5y ago
    RAII is exactly what I mean by "manual ownership tracking and deterministic destruction". RAII is better than completely manual memory management (C style malloc/free), but it still requires you to design your program such that every piece of memory is owned by some pointer with the correct properties. You have to choose between copying, bare pointers/references, unique_ptr and shared_ptr whenever two pieces of data are related to each other, or whenever you pass a piece of data to another function. Rust is a little better since at least the ownership concept is known to the compiler and automatically enforced. (Tracing/Copying/Compacting) GC is much easier since this entire concept goes away. You always pass references to data, and the physical storage is "owned" by the GC itself. It's also much faster for certain workflow patterns, though it always consumes more memory than deterministic destruction schemes.
isubasinghe 5y ago
I do a lot of Rust programming, I personally find Rust more productive right now.

simiones 5y ago

C++ is probably the least productive non-joke language ever created: it has deterministic destruction which requires (manual) ownership tracking, it has an extremely slow compiler with horrible error messages, it has massive performance differences between debug and optimized builds, it's focus on performance brings lots and lots of extraneous concepts to its libraries when just seeking to get something working (std::allocator, std::string_traits and many other similar examples). Comparing Python to Java, C#, Haskell, Erlang, Go, maybe even C or Rust, would show a much smaller performance difference.

shepardrtc 5y ago
> requires (manual) ownership tracking Have you tried RAII? Would you like to know more? https://stackoverflow.com/questions/2321511/what-is-meant-by-resource-acquisition-is-initialization-raii https://stackoverflow.com/questions/2321511/what-is-meant-by...
- simiones 5y ago
  RAII is exactly what I mean by "manual ownership tracking and deterministic destruction". RAII is better than completely manual memory management (C style malloc/free), but it still requires you to design your program such that every piece of memory is owned by some pointer with the correct properties. You have to choose between copying, bare pointers/references, unique_ptr and shared_ptr whenever two pieces of data are related to each other, or whenever you pass a piece of data to another function. Rust is a little better since at least the ownership concept is known to the compiler and automatically enforced. (Tracing/Copying/Compacting) GC is much easier since this entire concept goes away. You always pass references to data, and the physical storage is "owned" by the GC itself. It's also much faster for certain workflow patterns, though it always consumes more memory than deterministic destruction schemes.

isubasinghe 5y ago

I do a lot of Rust programming, I personally find Rust more productive right now.