The imports themselves may be dynamic. I once did a little review of dependencies in a venv that had everything to run pytorch llama. The number of imports gated by control flow or having a non-constant dependency was nontrivial.
Imports gated by control flow aren’t a huge obstacle, since they’re still statically observable. But yeah, imports that are fully dynamic i.e. use importlib or other import machinery blow a hole in this.
I miss the people of her generation. I feel like we could use their perspective, experience and fortitude right now. I sure miss their music too...even though Bird Lives.
I lost both my grandmothers this past 7 years. One about the same age as Betty, the other a few years younger. It's amazing how much insight you can glean from one-off comments in passing conversation you can pick up, or for that matter drop.
I'm in the middle of Gen-X... kind of the last generation raised "tough" so to speak. Also a generation facing massive ageism, despite knowing and understanding technology as well or better than the younger generations. First generation to make less than that which came before. By the same token, I don't think my generation has a lot of stand-out leaders in its ranks. We've mostly been good by example, but starkly independent.
All I know is that I miss both of my Grandmothers deeply.
Okay pathetic downvoters. If the commenter loves music of her generation so much then they should actively look to support local live arts that play that kind of music. But yeah never mind lets only support Big Music Industry instead (or other big entertainment industries).
I might relate to this, but I also spent more time talking to friends on the phone 20 years ago. The perception of this greatness can't be disentangled from the experience of youth.
I like to think that the enthusiasm for retro computing can make a clearing for innovative things to happen. I imagine such an environment can support values that aren't normally represented in fashionable, modern, commercial technology of today.
I've found adherence to C++ conventions in low-level software to be a rather contentious issue, mostly recently when working in an ML compiler group. One set abhorred the use of macros, the other any kind of polymorphism or modern C++ feature.
Coming from a background of working with OS kernels and systems software, I don't mind the kind of explicit "C++ lite" style used by the OP. Left to my own devices, I usually write things that way. I would think twice if I was trying to design a large framework, but ... I try to avoid those.
That is impressive. It certainly shows what is possible _if_ you are familiar enough with the intricacies of modern C++. I'm not sure how I feel about a workflow where one needs to continually address "overhead" introduced by the language environment.
reply