Online since 1990 Yes! I started with Gopher. I do modern Web Component Development with technologies supported by **all** WHATWG partners (Apple, Google, Microsoft & Mozilla)
You asked: What's the difference in maintaining your own code base vs. an open source one?
With Open Source code you will wake up one day to a reality described in the above blogs.
It is not if, it is when.
My own code gives me 100% control, any mistakes are my own.
That is also the reason why I stick the UNlicense on all Web Components I make Open Source.
I don't want to maintain dependencies.
BTW, Why are there 50+ alternatives to your Shoelace? And why do you think the stuff you built in your spare time is better than what the Lit/Stencil/Whatever team produces?
Know your history, Gory, dependencies, NPM, any code that is not your own, sucks:
How one programmer broke the Web, by deleting 11 lines of code
How Mootools broke the Web (even React)
You asked: What's the difference in maintaining your own code base vs. an open source one?
With Open Source code you will wake up one day to a reality described in the above blogs.
It is not if, it is when.
My own code gives me 100% control, any mistakes are my own.
That is also the reason why I stick the UNlicense on all Web Components I make Open Source.
I don't want to maintain dependencies.
BTW, Why are there 50+ alternatives to your Shoelace? And why do you think the stuff you built in your spare time is better than what the Lit/Stencil/Whatever team produces?
Let me emphasize my previous statement: "you can fork any version and choose to own the code yourself"
If you don't see the benefits of open source as benefits, it can still be a good starting point that you can maintain yourself thereafter.
I can agree to disagree, though. ✌️