@Natanox @blacklight @cybeej You are not wrong. And that is also why I have to have "the talk" with devs before they put fresh code randomly into production. Then I attack it to see where it breaks. Then I give them hell if it's a large business entity I'm consulting with. Sometimes we learn by doing. Sometimes the dependencies teach us lessons we didn't know we needed.
Conversation
Notices
-
Lorq Von Ray (lorq@small.circlez.social)'s status on Sunday, 30-Jul-2023 21:30:09 UTC Lorq Von Ray -
Natasha Nox 💙💛 (natanox@chaos.social)'s status on Sunday, 30-Jul-2023 21:30:09 UTC Natasha Nox 💙💛 @lorq @blacklight @cybeej I feel like we should get back to the UNIX / GNU style of toolboxes (not sure right now where the philosophy originated from). Make a tool that does *one* thing, and does it exceptionally well.
There might be an extended philosophy to be articulated for frameworks or very complex tools that require massive flexibility (simple example would be a Browser). -
Natasha Nox 💙💛 (natanox@chaos.social)'s status on Sunday, 30-Jul-2023 21:30:10 UTC Natasha Nox 💙💛 @blacklight @cybeej @lorq There are multiple bad developments I see at work here. One would be "dependency hell", another one the abundance of "jack of all trades" libraries and frameworks that can't be split up at all. Web development became quite monstrous in this regard, though some IDE's (or compilers?) are also quick in silently attaching 3 to 4 megs of libraries onto your hello world program unless told otherwise, just in case you need them.
-