It is procedural programming with OO seasoning and there's nothing wrong with that for small projects and utilities. Would like to see some case studies on using Go on projects with exceptional large code bases. I really think the all tenants of OOP (encapsulation, inheritance and polymorphism) come into play and are essentially when building large systems that have to be maintained by a team of programmers, but I'm open to see how others are structuring things.
On Saturday, September 24, 2011 at 11:14:22 AM UTC-5, nvcnvn wrote: > > I just read here: > http://golang.org/doc/go_faq.html#Is_Go_an_object-oriented_language > And all of the GO example we have is not writen in OOP way. > So can I say that GO see the benefit of Procedural over OO!? > > For myself, I fell ok with Procedural programming! Just need to stay > come, do some document for your code and that will help me avoid > duplicate of code, or easy to maintain and modify my code. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
