However what we're really arguing about is negligible micro-optimisations anyway so it's a little silly to say one is faster or slower than another. You're not taking into account moving your hands from the keyboard and to the mouse, shacking it to find which where and on which screen your mouse cursor is located, and then putting your hands back on the keyboard after the resize. Quickly moving focus to 1 random pane out of 6+ is also a single input, whereas with keys it can be up to ~(total number of panes - 1). > For things like altering split-pane layouts, mouse remains king for both quickly & precisely adjusting width and height - at the same time, no less. I could write a config file using golfed Bash and say "but you should know how to read and write Bash" but people would understandably dismiss that saying it's still not user friendly and I don't see your point here any different. I also agree with your frustrations with the replies about "people who know how to use a terminal know how to use JSON" sure they do but that doesn't mean it is appropriate usage of JSON. ![]() I think the reason JSON is popular for config files is because it's easy to implement rather than easy to maintain and I see JSON as a regression from the TOML / INI etc formats that used to be commonplace beforehand. This is less of an issue with other formats because you can often comment out lesser used directives. ![]() ![]() The other issue I have with many JSON config files is they don't always contain all the options, so you end up having to search around for what the right directive is to add to a particular config file (this is my biggest gripe with hacking VS Code config files). The lack of comments in JSON is an often raised point and it's really useful being able to add comments in a "living" config file. JSON is meant to be machine readable rather than human writeable and while I don't mind reading through JSON files, I really don't enjoy editing them because it's easy to break (eg including a trailing comma on the last entry in a map or array).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |