Jason NovingerM to Python · 2 years agoThis is valid Python syntaxwww.bitecode.devexternal-linkmessage-square8fedilinkarrow-up110arrow-down10file-textcross-posted to: [email protected][email protected]
arrow-up110arrow-down1external-linkThis is valid Python syntaxwww.bitecode.devJason NovingerM to Python · 2 years agomessage-square8fedilinkfile-textcross-posted to: [email protected][email protected]
minus-squaremsagelinkfedilinkarrow-up4·2 years agoUltimately it’s about the project leader what kind of code gets in. You can write unmaintanable code in every language - some even ascending to esoteric levels, like JsFuck
minus-squareverstralinkfedilinkarrow-up1·2 years agoWell, I’m saying that we could design a language where code would have to be formatted, so it would not be up to the project leader, at least syntactically.
minus-squaremsagelinkfedilinkarrow-up1·2 years agoI personally hate when code forces me to format things one way. And there always be a way to go around formatting. Once I forced formatting on git server just to never worry about it.
minus-squareverstralinkfedilinkarrow-up2·2 years agoYeah, that’s true, auto formatters will always have cases which format weirdly and have a nicer alternative. But in the end, the formatting does not matter much, so we all benefit for it being formated one way, and one way only. How would you format on git server? Create commits automatically, or ammend commits on push?
minus-squaremsagelinkfedilinkarrow-up1·2 years agoI… don’t actually remember. It was a server side hook, I guess it tackled a new commit at the end. But it has been too long ago. Nowadays I don’t enforce such strict formatting, I just comment on MRs where I notice transgressions. I never liked ammending commits. Had a colleague, team lead, who ammended other peoples commits. Ugh. That’s when I started signing my own work.
Ultimately it’s about the project leader what kind of code gets in.
You can write unmaintanable code in every language - some even ascending to esoteric levels, like JsFuck
Well, I’m saying that we could design a language where code would have to be formatted, so it would not be up to the project leader, at least syntactically.
I personally hate when code forces me to format things one way.
And there always be a way to go around formatting. Once I forced formatting on git server just to never worry about it.
Yeah, that’s true, auto formatters will always have cases which format weirdly and have a nicer alternative.
But in the end, the formatting does not matter much, so we all benefit for it being formated one way, and one way only.
How would you format on git server? Create commits automatically, or ammend commits on push?
I… don’t actually remember. It was a server side hook, I guess it tackled a new commit at the end. But it has been too long ago.
Nowadays I don’t enforce such strict formatting, I just comment on MRs where I notice transgressions.
I never liked ammending commits. Had a colleague, team lead, who ammended other peoples commits. Ugh. That’s when I started signing my own work.