I want to make something clear, which is that there isn't a total avoidance of external libraries. Only that you're not so quickly choosing them for every probl

I want to make something clear, which is that there isn't a total avoidance of external libraries. Only that you're not so quickly choosing them for every problem. It makes sense to use Vue (just an example), it doesn't make sense to use a library that's a wrapper on top of another wrapper to use within Vue. That sort of deal. You maintain the code the same way those other people maintain their code, testing. They aren't doing anything special here, you still have to write tests (well, you can get GPT to write some of them for you). The upside here is you are the one in control of this and you can change and test to your specific needs. You are not relying on external library who has to appeal to a general huge variety of use cases. You also don't have to deal with a lot of external time-wasters, as you're only working internally so you aren't at the whims of whether or not that group can even work on implementing your change. Plus, no more random changes that catch you by surprise when you're reading the change log. >Keep asking ChatGPT to fix it when things break? Hah, maybe some day we will get to that point. Until then we still need to know what is happening, however, you might be surprised to find out how infrequently things require that much input seeing as you aren't at the whims of random other parties constantly.