Viewing profile — technoweenie
technoweenie
HN member- Joined
- Sun, Jul 20, 2008, 3:40 AM UTC
- HN karma
- 1,562
- Public activity
- 256 items
- HN profile
- View on Hacker News ↗
About technoweenie
Recent public activity
-
comment
Comment #47502562
https://tangled.org builds on atproto for the social features.
-
comment
Comment #44918524
I'm really happy to see large file support in Git core. Any external solution would have similar opt-in procedures. I really wanted it to work seamlessly with as few extra commands…
-
comment
Comment #21114700
I just format the message in my text editor and paste it back into the commit message box before submitting.
-
comment
Comment #20921808
> Realistically how many hours of work went into this upgrade process then? Eileen wrote about the actual process a year ago when GitHub upgraded from Rails 3.2 -> 5.2: https://git…
-
comment
Comment #19684083
FWIW I've always heard it described as a thundering herd. Though, your description is spot on, according to Wikipedia [1]. The problem the article discusses is called a cache stamp…
-
comment
Comment #19683980
Groupcache is one implementation in Go. However, it uses its own in-memory cache on your app servers instead of an external cache service. https://github.com/golang/groupcache http…
-
comment
Comment #12540467
We typically run go's built-in server behind nginx. There's no need for something like gunicorn in go.
-
comment
Comment #11407506
The first time we announced svn support, it WAS a joke: https://github.com/blog/31-back-to-subversion
-
comment
Comment #11120481
GitHub also supports txt and other common document formats: https://github.com/blog/2061-attach-files-to-comments
- comment
-
comment
Comment #10050792
Here's as close to an official response that I've seen publicly: http://www.quora.com/Why-is-GitHub-for-Mac-not-open-sourced/...
-
comment
Comment #9735416
Correct. Though I wouldn't say the company is any less remote friendly than it used to be.
-
comment
Comment #9701342
How do you handle a custom GOPATH like that when the current repository needs to be in there too? We've tried manually symlinking the repo dir into the custom '$GOPATH/src/github.c…
-
comment
Comment #9647306
Migrations stay pretty small. Most of them just add a column or index. We also have to make sure tables aren't too hot to migrate. See a previous post for more on that: http://gith…
-
comment
Comment #9646992
That's just a special staging server for Venture Brothers nerds (no one else wants to type all that out).
-
comment
Comment #9353277
Yes, that's really important for the Git LFS project to us. Of the languages that we're comfortable with, it's the only one that met that requirement. I feel like there have been a…
-
comment
Comment #9345137
I honestly hadn't seen git-bigstore. Git LFS started out as a Git Media update, actually. We changed the name pretty late in the process so that it didn't clash with existing Git M…
-
comment
Comment #8847507
I think the main take-away with this post is that static sites for docs are awesome. GitHub uses [nanoc]( http://nanoc.ws/ ) for the [API documentation]( https://developer.github.c…
-
comment
Comment #8590441
Imagemagick can convert a PSD into a PNG.
-
comment
Comment #8322343
Work has started on the move to 3.2: https://twitter.com/charliesome/status/511517393038753794
-
comment
Comment #8260975
We use MySQL with ActiveRecord primarily (with a few exceptions). So that's all Users, Repositories, Issues, etc. Git data gets stored with Git on separate file servers.
-
comment
Comment #8245469
The query annotations show up as a mysql comment next to the query. I don't know if we have any automatic indexing of the annotations themselves. We try to stick to ruby/rails sinc…
-
comment
Comment #8245434
> Basically, what makes GitHub's process different to the decades-old "grep the slow query log and run an EXPLAIN"? Sam's chatops tools opens this process up to a lot more people t…
-
comment
Comment #7917252
Riak Search will do this for you. The Riak key/value store also has post-commit hooks that you can use: http://docs.basho.com/riak/1.2.1/references/appendices/conce...
-
comment
Comment #7852160
Whatever happened, happened. There's no rebasing involved. There's just a lot of jumping around to various tags at different points in time.