The flip side is that by using a library, it theoretically means it should be fairly battle-tested code, and should be using appropriate APIs. File watching has a bunch of different OS specific APIs that could be used, in addition to the naive "read everything periodically" approach, so while you could knock something together in an hour, the library should be the correct approach. Sadly, at least in rust land, there are a ton of badly written libraries to wade through... 🤷

[–] PhilipTheBucket@piefed.social 10 points 3 days ago (1 children)

Yeah. I have no idea what the answer is, just describing the nature of the issue. I come from the days when you would maybe import like one library to do something special like .png reading or something, and you basically did all the rest yourself. The way programming gets done today is wild to me.

[–] CameronDev@programming.dev 3 points 3 days ago* (last edited 3 days ago) (1 children)

I'm not sure its a problem in of itself, but i agree it definitely enables a problem. Between "is-even" and vibe coding, modern software engineering is in a very sorry state.

[–] PhilipTheBucket@piefed.social 4 points 3 days ago

Yeah. I feel like in a few years when literally nothing works or is maintainable, people are going to have a resurgent realization of the importance of reliability in software design, that just throwing bodies and lines of code at the problem builds up a shaky structure that just isn't workable anymore once it grows beyond a certain size.

We used to know that, and somehow we forgot.