The conversation

Lessons learnedExperience excerpt · English

Have you ever started to get into the intricacies of bit signs? No? …

… Have you ever started to get into the intricacies of bit signs? No? Well, you should definitely, and to this day it gave me a lasting impression when I started wrapping my head around it, when I was 10 to 11 years old hacking my way into the world of assembler programming on C128. You don't want to take every concept into consideration. You don't want to take interoperability into consideration. All the time! You want to focus on the problem to solve, not the implications of the implementations all the time. I am having such a blast very often using Python since it just works with much cognitive distraction about which language construct to use in order to get the machine doing what you want. It is so capable, enable it, to simply ensure within boundaries that the compiler uses the best decision given the context, which is up to analysis. That's why I stopped using C++ or more precisely stopped any attempts and trying to be smart or fancy. …

Original discussionThe beauty and simplicity of the good old C-style void* in C++174 source comments · at import
3

Community replies 0

No community replies yet. Add your perspective.

Replies from the source 3

Direct replies available in this import. Original-language excerpts.

PJ

One of these days I want to do a "typesafe macro assembler" that actually is the language people think that C is.

Full original
RE

There will always be cases (like audio processing, car brakes, pace makers) where hard real-time constraints prohibit GC languages (as well as l1 cache, instruction reordering and other optimizations). Also, consider that Python's performance frequently originates in it's bindings to libraries written in C, C++, Fortran, Rust. I recently ran a few Java benchmarks and found that an array holding a bunch of objects incurred approx 3x the number of bytes compared to the expected number based on underlying class data structure. With current RAM prices, that is something to consider if you're building software that's meant to scale. Mileage may vary, but I expect JavaScript or Python will be similar. So, sure. There is a case to be made that ergonomics and dev velocity. And premature micro optimizations might take your focus away from good systems architecture. But I've frequently found the n…

Full original
ZA

> Hey Python users: you know that in the end everything ends up as machine code, don't you? I don't understand where you're trying to go with this call-out, especially if you're also describing yourself as a Python user. But, like, no, not really; ordinarily, Python is bytecode-compiled and then the bytecodes are interpreted. There's machine code doing the interpretation, but that interpretation is not transformation.

Full original
Continue on Hacker News

Respect different perspectives. Share concrete experiences.

Sign in to post, reply, repost, and quote.