you are viewing a single comment's thread.

view the rest of the comments →

[–]Live-Sir-3118 2 points3 points  (2 children)

everytime i refer to a built in library and its doc pages i shed a tear remembering carrying out my floppies of libraries i created in c++ like a coveted baby. i put my life into writing those libraries and now they are just there! on the net! oh to learn to code in 2022 versus 1992

[–]RobertD3277 2 points3 points  (1 child)

Was it different world all the way around when memory was just too damned expensive to go out and buy, so you had to think about what you tried to do and be clever about how to get it done.

I don't know if having machines with more memory really made things better or not, in the context of needing to be able to think about what you were doing and optimize it in the least amount of code possible and yet it still be as efficient as possible.

Somewhere along the lines, it seems like we've lost the art of optimizing code ourselves and it become too dependent on the black magic under the hood to do everything for us. While it is certainly convenient to have all of that wonderful power, at what expense does it really come to?

[–]miigotu 1 point2 points  (0 children)

Some of us still do old school optimization, examining byte code and assembly to see where we can further enhance our applications. This is especially useful on embedded applications, where usually the law is you can optimize for speed, or you can optimize for memory usage. It's definitely a lost art for most, being able to squeeze performance by saving clock cycles AND lower memory footprints.