010a

Every single example he gave looked, in my opinion, better the new way. This entire article is just a vast list of opinions about their interface design disguised behind some inappropriate grand declaration of truth.

Isn't that... the entirety of Trump's platform?

Code quality can only ever be as good as your understanding of the problem domain. A more accurate statement would be "Problem domains are rarely perfectly understood."

Only in instances where you don't care about any of the other return values.

'encoding/json' is definitely more powerful than Python's JSON package. 'http' is similar.

But I will say that 'flag' isn't even _close_ to being comparable to argparse. flag is, like, the bare minimum you would need to write a command line application that accepts flags and generates help text. There are dozens of libraries for Go that more closely resemble argparse because flag's capabilities are so limited.

One of the reasons why Go is so unwieldy is because it is designed to be simple. Its very easy to mistake simplicity for elegance; the reality is that simplicity can lead to elegance, but it doesn't have to.

Go is an interesting language when you have a project with dozens of developers, because it explicitly, by design, does not let you introduce any concept of "your needs". Go is not ashamed of the fact that it has one way of doing things, and that way is rarely elegant. But it _is_ effective.

Go is far lower level than Python, which makes the term "low level" fine. Its like calling some color swatch "black" then arguing "that's not black _enough_ to be black". Any definition we give for an absolute term like that will be fundamentally arbitrary, but we know right from wrong when we see it.

A language does not have to replace C to be "low level". You sound like the type of person who, thirty years ago, would argue that C isn't low-level because it isn't assembly.

We can afford a t2.medium or an m3.medium at the price he quoted, which will have better RAM, processing capability, and probably equivalent networking capability, so that isn't really the takeaway point.

I would say that it strongly depends on the type of requests you are handling.

Saying that you can run a 1GB lambda for 1 month nonstop for $32 does not impress me, and its kind of strange that it impresses you.

You could run a t2.micro with the same RAM for $6/mo if you reserve it for a year. And if you want to give that t2.micro a workload where it only has to respond to 1 request at a time, the same terms we are affording the lambda system, then it's no comparison.

Now, for responding to disparate requests every once in a while? Lambda is ideal. You can spin it up and you don't have to pay when it is isn't processing requests. But continuous requests? Hard no.

We can argue that the cost overhead at full load is worth it for the ability to "infinitely" scale with no effort. Alright, that's fine. But let's not pretend that it is "cheaper".

And ECR is pretty much just hosted Docker Registry. Try using it versus something like GCR or just Dockerhub and even it starts feeling antiquated.

If you're interested, Stackpoint offers a really cool (seemingly free) service to bootstrap and manage K8S clusters on AWS, DigitalOcean, and Packeg [1].

[1] https://stackpointcloud.com/

I disagree completely. How do you reconcile products like Lambda, Dynamo, Elastic Beanstalk, IoT, Lumberyard... They have a laundry list of products which do meet your criteria of being designed for devops people to bring existing infra in, but they have plenty which clearly have app level components that devs would need to interface with. AWS has something for everyone.

Which doesn't matter if you are based in a country that doesn't respects US law.

The advantage of language constructs helping you, but the disadvantage of finding devs to actually build with them.

I would emphasize that, in many of those examples, Go wasn't a very viable choice when the apps were originally written. Twitch chose Go back at ~1.2 (2013), when Erlang might have made more sense.

Today, for companies making a similar decision now, that argument is a bit different. Go 1.6/1.7 obviously has massive improvements in the areas the article outlines. But, in Erlang camp, we have Elixir making that more enticing.

I would argue Twitch made the right choice. They will have a magnitude easier time finding devs to support a Go system over an Erlang system. And their product never suffered for it. And they are clearly a force behind making Go better, which has helped more people than just them.

Golang's more recent async GC changes begin to resemble Erlang's per-process GC in how they would affect overall system performance.

When people talk about Go's GC freezes, they're talking about the spinup/spindown time before the async GC kicks in. That part is incomparable to Erlang, but its a part which has gotten much faster recently, specifically through virtue of becoming smaller.

I didn't find that Udacity course all that helpful. Especially toward the end, where it could really shed some light on the actually advanced Kube topics, the videos shorten to 60 seconds each and he just glosses over topics without any explanation why they matter.

I got this one for the first time today as well, minutes before the site went down.

Redshift is definitely "based" on Postgres, but its distributed systems components are probably proprietary enough that the concern is valid.

He absolutely deserves the title in this case. What will happen in the UK/Britain over the next decade will likely rival the significance of the Magna Carta, except in a mostly-negative way. And it is his fault.

100G fiber? I had no idea France was running 4x EDR Infiniband to their citizens' homes.

And in terms of larger names, Spotify's infrastructure was recently switched to Google.

https://news.spotify.com/us/2016/02/23/announcing-spotify-in...

The world trusts the United States to correctly manage the foremost reserve currency. Many countries trust our military to protect them in times of need.

I agree that making it more international is ostensibly a good thing, but in reality I haven't seen a good argument that the world, or the internet, would actually be better off.

Specifically, while countries like the US don't have perfect human rights track records, we are much better than countries like China. And if we're going to give them even a bit of control of this infrastructure because "its the right thing to do", well, I can't agree with that.

Yes, there are practically philosophical questions like "who gave us the right do manage this" or "what happens if we screw it up?", but in reality we're doing a pretty great job and until that changes I think internationalizing it would just be trying to fix something that isn't broken.

The people who wrote that are not the same people who write the database.

Great meme bro.

I really feel like this isn't a general problem, but rather a problem with a subset of development environments.

Node (backend) definitely doesn't have a similar problem. Want an express app? Install node -> npm i express --save -> node app.js.

Go doesn't have it either, whether you're using the base tool or GVM. Python requires a minuscule setup in virtualenv, but beyond that its straightforward. Elixir and Rust are straight-forward.

In fact, the only environments where I've ever thought "wow this is a configuration nightmare" are front-end web dev, Ruby, and in really complex python apps, obviously notwithstanding less common app environments like C/C++.

Finding developers is hard. Finding developers who know those languages to support your software is near impossible.

Its hilarious how this comment alone exemplifies exactly what he's talking about when he says that conservative voices are being marginalized in silicon valley. We need to make sure we brand the post with his name so us cushy liberals can be protected from these mean and different viewpoints, right?

Slippery slope argument, but I think its pretty convincing. I'd argue that we wouldn't see it surface directly in any UBI bill, but rather we might start seeing UBI being used as an argument to get other restrictive bills passed.

Like: present case study which says that low-income individuals are at the greatest risk for tobacco dependence -> low-income families benefit the most from UBI -> anti-tobacco politician can now make the case that the government is subsidizing their tobacco usage -> argument from guilt that tobacco sales should be further restricted universally, not just with basic income.

We've seen dumber things happen on capital hill.

... Which literally describes why Automattic bought it. They own Wordpress.