On Saturday, September 24, 2011 at 9:14:22 AM UTC-7, 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!?
>
Objec
Go also support first-class function which is an idea brought from functional
programming. Anyhow, in my opinion, you shouldn't be too dogmatic about a
particular paradigm. There are cases that can be solved elegantly using a
particular paradigm and there are cases that will lead to further unne
> Can I say Procedural is better than OO?
Better at what? It depends what you are trying to do.
The novelist and aeronautical engineer Neville Shute wrote "It has been
said an engineer is a man who can do for five shillings what any fool can
do for a pound".
These days we accept that some eng
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)
