5 ms·
Go, like Java, was designed by people who intended never to write any code in the language, themselves. Both are languages which those individuals designed for
by ncmncm 5y ago
Go, like Java, was designed by people who intended never to write any code in the language, themselves. Both are languages which those individuals designed for use by people less intelligent, careful, and thoughtful than themselves.
The case of Java demonstrates they were mistaken: their estimation of their own understanding was grossly outsized. I don't know enough about Go to say whether that is true of Go's designers.
- aredplug 5y agoEven if that were true, is it a bad thing?
- Skunkleton 5y agoGo itself is a huge project written in Go. What are you talking about?
- lucian1900 5y agoFamously, it even took many years for the compiler to be bootstrapped. That’s unusual in the extreme.
- tmp538394722 5y ago> Unusual in the extreme The most popular python and ruby implementations are written in C, right? Swift is written in C++ It seems not sooooo unusual.
- jacquesm 5y agoPython and Ruby are not from the get-go compiled languages but interpreted ones.
- atrn 5y agoThey had a functioning compiler and decided to concentrate on other areas and it's not too uncommon for a languages's compiler to NOT be written in that language. Afterall Rust relies on the non-Rust LLVM.
- adgjlsfhk1 5y agoOne thing that has been discovered over the past 50 years and applied over the last 30 or so is that writing a bootstrapping compiler for a young language tends to strongly bias the language towards being good at writing compilers (potentially to the detriment of other features). Compilers are essentially graph algorithms on loosely typed data. I think a lot of the reason it took so long for Rust and Julia to be invented is that they are both not very good languages for writing a compiler in, so in the era where all the new languages had bootstrapping compilers, no one would write a language with the sets of tradeoffs they have.
- surajrmal 5y agoI very much agree. In fact, taking it a step further, OS which self-host development also have this problem where they over optimize for an OS good at compiling and not necessarily good at other things.
- mseepgood 5y ago3 years is not that many years (Go is now 12 years old), and that's not unusual. There are other priorities when you have just released a new language.
- ncmncm 5y agoWriting the compiler for your new language in it amounts to wankage, these days. There was a time when doing that helped convince people the language could do practical things, and might be useful because you might not have had a compiler you liked for your dev environment. Nowadays, though, there is so much support for coding compilers in an existing langauge that building one in the immature language means wasting a lot of time, and furthermore makes your language hard to change because maybe the compiler is using something you want to change. There are more impressive things to write in your new language that might be actually useful. Thus, rustc is (mostly) not coded in Rust. Rust's demonstrator project was the guts of a browser, instead. Notably, that project was coded in a language substantially different from Rust both today and at the time.
- WalterBright 5y agoNot only do I use D for all my programming now, I've also gone back and translated my older programs I still use into D. Most recently I converted my ancient (1980s era) disassembler into D.
- cmrdporcupine 5y agoI am not sure why you're being downvoted, you're right. Here's the quote from Rob Pike I find astounding: "The key point here is our programmers are Googlers, they’re not researchers. They’re typically, fairly young, fresh out of school, probably learned Java, maybe learned C or C++, probably learned Python. They’re not capable of understanding a brilliant language but we want to use them to build good software. So, the language that we give them has to be easy for them to understand and easy to adopt. – Rob Pike" [1] (emphasis mine) You and I: we're not smart enough to use modern language features. And it just so happens that the language features and practices that we can handle are the ones that Rob Pike likes and settled on as good in the 70s and 80s. Anything from the last 25 years, we're not capable of understanding. Honestly, part of many bonuses of leaving Google at the end of the month (after 10 years there) is that I hopefully will have the choice not to use Go and its heaps of insulting boilerplate... but I also hopefully won't have to deal with that kind of arrogance. [1] http://nomad.uk.net/articles/why-gos-design-is-a-disservice-to-intelligent-programmers.html http://nomad.uk.net/articles/why-gos-design-is-a-disservice-...
- johnnycerberus 5y agoIn Romania there's an old question to find the character of somebody: are you Roman or Greek? Because if you are Roman, you put practice above theory, you are a pragmatist, skeptic, if you are Greek you will put theory above practice, you are an idealist, optimist, at the expense of hardships in the material world and other potential drawbacks. Rob Pike chose Roman, otherwise it would have cost Google money to train those people and we don't know if those language features could bring any benefits for the kind of software they develop. As he said, they are not researchers working with category theory, instead they program ever-changing software for an imperfect world driven by profits, rather than academic idealism.
- cmrdporcupine 5y agoI mean, I actually work(ed) at Google and this is nonsense for Google developers. The most used and deployed code at Google is written in C++, not Java or Python, and while we have a sane subset of it in our style guide it is by no means dumbed down to the level that Pike seems to imply we need it to be. Google has done fairly fine deploying C++ into production for a couple decades. I haven't found Go superior at all so far, more insulting than anything. And tedious and opinionated in all the wrong ways.
- zozbot234 5y agoGo is really just a modernized Alef/Limbo, and there's plenty of code written in those languages, in their own niches. It's quite a good language for what it's intended to do. (People sure love to talk about its lack of generics, but Java pre-1.4 or so didn't have generics either. It takes time to find out the best semantics and integrate them into the language.)
- erik_seaberg 5y agoPre-generic Java required (un)boxing and runtime casts everywhere, so it wasn’t really safer than a dynamic language, just far more tedious. I’m thankful that we pretty much burned that code to the ground and started over. Those casts are still in the bytecode for the verifier, but at least we no longer have to reread them, and we have warnings when we violate the assurances that they won’t fail.
- fsdjkflsjfsoij 5y ago> was designed by people who intended never to write any code in the language That's false. All of the original developers started writing side projects in Go extremely early on and all of them still write tons of Go including on their side projects. They don't have their ego tied up in their choice of programming language.
- pjmlp 5y agoWhat are you talking about Java? Gosling and others have written plenty of code in Java themselves, plenty of Solaris tooling was migrated to Java (a fact that Bryan Cantrill has complained often in his talks), and it replaced their OpenSTEP efforts, with Java EE being a rewrite from Distributed Objects Everywhere, originally written in Objective-C.
- ncmncm 5y agoThe Java authors were quite open about their absolute preference for Lisp, and their distaste for OO. That Gosling did not fully understand features cribbed from other languages is evident from how broken the Java version of those features are.
- pjmlp 5y agoSurprising opinion given that Java is heavily based on Objective-C. https://cs.gmu.edu/~sean/stuff/java-objc.html https://cs.gmu.edu/~sean/stuff/java-objc.html As for your reference to Guy Steel, he was just one person on a large team, which besides the point above was full of ex Smalltalk and SELF people as well. Maybe learn properly about the Java history?