4 ms·
There's multiple good reasons for using a framework. 1) It enforces appropriate design patterns for the task at hand. 2) It produces code structures that are
by crdoconnor 10y ago
There's multiple good reasons for using a framework.
1) It enforces appropriate design patterns for the task at hand.
2) It produces code structures that are standardized rather than idiomatic.
3) It provides a superstructure that allows the integration of a variety of different plugins without having to write a lot of boilerplate.
I've no doubt this applies to go as equally as it applies to any other language.
That said, bad frameworks (which is most of them) are often worse than none at all.
- PaulRobinson 10y agoI don't think you read my comment, or at least if you did, you didn't understand the point I was making. Micro-services are the appropriate design pattern that means frameworks are redundant in a micro-service architecture. Code structures do not need to be standardised in a service you can read the entire source code to in 20 minutes and replace in a few days if you need to. Micro-services do not want or need the integration of a variety of plugins, and little to no boilerplate is required.