What's happening to my GitHub, is code columns the next cool metric?
174 likes 12 replies
Replies
Joshua Ward | ✝️ | NO AI | Rust! | Simple is better · May 11
What if: text editor that stored diffs using the same data structure as Goggle docs ( or your favorite non-evil equivalent ) to build the diffs. Would be so much more accurate, just sayin’ Although of course new problems would arise
Yasa · May 12
I Like That PArticular Shade Of Green
Nonlucid Luna · May 12
this is either gonna work really well or be really bad. Who knows? I personally think code columns would be great if used for something like... I dunno... organization? like, you define functions in one column, the main code is in another column, and so on and so forth, and perhaps, and maybe and
Drumchaku · May 12
GitHub getting really buggy. Might be a good time to move my repos elsewhere.
treethought · May 12
I'd prefer a resolution of code to lines of code
GSV(E) A Suffusion Of Diggity · May 12
When this code hits 88 columns wide you're going to see some shit
Fuzzy · May 12
I hope it lets me leave a PR comment on column 6 with no line number
Banda Bassotti · May 11
Code editor with MS Word style tab spacing rulers on the sides.
Daniel Bayley 🇺🇦 · May 12
Microslop just can’t help itself. Still, a less insane metric than ’tokenmaxxing’.
Jacob Packert · May 11
yikes Did their LLM go `flex-direction: vibe‘ ?
patak · May 11
I'm glad they are innovating and trying new things.
Tekchip · May 11
The implication seem to be coding longer not...harder? The joke almost came together.