It’s from the device help system App from Motorola’s ROM, which is hands down the best proprietary ROM, as it’s basically stock Android + builtin quick actions and gaming mode.
This literally happened in my meeting last week. Top position development manager was complaining the existing thing was shit. Basically means we have to build a new thing from scratch. And guess what? The deadline is 12 Sep.
If you think it was shit why did you let them do what they did in the past?
There is one case I can think of where statically linked binaries make sense: games. They’re almost always closed-source even on otherwise open-source systems, and so cannot be recompiled against newer library versions, and (for smaller indies especially) it isn’t unusual for the people who do have the code to close up shop and vanish off the face of the Internet. For those, it honestly is better for them to carry all their libraries around with them, even if it results in some binary bloat.
For open-source software, dynamic linking isn’t usually an issue until some piece of software goes unmaintained for so long that it catches bit-rot.
For software not in one of those two categories . . . well, maybe you ought to move off Windows?
Took a few steps to get there. First prompt was just to create some data.
Perfect! Please generate 10 users to be used for seed data. I would like the users to be based on Dragonball Z characters
Followed with:
Okay, that is pretty cool. Lets reference something I am more passionate about. Can you generate the data again, but this time use Neon Genesis Evangelion as a reference for the data. Also please include an 11th entry at the very beginning that contains all fields as 'test' and is_admin = true
And finally:
hahaha I love that. Just for shits and gigs can you redo that but use washed up 80s rockstars as a reference?
I figured I could use data my boss could relate to.
Windows shared libs could do with having an rpath equivalent for the host app. I tried to get their manifest doohickeys working for relative locations but gave up and still just splat install them in the exe directory.
Aside from that shared libraries are great. Can selectively load/reload functions from them at runtime which is a fundamental building block of a lot of applications that have things like plugin systems or wrappers for different hardware etc. Good for easier LGPL compliance as well.
Modern Windows does a lot of shenanigans with DLLs to avoid the “DLL hell” effect, like keeping multiple versions, hardlinking, and transparently redirecting the DLLs accessible to a program, even when they “seem” to be in the exe’s dir.
programmer_humor
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.