Conversation
full-shell projects , as much as theyre impressive , are not something i ever wanna touch the code of personally , it makes me feel much much safer to implement the thing in python and trigger scriptlets when necessary .
4
0
2
@fiore full "shell" projects aren't the same as a python thin
shell is good to pipe programs together, high level logic is in shell, by means of combining other utilities
shell is good to pipe programs together, high level logic is in shell, by means of combining other utilities
1
0
2
Gato de muchos frijoles 
coolbean@brain.worm.pink
@fiore entirely depends on scale. i remember this script i used to use to launch teamspeak with proton and sharing its wine prefix with arma 3 to make tfar work and it was just... so pointless because 90% of the script is setting environment variables and assembling the launch scriptlet and like... why
1
0
1
Gato de muchos frijoles
coolbean@brain.worm.pink
@fiore i rewrote it in sh and noone died
at a small scale, using python just needlessly complicates what you're doing
at a small scale, using python just needlessly complicates what you're doing
0
0
1
@navi yes i agree , but at the same time the complexity of managing a full shell codebase is just . not something i personally wanna deal with
id much rather have that complexity contained in tiny parts , when needed .
i do agree that shell software is very cool! all im saying is that i personally would be uncomfortable writing it
1
0
1
@fiore yes yes you write the complex tiny parts in a language that's meant for programing
then use shell to wire it together =w=
then use shell to wire it together =w=
0
0
1
@fiore The only I thing I worry about with shell projects is that you cannot ensure that if the person running your scripts environment is out-of-date / weird. (For example MacOS shipping with a old version of bash)
0
0
1