Webi has become far too complex.
I wanted something with near-0 magic - which is why I opted for shell scripts.
But as I've added one case, and then another, and then another (and pivoted from the helper script to the webi command), it's bloated way too far.
There is a lot of necessary complexity, but there's also a lot of leftovers from the learning process.
My thoughts on fixing that:
This shouldn't really be Webi v2.0.0 - because it should be a smooth refactor with additional API on the server-side, not breaking changes, nor a from-scratch rewrite, nor a philosophical shift from the original goal.
Thoughts
Webi has become far too complex.
I wanted something with near-0 magic - which is why I opted for shell scripts.
But as I've added one case, and then another, and then another (and pivoted from the helper script to the
webicommand), it's bloated way too far.There is a lot of necessary complexity, but there's also a lot of leftovers from the learning process.
My thoughts on fixing that:
webineeds to be its own command, not embedded in the bootstrap(less scary, easier to lint, more fun to add
--whatevertoo)webishould be offline-first(ex: switch versions, reinstall most recent version)
webi_downloadshould be templated based oncurlandwgetwebi_extractshould be templated based ontar,xz,gitetcwebicommandbootstrap.shtocurl-pipe-bootstrap.shfor claritytemplate.shtoinstall.tpl.shfor clarityThis shouldn't really be Webi v2.0.0 - because it should be a smooth refactor with additional API on the server-side, not breaking changes, nor a from-scratch rewrite, nor a philosophical shift from the original goal.
Thoughts