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
and all of that inside single go file?
I think you'd make your life 10 times easier by splitting it better
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.
no, did you even visit the link?
I've seen them and point is still valid.