Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

None of the Go ideas are new.

And in 1981 there were already application servers, running in multiprocessor machines using Multics, UNIX and VMS, just to name a few operating systems.

Personally I see Go as a better C, nothing more.



Interesting, I didn't know there was multi-core even back then.

But still, at least, they weren't as common place as they are now.


"Personally I see Go as a better C, nothing more."

Which is a good thing, right?


Sure, we need safer systems languages.


To be fair, the way Go uses interfaces is new.


Nope, not even. SML apparently did so, and probably others.


The only thing new about them is that you don't need to write "implements" or something similar.


It is more subtle and powerful than that.

By placing the contract at the use of a type with an interface rather than at the declaration of a type you effectively introduce a form of duck typing to a static language.

You can write an interface for a type long after the type has been declared (or been declared by someone else). Interfaces can be defined and used without having to go back and change existing code. This is very lightweight.


Still, there are a few functional programming languages that offer similar concepts. Scala is one of them, as a few in the ML family.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: