What 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.
Comments
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
What 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.
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.
Not just for continuing development in general, but it would be nice for potential contributors too!
no, did you even visit the link?
what's inside "browser.go" then?
did you not see the 20 other go files in that repo?
I've seen, but the point is still valid.
Did you even look at the repo? There are many files.
Answered that in other comment
I've seen them and point is still valid.