10 ms·
Alan Donovan and Brian Kernighan Answer Questions on Go
- gamesbrainiac 11y agoI never knew that the decision to not have versioning built into go was because of the diamond dependency problem. This makes a lot of sense now that I think about it. I wonder what alternatives to manually versioning things the go team is considering. Also, at the beginning the Go team wasn't all that enthusiastic about an IDE, but its great to see that Go will get an IntelliJ grade IDE soon, so that works for me :)
- lostcolony 11y agoI really am not a fan of the lack of versioning, even with that explanation. Of course diamond dependencies are a problem. But they haven't actually fixed that problem; they've just declared a method for picking one of the two dependencies that is ill defined ("whichever one you happen to have pulled in first"). At least with versioning I get told that there's an incompatibility in the expectations between two libraries. With Go's removal of version numbers, they haven't removed any of the complexity of resolving incompatibilities, they've just hidden the fact that there is one. I would have much preferred a strategy of maintaining version numbers, and resolving them via "either you specify what version you want pulled in, or we'll build with the most recent and throw a warning".
- skybrian 11y agoThe fix for Google is to check in all third party libraries locally, so you get the same version as everyone else in the company until someone decides to check in an upgraded version. It works fine and anyone else is free to do the same. But that requires a monorepo that scales and people to test and check in the upgrades, so it doesn't work well for open source development, which is why people are working on alternatives.
- lostcolony 11y agoRight, but you could do that with version numbers, too. The difference between updating from "whatever version was pulled in at the time we first set up the repo with this library" and "current" is no different than updating from "version X" to "version Y", except that you don't know what the differences are, and there's no way to determine that it would be easier (and possible) to update to version X.1, since that includes the fix/feature that triggered the desire for an update, and doesn't break as many things, so requires less work.
- skybrian 11y agoYes, if you're going to check stuff in locally, you need to document which version you pulled to make the next upgrade easier. So it's not like nobody is keeping track of versions (or better yet, git commits). But this can all be done using a separate system. The build system itself doesn't need to know anything about versions. If you look at Bazel, it doesn't let you specify versions for target deps. Only the developer actually upgrading a third-party library needs to deal with open source version numbers, and everyone else can build on their work.
- lostcolony 11y ago"You'll need to document which version you pulled" - so now you're tasked with describing "I got this version" (be that git commit or whatever), rather than it being explicit as part of the package "This is (x) version". So you get to reimplement something yourself, in a non-portable, non-self-describing way. Such an improvement. Of course it could be done in a separate system. It could be done and tracked in a separate system even with version numbers. Go has just chosen to -require- you running your own package manager to make things stable, whereas for most languages it's optional and you can create a repeatable, portable build without it.
- mike_hearn 11y agoThere are fixes for the diamond dependency problem out there, it's not like this is how to build a warp drive. For instance UNIXes have had symbol versioning since forever, they have RTLD_DEEPBIND in glibc, etc. Java is currently noodling around this problem with Jigsaw (though there's already a solution in OSGi) and it looks like for now they'll punt on solving it themselves, but provide the APIs needed for a simple container to solve it instead. It's fine to not ship a solution in version one. But to use it as a reason to not have version numbers at all seems like heading in the wrong direction (backwards).
- d_theorist 11y agoI have never really thought about this problem before, but would it not be possible to: 1. Treat each version of a package as a separate package. If there are two versions required, they are both included. 2. At compile time transform package names to include the desired version number. I may be completely misunderstanding or over-simplifying this problem.
- lostcolony 11y agoFor some things, yes. But there are a lot of potentially tricksy issues in doing that. Imagine a queueing library, for instance. You push something onto a queue created with library A, and then you want to read from library B (A and B are different version of the same library). Just about anything could happen (depending on how the library/language are implemented). You might get an error due to library B reading a data structure formatted for library A. Or you might get nothing back, because library B is checking for the queue in its own registry, while it exists in library A's. Etc. If there is no library-dependent state between calls, or the calls are not being mixed between libraries, you can totally do that, though. A JSON serialization library can totally be supported in that manner, for instance. The queueing library example, if it's only being used to support other libraries or separate functionalities, such that you never have to push onto a queue in library A, and expect to be able to pop it off from a queue in library B, would work, too. But in that latter case, that's not something the library writer can guarantee, it's all about your own usage. So there's a lot of potential issues.
- pcwalton 11y agoMaking the version part of the type generally fixes these issues. Anything that could go wrong will nearly always go wrong at compile time.
- ustolemyname 11y agoSure, that fixes some problems, but I don't understand how that would solve the first example listed above. Can you explain how the compiler would prevent this runtime error? // package a lib-v16.Queue(int32) // Stores in queue for version 16 of lib // package b int32 = lib-v18.DeQueue() // Loads from queue of version 18 of lib, which is empty And even if we accept that you shouldn't have state in the package and the queue should be passed around, now we just have two packages (a & b) that use incompatible versions of lib for potentially no reason.
- psadauskas 11y agoI think that the solution to this problem is one of the few things that nodejs got right. Instead of declaring a global dependency on `require("D")`, you assign it a variable name. Then, each package can declare its sub-dependencies, and even when the versions differ, the different versions are kept in a different scope. https://nodejs.org/api/modules.html https://nodejs.org/api/modules.html // Package A: import B from "B"; // A/node_modules/B/1.0.0 import C from "C"; // A/node_modules/C/1.0.0 // Package B: import D from "D"; // A/node_modules/B/1.0.0/node_modules/D/1.0.0 // Package C: import D from "D"; // A/node_modules/C/1.0.0/node_modules/D/2.0.0
- jasonwatkinspdx 11y agoI'm convinced this is the right approach: dependencies should be purely local to a module. The tooling should make it easy to detect you have a diamond, but let each module get what it needs. As generally everyone moves towards more continuous update and integration, at the end of the day it's all gonna be sha's anyhow.
- wtetzner 11y agoBut what do you do in a typed language? For example, suppose you have modules A and B, which depend on module C. Let's also say that module A has a function foo that return a value of type C.t, and module B has a function bar that accepts a value of type C.t. Now let's say that module A is depending on version 1.0.0 of module C, and module B is depending on version 1.5.2 of module C. Does B.bar(A.foo()) still work? Is type t the same in C version 1.0.0 and 1.5.2?
- incepted 11y agoNo, it doesn't really make much sense. The diamond dependency problem only happens when two indirect dependencies are identical but on different versions and that these two versions are incompatible. That's two big if's. 99% of the time, it's not a problem. Notice first that this is a pretty rare problem since libraries tend to be backward compatible these days. And if you happen to come across a bad behaved one, you simply exclude the one you don't want from the graph, problem solved. This problem has been fixed in Maven for almost ten years now, the only reason why you would not implement this crucial feature in a version manager is laziness.
- voidlogic 11y agoEveryone seems to overlook this, but Go has had LiteIDE for a very long time and it keeps getting better.
- dawkins 11y agoI thought the same. I use it every day and its great. I dont understand why it doesn't get more traction.
- vox_mollis 11y agoBecause visually, it's reminiscent of Eclipse 1.0. For better or worse, a sizable proportion of developers choose IDEs on the basis of looks.
- Vendan 11y agoHeh, I choose IDEs based on performance, not looks, and liteide is blazing fast compared to anything else I've used.
- AsyncAwait 11y agoI'm not sure if the Intellij Go Plugin is going to be made into a separate IDE, but it's already available for their other IDEs as a plugin and they have a team improving it constantly. Notably, it also works with their open-source IDEA Community Edition. https://github.com/go-lang-plugin-org/go-lang-idea-plugin https://github.com/go-lang-plugin-org/go-lang-idea-plugin So far the best "Go IDE", I've used.
- KyleBrandt 11y agoThe recently open sourced VSCode also has Go support now. Good first impression. The docs and type inference stuff are more convenient compared to the oracle plugin + GoSublime for sublime it seems.
- ngrilly 11y agoI thought it was just syntax highlighting. Any link documenting VSCode's Go suppport?
- pjmlp 11y agoThere is a video of the presentation: https://channel9.msdn.com/Events/Visual-Studio/Connect-event-2015/060 https://channel9.msdn.com/Events/Visual-Studio/Connect-event...
- cdnsteve 11y agoFound it: https://github.com/Microsoft/vscode-go https://github.com/Microsoft/vscode-go
- ngrilly 11y agoThanks.
- lobster_johnson 11y agoRemember to install the dlv (which requires fiddling with certs on OS X) if you want to launch and debug programs. If you don't, Code won't complain, only silently fail to launch the program.
- incepted 11y ago> In general, Go strongly encourages being explicit about errors. That's completely incorrect: it's trivial (and common) to just ignore errors in Go: ok, _ := Foo() Checked exceptions don't let you get away with this kind of sloppy programming.
- ngrilly 11y agoIt's also trivial to "just ignore errors" in a language based on checked exceptions: try { ok = foo() } catch (Exception e) { // Do nothing } Checked exceptions don't save you from "this kind of sloppy programming".
- Retra 11y agoAnd it'll happen frequently, because if you're just trying to test out `ok = foo()` and you're not sure if it'll work, then you've got to write four lines of awful boilerplate and go read an API reference just to get it to compile. Checked exceptions are supposed to encourage correctness, but there's no fudge room for playing around, so they are very not fun. As an aside, I once tried using a crypto library to do something fairly simple (encrypt a file I'm writing to disk), and I had to handle a whole stack of exceptions that I had no clue how to handle. So what can you do? You should be able to write code that provides sensible default behavior, but checked exceptions make you work to just get that behavior, which is not how default behavior is supposed to work.
- incepted 11y agoIf you don't know how to handle an exception, just add it to your `throws` clause and let a caller handle it. That's the whole point of exception: letting you choose who is the most appropriate to handle the error. Return value errors like Go implements forces everyone to care about all errors, at all times, even those they can't handle, which is why you see the pattern ok, err:= Foo() if err { every ten lines in Go sources.
- Retra 11y ago
- nothrabannosir 11y ago>> ..., and extreme abstraction capabilities in high level languages like Common Lisp, ... > Go has everything you mention in both of your lists of desirable attributes (depending perhaps on what you mean by "extreme abstraction") "perhaps"? By whose definition would it ever even come close to "extreme abstraction"? All of us assembly programmers, maybe? Don't get me wrong, I use Go where it makes sense. It has pros and cons. I'm literally programming Go right now. But "extreme abstraction"... you need more than "perhaps" to qualify that. Or was that his point and did I just completely miss the joke? Actually, that's probably it.
- howeyc 11y agoYou missed what Donovan said, which answered the question. Obviously PL-enthusiasts (give me all the shiny! all the time!) wont like the answer though.
- deleted 11y ago[deleted]
- nothrabannosir 11y agoAbsolutely agree with what he said, and I agree it answers the question. And I agree with what you said, it's not a great answer for everybody, but it's an answer. Yet still, Kernighan said what he said.
- sanderjd 11y agoI don't really understand the claim that generic programming is "shiny". It is an old idea that has been implemented many times. It's totally fine that the Go team left out generics – it's their decision – but denigrating people who lament that decision as shiny-chasing PL-enthusiasts is unfair.
- lynchdt 11y agoThis us utterly hypnotic. Nice work.
- percept 11y ago"The reason it took God only six days to create the universe is that he didn't have to deal with the embedded base."
- atilaneves 11y agoGo is as far removed from "extreme abstraction" as any other language I know. I don't know how it can even for a second be considered to have that desireable attribute. I, for one, don't like abstraction and power just because I'm a PL geek. I admit those are also reasons, but the truth is I use them to make my codebase smaller, simpler, and easier to reason about. For some, achieving that goal means writing for loops. For me, it's never having to write explicit loops.
- 0xdeadbeefbabe 11y agoIt would be a shame if you are only making some things easier to reason about instead of everything.
- rubiquity 11y agoAgreed. There's abstraction and then there's abstraction. I might have been in the camp of Go enthusiasts if my experience with abstraction only included C++ or Java. But once I discovered Standard ML and OCaml I found out how wonderful abstraction can be.
- bkeroack 11y agoI'm not sure many people are arguing that abstraction isn't good for those who are writing the code--that's the whole point of abstraction after all, to make the developer's job easier. The problems tend to crop up for other people trying to decipher and read it. Sometimes also for the machine trying to execute it.
- agentultra 11y agoKernighan's response to the C question was rather odd -- where is this myth that C is only used in embedded systems and drivers coming from? The Linux kernel is still written in C. Ben Klemens, author of 21st Century C, leads the statistical computing group for the research arm of the U.S. Census Bureau. He models complex systems and computations in C. The entire Python scientific computing stack is resting on C. A huge portion of the GHC compiler is written in C. Many AAA game developer studios are writing their engines in C (with vendor supplied C++ compilers, but C none-the-less). And do people really write C89 for greenfield projects today? C99 is pretty amazing and has added some great features to the language. C11 might be the trivial change having only added some atomic operators (depending on whether you think this is trivial) and rescinding VLAs (though most compilers will probably continue to support them anyway). I think Go is a perfectly fine language but it seems like perhaps the group is a little out of touch with the rest of the world judging by replies to questions like this.
- vvanders 11y agoThe trend in games these days is to move to C++ but there is still C used in some places.
- lobster_johnson 11y agoKernighan wasn't the one claiming that C was mostly used for embedded systems and drivers; that was the guy who posed the question. Kernighan only agreed that C is still popular in that space. As for C99, I would love to see some hard stats about rate of adoption. Personally I can't imagine starting out on a new project and not use C99, but then the hard-core C contingency is a pretty conservative bunch. (Are there still systems where you can't get a C99 compiler?)
- agentultra 11y agoYou're right -- Kernighan didn't say that and I didn't intend to imply that he had. Apologies for those confused. The rate of adoption question is interesting. If only there were a foundation or group out there shepherding the community and keeping tabs on such developments. If there is I'd appreciate being pointed to the right address.
- stcredzero 11y agoHere's a solution to the diamond dependency problem: Imports can only be done for a specific lexical scope. Also, imports must specify a particular version. Lastly, calls to a package go to a specific version of the package, and types are defined in a specific version. (This is why all imports must be done for a specific lexical scope.) The same scheme could be used to resolve diamond dependencies in multiple inheritance as well.
- pcwalton 11y agoThat's essentially the solution Rust and Cargo adopt. It occasionally causes strange errors like "expected Foo, found Foo" (where the first Foo was, say, Foo version 1.1 and the second was Foo version 1.2), but the compiler now detects this situation and tries to explain what's going on. I'm certain I'm biased, but in my experience it's been the most robust way to handle versioning that I've dealt with.
- stcredzero 11y agoI proposed this in a Smalltalk newsgroup over a decade ago. The reaction? I was ridiculed. Imports naming specific versions would also allow better integration of code/build into a version control system. Actually, the entire OS should be built with version control in mind from the ground up.
- CyberDildonics 11y agoNo truly good idea will ever escape ridicule.
- bjz_ 11y ago> the compiler now detects this situation and tries to explain what's going on. Oh really? That's great news! I remember having that problem earlier this year and thinking that it wasn't the greatest from a usability standpoint.
- nickpsecurity 11y agoNice interview. Plenty of good details. I mean, there was this slip: "The languages... are either long gone (PL/1) " http://www-03.ibm.com/software/products/en/plicompfami http://www-03.ibm.com/software/products/en/plicompfami http://www.fujitsu.com/fts/products/computing/servers/mainframe/bs2000/software/programming/pl1.html http://www.fujitsu.com/fts/products/computing/servers/mainfr... http://www.iron-spring.com/about.html http://www.iron-spring.com/about.html Next he's going to be telling you COBOL is gone, too. Big time writers' definition of dead/gone in IT has always seemed different than general usage. ;)