3 ms·

There are breaking changes like every second minor release, functionality gets removed, dependent repositories get deleted/renamed/moved by author. PRs are disc

There are breaking changes like every second minor release, functionality gets removed, dependent repositories get deleted/renamed/moved by author. PRs are discussed on the wrong level and author is very opinionated. Do not use this framework unless you want to end up in an inconsistent mess!

chuhnk 7y ago
Thank you for the honest feedback. We're moving fairly quickly in regards to the evolution of the framework. Some of that results in breaking changes and you're right we haven't established the right channels for communication. To be quite frank, open source and public library maintenance was never my goal or part of my experience, I build platforms and remain mostly behind the scenes. So I apologise for the pain but hopefully people have found the framework to be useful despite some of the issues.
- volkandemirel94 7y ago
  I like the way the author releases minor fixes. 1.14.0 - Remove the consul registry. What have people to do who're running hundreds of microservices in prod relied on go-micro with consul registry? Any migration path without stopping the world? What about the cost of person-hours we need to spend changing the code everywhere? The business wants to run the services 24x7 and does not depend on the mood of the third-party framework author.
  - chuhnk 7y ago
    I'm assuming you're from a certain large corporate from whom no one actively engages our community or makes any comments on PRs or creates any issues or contributes anything for that matter and does not actively pay for support. As a developer and user of open source I completely understand your pain. As a maintainer who has built and managed this project alone for the past 4 years I would tell you that you have many options in how you make use of a completely free open source project with a liberal Apache 2.0 license. You are entirely free to fork the project, pin your dependency to a certain release, to actively engage in the community, to file an issue when you have concerns and to of your own volition use something entirely different if you are unhappy with your usage of a free tool. We are in the process of moving from a totally free open source project maintained by one person to a small team building a product and business around these tools. During that period there may be some pain and issues, we'll move fast and potentially break things and in that make many mistakes but hopefully people will engage to help us move in the right direction. If you are a company who relies on this piece of software for the 24x7 uptime of your business and this adds measurable value to your company then perhaps it would make sense to engage in some sort of SLA or support agreement for this critical software that you currently pay nothing for.

chuhnk 7y ago

Thank you for the honest feedback. We're moving fairly quickly in regards to the evolution of the framework. Some of that results in breaking changes and you're right we haven't established the right channels for communication. To be quite frank, open source and public library maintenance was never my goal or part of my experience, I build platforms and remain mostly behind the scenes. So I apologise for the pain but hopefully people have found the framework to be useful despite some of the issues.

volkandemirel94 7y ago
I like the way the author releases minor fixes. 1.14.0 - Remove the consul registry. What have people to do who're running hundreds of microservices in prod relied on go-micro with consul registry? Any migration path without stopping the world? What about the cost of person-hours we need to spend changing the code everywhere? The business wants to run the services 24x7 and does not depend on the mood of the third-party framework author.
- chuhnk 7y ago
  I'm assuming you're from a certain large corporate from whom no one actively engages our community or makes any comments on PRs or creates any issues or contributes anything for that matter and does not actively pay for support. As a developer and user of open source I completely understand your pain. As a maintainer who has built and managed this project alone for the past 4 years I would tell you that you have many options in how you make use of a completely free open source project with a liberal Apache 2.0 license. You are entirely free to fork the project, pin your dependency to a certain release, to actively engage in the community, to file an issue when you have concerns and to of your own volition use something entirely different if you are unhappy with your usage of a free tool. We are in the process of moving from a totally free open source project maintained by one person to a small team building a product and business around these tools. During that period there may be some pain and issues, we'll move fast and potentially break things and in that make many mistakes but hopefully people will engage to help us move in the right direction. If you are a company who relies on this piece of software for the 24x7 uptime of your business and this adds measurable value to your company then perhaps it would make sense to engage in some sort of SLA or support agreement for this critical software that you currently pay nothing for.