News for hackers. Stuff that matters.

A comment on The State of Go. Parent comment

Re:The State of Go by _ak on Wednesday May 27, 2015 @06:42AM (#9610449)
The "systems" in "systems programming" can also be interpreted to refer to Google's systems. After all, Go was designed to solve Google problems in a Google environment. That's how I always understood it.
[ Parent | on HN ]
Re:The State of Go by pjmlp on Wednesday May 27, 2015 @08:23AM (#9610814)
In CS speak that is actually known as "distributed systems", not "systems programming".
[ Parent | on HN ]
Re:The State of Go by learc83 on Wednesday May 27, 2015 @01:04PM (#9612763)
In modern CS speak yes, but the creators of Go were apparently referring to infrastructure types of programs; web servers, database servers etc...

Here's a quote from the announcement talk

"And it's a systems language in the sense that we intend it to be used to write things like web servers"

[ Parent | on HN ]
Re:The State of Go by pjmlp on Wednesday May 27, 2015 @02:59PM (#9613569)
If it has servers in the name it is distributed computing.

How modern is modern CS?

I took my CS degree around 20 years ago with focus on computer architecture, compiler design and distributed systems.

Distributed systems literature used in the degree went back to the early UNIX days.

[ Parent | on HN ]
Re:The State of Go by learc83 on Wednesday May 27, 2015 @06:09PM (#9614724)
>How modern is modern CS?

The creators of Go were on the team that built UNIX, and they clearly have a different meaning for the word systems.

They were using it to refer to infrastructure, without making a distinction whether it was distributed or local. Something like a compiler would be "systems" program under this definition.

I agree that distributed systems, and systems programming are generally accepted terms of the art in CS now, and even 20 years ago.

[ Parent | on HN ]
Re:The State of Go by olavk on Wednesday May 27, 2015 @03:23PM (#9613690)
Ah, than makes sense.
[ Parent | on HN ]