2. • @lestrrat • Perl/Go hacker, author, father • Author of github.com/peco/peco • Organizer for builderscon
![GoらしいAPIを求める旅路 (Go Conference 2018 Spring)](https://cdn-ak-scissors.b.st-hatena.com/image/square/6c54557dcc4fa1b9b1705a940347689c44967622/height=288;version=1;width=512/https%3A%2F%2Fcdn.slidesharecdn.com%2Fss_thumbnails%2Fgocon2018spring-180415024330-thumbnail.jpg%3Fwidth%3D640%26height%3D640%26fit%3Dbounds)
Vendoring. Generics. These are seen as big issues in the Go community but there’s another issue that’s rarely mentioned — application package layout. Every Go application I’ve ever worked on appears to have a different answer to the question, how should I organize my code? Some applications push everything into one package while others group by type or module. Without a good strategy applied acros
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く