bketelsen

author here - would love advice or tips on how to get dbus running so settings work well and other WMs work like Gnome.

gRPC is a great framework for generating RPC servers and clients, it's a different space. goa is built for creating an entire REST API.

The creator of goa is presenting on code generation and APIs at Gophercon this year. I'm also presenting on goa at abstractions.io in August. I'm quite biased as a contributor, but I think goa is a great solution for APIs because it encourages you to think through the design completely and generates the code from that design. Generated code is idiomatic and clean. You can see me present at the Tampa Go Meetup here: https://www.youtube.com/watch?v=tCFrgWikEX8

I've been using Caddy for at least a year now, and I host several high-traffic sites on it.* I was one of the first people to try the Let's Encrypt support when it was in Alpha. The Caddy team has been amazingly supportive and responsive during the whole process. Last week when I read this post I immediately dug out my personal credit card and donated $75. It's not much, but they add up. I hope others will too. I agree that making a paycheck out of open source is complicated and confusing. Cheers to Matt & team for trying.

* Not HN definition of "high" probably, but still, not joe's blog either.

I use caddy for everything I serve on the web now, and have been for roughly a year. It's an amazingly stable server -- fast and easy to configure. The team has continuously updated Caddy, and been extremely responsive to any feature requests and support questions. https://www.gophercon.com and https://blog.gopheracademy.com are both served (with Let's Encrypt!) from Caddy.

But do you close your doors sometimes?

I can confirm that Caddy + Let's Encrypt is the most seamless and awesome way to run TLS. I did this last night for one of my LE beta whitelisted domains and it took MAYBE 4 minutes. Caddy did all the work. Kudos to the Caddy team for such a great admin experience.

There are times when it might be better to disable comments on your corporate blog. This was one of those times.

SkyDNS supports whatever naming scheme you want to use. You set the names yourself. That means it can be compliant with RFC2782 if you choose, or the names can be semantic -- like Kubernetes uses, with each position in the name implying a semantic meaning "servicename.kubenamespace.domain"

Disclaimer: I invented SkyDNS.

Add this to ngrok [0] and you've got some pretty serious remote collaboration tooling, with security.

[0] https://ngrok.com/

Thanks for the feedback - we're working on our post-conference survey right now. Expect one soon.

Came here to say the same thing. Why is the government collecting secrets of its workers' sex lives? Why is it being stored? All data is subject to theft. The bigger question is why it was collected and stored in the first place. The government is responsible here.

http://www.consumerfinance.gov/ is your best hope. They've got strong power over the banking/finance/credit industry. The bureaus are scared to death of them. Find a phone number/complaint address there and you'll get some action.

I just scanned registrations and don't see you there....

Hats off to you, good sir.

Many kudos to Stripe for funding this. Truly a great gift to the community.

They technically don't. The "go" tool is a programmatic wrapper around the compiler and linker - which live in your Go installation under pkg/tool/$platform The compiler for 64bit Linux is named 6g and the linker is named 6l. The "go" tool wraps usage of these two tools into a program that uses the convention of the GOPATH to figure out where dependencies should be found. If you wanted to do everything without a GOPATH you could. Go find your 6l and 6g tools and play with them a bit.

/usr/local/go/pkg/tool/linux_amd64/6g mygofile.go -o mygofile.a /usr/local/go/pkg/tool/linux_amd64/6l mygofile.a mygapp (disclaimer - this is off the top of my head - haven't manually compiled and linked in years because the go tool makes that unnecessary)

This is one of the best configured and thought-out Docker containers I've ever used. Running this for our project's git repository for several months now, over several upgrades. Really well done.

is it 21Floors now? <bring forth the downvotes>

Looks nicely done. Congrats.

and it still prints "sh: symbol lookup error: sh: undefined symbol: rl_signal_event_hook" every time you run it on Arch linux. The issue (#170) has been open since March of 2014. <yes, whiny people should submit patches>

RSC is awesome.

These are great - I'm already using docker containers for nearly everything I do for development, and now I'm inspired to continue the trend into all the other applications on my system. They're more portable (I keep my zsh aliases in github) and it'll keep my Arch/i3 install cleaner too. Thanks for the tips. I think my next step will be to start assigning the apps to their own workspaces in i3. Great post.

i have - it works fine, and is faster.

I've used LilyTerm, Terminator, and a few others. I've been using gnome-terminal for maybe a month now, and haven't found a reason to change.

I switched from OS X to Linux a few months back, and I'm never going back. I thought like you did originally, that I needed something "standard" like Ubuntu, but found Ubuntu does too many things and installs too many things. Instead I'm now using Arch Linux and i3 Window Manager. It's a long stretch from the beautiful Mac UI that I used for the past 15 years, but as a programmer I can't stress enough how awesome it is not to move my hands off the keyboard for 95% of the operations I do. Almost no mousing required at all. It got even better when I hacked in a few Gnome bits (gnome-session & gnome-keyring) so I could have a more comfortable experience. Nothing will replace the well-written apps you expect on your Mac, but generally if you can live with working-but-uglier apps on Linux you'll be fine. And given that unless you specifically develop apps for Macs, you're probably deploying on Linux anyway, you'll enjoy developing closer to the production metal.

I suppose I should make that more clear. Thanks.

you could always submit a talk on implementing the gopher protocol in Go.

I've tried them all. I went from the extreme of Revel (very rails-like) to straight net/http. I ended up using Goji for my most recent API and really like the feel. It's very close to net/http with just enough candy to make it easier on me without losing straight net/http compatibility.

Great news. I'm not a fan of Docker's new monolithic approach to containerization. Things like orchestration and networking should not be included in docker, but rather pluggable.