technoweenie

Joined 18 years ago

Karma

1,562

Submissions

256

Member since

Jul 20

\m/

View on Hacker News

Recent submissions

Comment · 7 months ago

https://tangled.org builds on atproto for the social features.

Comment · 1 year ago

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 as possible, so the API was constrained to the smudge and clean filters in the '.gitattributes' file.

Though I did work hard to remove any vendor lock-in by working directly with Atlassian and Microsoft pretty early in the process. It was a great working relationship, with a lot of help from Atlassian in particular on the file locking API. LFS shipped open source with compatible support in 3 separate git hosts.

Comment · 7 years ago

I just format the message in my text editor and paste it back into the commit message box before submitting.

Comment · 7 years ago

> 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://github.blog/2018-09-28-upgrading-github-from-rails-3...

Comment · 7 years ago

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 stampede or dog pile [2].

[1] https://en.wikipedia.org/wiki/Thundering_herd_problem

[2] https://en.wikipedia.org/wiki/Cache_stampede

I wouldn't fault anyone for getting these similar names mixed up though.

Comment · 7 years ago

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

https://news.ycombinator.com/item?id=6121501

https://talks.golang.org/2013/oscon-dl.slide#43

Comment · 10 years ago

We typically run go's built-in server behind nginx. There's no need for something like gunicorn in go.

Comment · 10 years ago

The first time we announced svn support, it WAS a joke: https://github.com/blog/31-back-to-subversion

Comment · 10 years ago

GitHub also supports txt and other common document formats: https://github.com/blog/2061-attach-files-to-comments

Comment · 11 years ago

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 · 11 years ago

Correct. Though I wouldn't say the company is any less remote friendly than it used to be.

Comment · 11 years ago

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.com/user/repo' dir, but it feels really hacky.

Comment · 11 years ago

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://githubengineering.com/using-mysql-performance-schema-...

It's also really important that migrations don't affect the running app code. New columns shouldn't be used yet. Removed columns or tables need to have all references removed first before running the migration. We confirm this with a deprecation helper that sends metrics to Graphite.

That's about all I can answer from the app side :)

Comment · 11 years ago

That's just a special staging server for Venture Brothers nerds (no one else wants to type all that out).