If I could upvote this twice, I would. You've managed to put words on something I've been struggling to articulate.
Your point about using Go's type system (esp. interfaces) rings particularly true. When I finally figured out how to effectively use the type system, I suddenly found myself writing extremely malleable code. You can move data types and functions around quite freely, and this makes it easy to design & refactor without losing your place.
The flip side, as you say, is that extreme flexibility requires you to build your own skeleton.
BTW, are you github.com/thejerf? If so, I've contributed to Suture, and use it quite often, so thanks for that.
Your point about using Go's type system (esp. interfaces) rings particularly true. When I finally figured out how to effectively use the type system, I suddenly found myself writing extremely malleable code. You can move data types and functions around quite freely, and this makes it easy to design & refactor without losing your place.
The flip side, as you say, is that extreme flexibility requires you to build your own skeleton.
BTW, are you github.com/thejerf? If so, I've contributed to Suture, and use it quite often, so thanks for that.