| Elephant Man <conanospamic@gmail.com>: Jan 28 08:19PM Article d'annulation émis par un modérateur JNTP via Nemo. |
| Elephant Man <conanospamic@gmail.com>: Jan 28 08:19PM Article d'annulation émis par un modérateur JNTP via Nemo. |
| Elephant Man <conanospamic@gmail.com>: Jan 28 08:19PM Article d'annulation émis par un modérateur JNTP via Nemo. |
| Horizon68 <horizon@horizon.com>: Jan 28 10:33AM -0800 Hello.. About Energy efficiency.. Energy efficiency isn't just a hardware problem. Your programming language choices can have serious effects on the efficiency of your energy consumption. We dive deep into what makes a programming language energy efficient. As the researchers discovered, the CPU-based energy consumption always represents the majority of the energy consumed. What Pereira et. al. found wasn't entirely surprising: speed does not always equate energy efficiency. Compiled languages like C, C++, Rust, and Ada ranked as some of the most energy efficient languages out there, and Java and FreePascal are also good at Energy efficiency. Read more here: https://jaxenter.com/energy-efficient-programming-languages-137264.html RAM is still expensive and slow, relative to CPUs And "memory" usage efficiency is important for mobile devices. So Delphi and FreePascal compilers are also still "useful" for mobile devices, because Delphi and FreePascal are good if you are considering time and memory or energy and memory, and the following pascal benchmark was done with FreePascal, and the benchmark shows that C, Go and Pascal do rather better if you're considering languages based on time and memory or energy and memory. Read again here to notice it: https://jaxenter.com/energy-efficient-programming-languages-137264.html Thank you, Amine Moulay Ramdane. |
| Horizon68 <horizon@horizon.com>: Jan 28 10:23AM -0800 Hello, About implicit type conversions.. The more implicit type conversions a language supports the weaker its type system is said to be. C++ supports more implicit conversions than Ada or Delphi. Implicit conversions allow the compiler to silently change types, especially in parameters to yet another function call - for example automatically converting an int into some other object type. If you accidentally pass an int into that parameter the compiler will "helpfully" silently create the temporary for you, leaving you perplexed when things don't work right. Sure we can all say "oh, I'll never make that mistake", but it only takes one time debugging for hours before one starts thinking maybe having the compiler tell you about those conversions is a good idea. Thank you, Amine Mopulay Ramdane. |
| Horizon68 <horizon@horizon.com>: Jan 28 09:34AM -0800 Hello, Integer Computation Efficiency Comparisons Between Modern Compilers – Case Study – PI Computation (Delphi, Java, C, C++) Read more here: https://helloacm.com/integer-computation-efficiency-comparisons-between-modern-compilers-case-study-pi-computation-delphi-java-c-c/ Thank you, Amine Moulay Ramdane. |
| You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page. To unsubscribe from this group and stop receiving emails from it send an email to comp.programming.threads+unsubscribe@googlegroups.com. |
No comments:
Post a Comment