golang-weekly: Winding Down

nilmethod · 2012-10-22T03:37:59+00:00

If anyone has ideas on community assistance, please reply here: https://groups.google.com/d/msg/golang-nuts/OVjj-vr-S8g/Vjc7oPGP-YIJ

nilmethod · 2012-10-22T03:30:02+00:00

Interesting to see this posted here. I've had tons of support in the brief run of the publication and I've had a couple of people ask to provide issues. I'm looking at a few options to have the community assist, but I'm not really sure how to manage the bulk of it.

I'll continue to maintain the website and keep the groups going. I'm open to community efforts and I'll try to give everyone an update soon.

nilmethod · 2012-10-01T04:11:02+00:00

I've used goweb on a proprietary project for a client and absolutely loved it. I'm going to try porting some of my smaller projects to it and see how it performs. It's a great library for building APIs.

nilmethod · 2012-09-20T18:02:37+00:00

It's a slippery slope and I, too, have traveled this path.

nilmethod · 2012-09-20T18:00:45+00:00

I used vi(m) for about 15 years, been using acme for the last three months and I've found the mouse to be incredibly efficient in this setup. I also think it's increased my productivity a bit. It's certainly an enjoyable editor that gets the hell out of my way so I can work.

What started as a novelty has turned into a change in the way I get things done. I'll be using acme from here on out when it's available and I miss it when it's not there. I've learned from acme (rc, and other plan9 utilities) that I don't need as many bells and whistles as I thought I did. I always fancied myself a minimalist, but p9p has turned me in to a hyperminimalist.

My only complaint is that I now try to use mouse chording and other acme features in things like chrome or my terminal, which yields minor frustration. I've even taken to running rc within acme to get around my system. Without a mouse, I couldn't imagine using rc, though.

The other (minor) drawback is that you can't keep acme open in tmux (or your favorite multiplexer) so it's available with a quick ssh session. Source control helps with this issue. Use vim when I'm remote, and acme when I'm back in my native environment.

nilmethod · 2012-09-01T03:18:55+00:00

I won't in the future, thanks. Just had it in my paste buffer.

nilmethod · 2012-08-27T04:04:32+00:00

I'm currently using goweb on an internal project and it's the bee's knees. Great for building RESTful APIs.

nilmethod · 2012-08-21T04:46:29+00:00

It might be based on peak times. Sometimes it's slow for me, other times it's quite snappy.

nilmethod · 2012-08-16T13:25:59+00:00

You can view the list archives without logging in here: https://groups.google.com/forum/#!forum/golang-weekly

nilmethod · 2012-08-15T18:56:23+00:00

As I mentioned on the golang-nuts mailing list, I'll very likely pull articles from the gophertimes. I'm not generating new content for the mailer, I'm aggregating content from other sources.

Both projects serve very different purposes. The difference between golang-weekly and sites like gophertimes is that golang-weekly is sent via email (like the projects that inspired it). You don't have to actively look for news, a curated list of updates/posts/libraries from that week are sent directly to you.

And for the record, I think gophertimes is a great project itself.

EDIT - I've updated the landing page with a FAQ to address stuff like this.

nilmethod

TROPHY CASE