|
|
|
|
|
by kisstheblade
1681 days ago
|
|
"No inheritance - no more digging through the massive world-tree of objects to find the code that actually does things." You still have interface methods? I had problems navigating a new codebase and find the places "actually doing things". Some object was passed in somewhere which mysteriously implemented a one method interface defined on the spot in the other go file. I.e. the implementation had no relation to the interface which was obvious without a lot of searching and finding the right implementation. Also passing in functions (callbacks?) all over the place is a little messy at least for a newbie. It was hard to find where the functions where called and at what point and how the program flowed. (this is hard to explain but maybe somebody gets the point...) edit: somebody else touched on what I also meant: " duck typing make refactoring and understanding new codebases error prone" Also the modules and dependencies management surely is a joke? Pulling stuff from github willy-nilly? Quite bad in any case when compared to maven where you have a local repository with all the dependencies (so they don't change or disappear from the internet so that you can actually build your software 5 years later, exactly in the same way) |
|