3 ms·
http client, UI interactions logic, domain models, utilities like tree operations, browser domain logic and all of that inside single go file? I think you'd m
by tester756 4y ago
http client, UI interactions logic, domain models, utilities like tree operations, browser domain logic
and all of that inside single go file?
I think you'd make your life 10 times easier by splitting it better
- spenczar5 4y agoWhat difference does that really make? In Go, all files in a directory share a namespace. I think the only impacts of splitting a file are build tags and shortening the import list, and neither really applies here. Those components you listed could be in separate packages, but in a program this small that seems merely different, not better or worse.
- tester756 4y ago>What difference does that really make? Depends if you want to continue developing this (or any) project If you want, then it makes huge difference, the faster you refactor it, then the easier the development will be. If you want to stop putting effort into it, then there'll be no difference. One file doing everything is almost always more annoying than stuff splitted correctly.
- euclaise 4y agoNot just for continuing development in general, but it would be nice for potential contributors too!
- 2h 4y ago> all of that inside single go file? no, did you even visit the link?
- lanecwagner 4y agoDid you even look at the repo? There are many files.
- tester756 4y agoAnswered that in other comment I've seen them and point is still valid.