660 karma · joined July 2, 2012
I see it the other way around. I'm in favor of generics for Go, but I can't support this design and I think it will have a negative effect on library stability.
Rather than narrowing the scope of contracts to remain mostly orthogonal to existing features, they have it totally open-ended. They clearly didn't want to put too much restraint on what can be stipulated by a contract, and consequently it just feels like a solution looking for a problem (or like they didn't want to to make any hard decisions for which they might be critcized). With contracts as they are, they are incredibly powerful and stomp all over the type system and interfaces in terms of their practical utility. This is not orthogonal design, or really any sort of design, it's a blank page. They feel like a complete abdication of the designers' responsibility to make Go a simple language that tries to only pull in minimal features while reducing overlap. It's context.Values again but far worse. Please stop trying to make everyone happy, it's impossible (and I realize the irony here).
I liked generics when they were going to be super strict (and consequently super simple from the user's perspective), no upper or lower bounds on the type, just essentially a glorified gogenerate. This feels like you all are trying to answer to the critics rather than to the code.
Over time, we've found that a rectum capable of dilating to at least 1.5 inches in diameter is correlated with improved productivity, so try and stay loose throughout the day! There are lube and applicators available in the restrooms, and welcome to Job Corp!
This is the part I always fail to grok in discussions about type systems. For me it is just the opposite: I typically don't find dynamic typing to be worth the trouble, so I fail to understand this sentiment when going the other direction.
Maybe it's because my degree is in mathematics (lots of proofs written out long-hand), and my first language was Java? I have since all but abandoned many of the ideas that Java so rigidly enforces, OOP among them, but static typing just has so many advantages for me that I have no desire to get rid of it.
One thing I've noticed in some recent work is that the static language I'm using (Go) allows me to both be lazier and get more done than comparable work being done in dynamic languages. I'm not reading or writing tons of documentation (I'm reading other people's code directly, or just looking at the types involved and moving on). I'm not constantly handling byzantine runtime errors or having to memorize the arbitrary intricacies of any over-bearing frameworks in order to be productive. I don't need to be on guard quite so much, I lean on static analysis. In general I just don't need to hold so much extraneous crap in my head, it's all spelled out right there in the code and I'm free to think about larger concerns, like the best way to solve the problem at hand. And when I circle back around to some 10-20k line library I wrote 3-6 months ago, I can read, understand and refactor parts of it quickly.
People often talk about developer comfort and speed being improved by dynamic languages, and maybe that's true if Rails solves all your business needs, but for many of the tasks I've work on, that just hasn't borne out over the past 10 years. I have no doubt that dynamic languages seemed a breath of fresh air after fighting with C/C++/Java, but to my eyes Ruby/Python/Javascript etc were always a bridge too far for a lot of tasks.
Looking back, there was always something a bit odd about these folks: namely, that they seemed to be far more concerned than I was about what to do with their time. They seemed to really be concerned about having the "right" kind of job, or the "right" kind of life. When I was working customer service or slinging cocktails at the gay bars to pay my rent and food costs, they were researching grad schools (only the best), or traveling to the third world on short-term humanitarian missions. One took several years off from work without much apparent anxiety. Another jumped from city to city, making large numbers of fair-weather friends and throwing himself into startup after startup, never settling down or really committing to anything or anyone. Another married a successful artist, and raises the kids in Santa Monica. I know a few living very bohemian lives, in high-minded intentional communities, writing books to teach their peers about some obscure facet of culture. Some went into the corporate world, where they adequately fill a suit and sometimes write about M&A on a blog.
I've worked with lots of these types as well of course, in the tech industry. They have no concern about being their own angel, and care a lot about diversity, but have no qualms about asking you to work late, or over the weekend to help "the business" meet its latest pivot. Needless to say, all of these people are white.
My husband's family is white too, although quite poor. His father used to break and shoe horses, and can track an animal through a desert. The sort of man who relies on Medicare to pay for his liver removal surgery, his lymph-node removal, his spinal growths removals, and any other places where the cancer metastasized, but is out fixing a truck engine soon after, with his oxygen tank dangerously close to the welding torch. This happens in the sort of countryside where your trailer gets broken into, and the thieves drag your refrigerator over to their trailer not far away up the dirt road, leaving a trail you can see from space, but the police can't do anything. In an earlier time, he would have solved that problem himself, but he doesn't hear so good, or see so good thanks to a couple of strokes and type-I diabetes. The wife has MS, so he spends most of his time taking care of her.
When the grandfather shot himself, the gun was one of the most valuable things he left behind. Despite losing her retirement to shady financial management, after 30 years as a charge nurse in the ED, the wife couldn't wait to blow what little they got in the will on a new hot tub. Better enjoy it now.
Of course they'll have to sell their sandy little plot in the next year or so anyway, before it becomes worthless due to the water table drying up. My husband does what he can to bail them out when unexpected bills arrive, and maybe he ought to spend more on their comfort. God knows his sister can't help from behind bars.
My family is different, my parents paid for my bachelor's, just not my master's, but we can tell some similar stories from a couple generations back. My grandfather had to cut off his own father during the depression, essentially dooming him, because the old man stupidly lost everything he owned, and his only hope was the wage my grandfather earned, after a career as a ship's engineer, shoveling coal into the furnaces of buildings in NYC. This is the ugly side of progress no one wants to talk about: how people get left behind. How the parents fight a losing battle, and the kid grows up knowing their only hope is to get the hell away from it all. These callous things long to be forgotten.
I'm not hiring artists I'm hiring engineer's. I'm not hiring your for your gorgeous code in x language, I'm hiring for problem solving skills and communication.
I agree with the second half (problem solving and communication) but take some issue with the the way you dismissed the art of it all. Maybe we have different ideas of what an artist is?
I tend to think of software in more blue-collar terms myself, perhaps more like a carpenter (who has to consider more than just aesthetics, but certainly can't ignore them) than a violinist, but my earlier comment was just continuing the established metaphor. Either way, I get the sense we agree more than we disagree here.
If your engineers aren't writing clean, readable, maintainable code that solves problems as simply as possible (ie, gorgeous), I'm not sure your hiring practices are doing you any good.
If that code is unsatisfactory for some reason, I'd rather figure that out after writing it, based on concrete evidence, than during an upfront design meeting with folks who likely won't be doing the actual work, but often feel the need to impose themselves in arbitrary ways. When a team focuses on excellent communication through writing, I find less planning and verbalizing is necessary, and a lot more gets done.
As a partial aside, one of my greatest annoyances when starting a new job is when after being grilled for technical skills during the interview, they walk you in to a messy, amateur codebase, where many of the ideals discussed during the interview clearly haven't been applied, but no one seems to acknowledge it. This has happened to me repeatedly, enough so that when these sorts of questions come up during the interview, I mentally start preparing for the disappointment. People sometimes seem to take more pride in trying to rattle candidates than they do in building anything admirable. Luckily, there are many fine places to work where the team can be honest with itself and with candidates. I don't really care about the current state of projects when I'm starting; I don't mind being a janitor (except in extreme cases). Just don't start our relationship off with a load of BS. I feel like this is such an elephant in the industry. A lot of our code is bad, real bad, but we can't admit it.
In all seriousness, I do wonder how these billionaires can resist just riding off into the sunset. Have some damn dignity.
I've worked on systems that allocated and freed hundreds of GB every 10 minutes, written in Go with no such issues.
Garbage collection has become very fast in recent versions of the language. It's quite painless now, and we did struggle with it in the past. I'd take the current GC over dealing with other strategies unless you are a very specific, >60fps kind of situation. We literally don't think about the GC anymore.
Random stats from one of our busier nodes, over the past 20 min: 40GB currently in use, 391GB allocated (and freed) in the last 20min average of 2.6ms GC pauses every 70.6s 95th percentile on GC time is 7.26ms
For dependency management, there's a lot of tools that make things more automated and I think probably offer people what they are expecting/used to from other environments. This has been a sticky point for sure. I've settled on a bare bones solution that seems to work well: just using git submodules in the vendor directory within the project repo. Does everything I need (pin to version of a fork, build immediately after a clone and a submodule update --init). As of Go1.5, the vendor directory is supported by the compiler, and it will look there first to resolve dependencies. While this does work with recursive dependencies, you will want to flatten the dependency graph as much as possible if types are being used across multiple deps because types are distinguished by their full import paths. This encourages breaking things into modules so I'm ok with it.
First-tier support is a problem I have no doubt, but not one we've suffered from personally.
I'd say that debugging comes up a lot too, and Go doesn't have an official, reliable option for debugging. The Delve project is getting close to that though it looks like. I personally debug with the stdlib pprof package (provides an http server that prints stack traces for all goroutines currently active, allows cpu/memory/blocking profiles to be requested), print statements, general testing/experimentation and newrelic.
The busiest node traffic-wise had average GC time over the past 20min of 3.4ms every 54.5s. 95th percentile on GC time is 6.82ms.
That node is sitting at 36GB in-use right now, and has allocated (and freed) an additional 661GB over the past 20min.
Can't really speak to how fast this is vs other environments, but it's smooth sailing overall. /shrug
I'm simply proposing that the criticism is founded on actual flaws with the piece, rather than it being too complex to be understood by its detractors.
According to a copy+paste of the text into http://sarahktyler.com/code/sample.php, the article as a whole reaches Flesch-Kindaid grade level 7.
Honest question: if a company receives investment from Peter Thiel, do the founders have any choice but to express the opinion above?
Personally, I find 2) unbearably obnoxious, but it's something I'm willing to forgive if they provide evidence in the affirmative, as Federer certainly has. I think we have to permit a certain amount of elitism, because it would be dishonest to expect that these players refrain from acknowledging their positions within the respective pantheons of their sports.
The man is obviously flawed, but a lot of the criticism is petty and no better than Jordan's own kvetching. I'm sure we all know plenty of other ego-maniacs who don't even have something real to brag about.