@seaQueue to Programmer [email protected] • 8 months ago50 million rendered polygons vs one spicy 4.2MB boiimagemessage-square137arrow-up11.38Karrow-down113
arrow-up11.36Karrow-down1image50 million rendered polygons vs one spicy 4.2MB boi@seaQueue to Programmer [email protected] • 8 months agomessage-square137
minus-square@[email protected]linkfedilink7•8 months ago4.2 megs on one line? Vim probably can handle it fine, although syntax won’t be highlighted past a certain point
minus-square@[email protected]linkfedilink5•8 months agoI’ve accidentally opened enormous single line json files more than once. Could be lsp config or treesitter or any number of things but trying to do any operations after opening such a file is not a good time.
minus-square@[email protected]linkfedilink1•8 months agoYeah, very well may be. LSPs always slow down opening big files, so I usually inspect those with an empty/different config
minus-squareBaldProphetlinkfedilink3•8 months agoTechnically every JSON file is a single line, with line break characters here and there
4.2 megs on one line? Vim probably can handle it fine, although syntax won’t be highlighted past a certain point
I’ve accidentally opened enormous single line json files more than once. Could be lsp config or treesitter or any number of things but trying to do any operations after opening such a file is not a good time.
Yeah, very well may be. LSPs always slow down opening big files, so I usually inspect those with an empty/different config
Technically every JSON file is a single line, with line break characters here and there