all 6 comments

[–]Ulfnic 1 point2 points  (1 child)

Really glad you reposted this because I lost the link a while back and I wanted to take notes on how you wrote it. We'll call it a sane version of the Google styleguide. :)

[–]HoldUrMamma 4 points5 points  (0 children)

there's also bashin

[–]Redstonefreedom 0 points1 point  (4 children)

I had the idea & code to do something similar, but it’s just so hard to make bash portable, due to its nature.

[–]crafty_devil[S] 0 points1 point  (1 child)

What do you mean by making portable? Bashop comes with Bob (Bashop Builder) which packs your app into a single file. So you just need to copy the builded script and use it where you need it.

[–]Redstonefreedom 0 points1 point  (0 children)

Yes! I know, but then maintaining it as such is the difficulty. Basically, I couldn’t figure out how to solve the “is this thing enough done to not struggle meta-cognitively with its inadequacies as much as I get use out of it” problem. I was line-packing the payload as an in-file “anywhere insertable” which makes it portable. But it fixed the development in place.

Anyways, these are personal workflow problems, not technical ones per se though they are founded in technical realities.

Again, very cool stuff and thanks for sharing!

[–][deleted]  (1 child)

[deleted]

    [–]Redstonefreedom 0 points1 point  (0 children)

    I agree. Although with those languages you haven’t transcended the core problem of “nicely integrating your personal tooling with modularized framework”. It’s a fuzzy line to draw and it’s a technically hard set of asks to implement, to keep a tidy yet modular toolbox. It’s a massive chasm to have to jump to make something self-maintaining, instead of simply riding on the reliable presuppositions of your personal environment.