12 ms·
> Go. Go is a systems programming language Not those kinds of "systems". It is funny, it seems initially it was meant to be those kind of "systems", and then i
by rdtsc 13y ago
> Go. Go is a systems programming language
Not those kinds of "systems". It is funny, it seems initially it was meant to be those kind of "systems", and then it pivoted as we like to say, to become a "distributed-server-network-backend systems" not "hardware-kernel-OS" kind of systems. And then creators kinds of winged it and remarked how "well, that's what we meant when we said systems".
As for Rust, yeah, there are already a few projects trying to build a kernel or drivers in Rust. Here is one for example:
https://github.com/charliesome/rustboot https://github.com/charliesome/rustboot
- zhemao 13y agoI think that is the definition of "systems" the class is using though. If you look at the programming assignments, they are all about implementing programs in userspace and not hacking on the kernel. Yeah, I was confused at first too. Not sure how you can call it an "OS class" if students never touch kernel code. Although, apparently one project group did manage to write a kernel in rust based off of rustboot (https://github.com/wbthomason/ironkernel https://github.com/wbthomason/ironkernel).
- rdtsc 13y agoYeah I am a little confused by it. Actually Go or Erlang would be a good choice for this "OS" class and they do seem to have adopted the other "systems" definition.
- scott_s 13y agoIt looks to be inspired by CMU's "Introduction to Computer Systems" course (http://www.cs.cmu.edu/~213/ http://www.cs.cmu.edu/~213/). The professors who teach that course wrote a textbook, "Computer Systems: A Programmer's Perspective" (http://csapp.cs.cmu.edu/public/students.html http://csapp.cs.cmu.edu/public/students.html). I was a TA for a year for a version of that course adapted to the school I did my PhD at. We did the same thing: this course became the required one, and OS became an elective. I was skeptical as well, but after TAing it for a year, I think it is absolutely the correct thing to do. This course instills an understanding of the whole stack of a computer system that exists in user-land: assembly; how programs are executed including the stack, data segments, dynamic memory; code generation; process management and concurrency; memory allocation; network and server programming. The point of the course is how different levels of the system interact, not just studying one component in isolation. It is the kind of course I wish I had as an undergrad; instead, I had to build that knowledge piecemeal during grad school. More people will do user-land systems programming than kernel systems programming, so I think it makes sense to make the user-land course required, and the kernel level one an elective.
- mseepgood 13y ago> it seems initially it was meant to be those kind of "systems" 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" http://www.youtube.com/watch?v=rKnDgT73v8s http://www.youtube.com/watch?v=rKnDgT73v8s I don't think that Google ever wanted to develop a new OS kernel.
- rdtsc 13y ago> From the announcement talk From the announcement blog (and that was the widely circulated quote in tech news not the video transcript): --- Go combines the development speed of working in a dynamic language like Python with the performance and safety of a compiled language like C or C++. [...] And the compiled code runs close to the speed of C [...] Go is a great language for systems programming with support for multi-processing ... --- http://google-opensource.blogspot.com/2009/11/hey-ho-lets-go.html http://google-opensource.blogspot.com/2009/11/hey-ho-lets-go... > I don't think that Google ever wanted to develop a new OS kernel. As the meme goes, they keep using the word "systems", I don't think it means what they think it means.
- wglb 13y agoJeez. These dudes were writing "systems" long before most folks here on HN were programming. To me, and to them, "systems programming" has a particular meaning that does not include kernels. Like it means assemblers, compilers, web servers.j I think they have more credibility about what it means than perhaps you do.
- dbaupp 13y agoBefore many HNers were even born too.
- frou_dh 13y agoIt's a tough crowd when being the authors of both the Unix and Plan 9 kernels isn't sufficient to get the benefit of the doubt on this matter!
- bascule 13y agoRust is a high-level systems programming language. Go is a low-level managed language runtime
- bjz_ 13y agoThis is probably the best clarification I've read regarding the difference between Go and Rust. They operate in different domains, and any competition is out of confusion over definitions (the source of many needless disagreements throughout human history).
- tptacek 13y agoOther than the word "systems", was there any other indication that the Golang team meant to target OS kernels?
- zura 13y agoNot sure about OS kernels, but their intent was to attract C++ programmers, although, they ended up mostly attracting python programmers.
- coldtea 13y agoYou mean, if we assume that the word "systems" doesn't have a well defined meaning, that especially the Go team would know all too well when it used it?
- scott_s 13y agoI define "systems programming" to be programming which must interact directly with the kernel or devices. Doing so requires knowledge of how those systems work. It includes, but is not limited to, writing operating system kernels.
- pjmlp 13y agoI am more into D and Rust than Go nowadays, but I think Go can be used for writing an OS if one so desires. The language is quite similar to Oberon in features. You just need to provide a syscall package for bare hardware. If powerful single user graphical OSs were written in Oberon, why not Go?
- nl 13y agoSystems programming does not mean operating systems. To me it means "infrastructure" - things like web servers, database servers, or the wide range of distributed systems that are currently written in Java (eg, Hadoop).