text
stringlengths
0
1.17k
[1659.14 --> 1663.16] creative ways i love looking at the mailing list because somebody's like i'm writing code like this and i look
[1663.16 --> 1668.72] at him like wow that's so cool uh or somebody goes this is how i do content negotiation with
[1668.72 --> 1674.78] dependency injection and how i like observe you know what people want to render out as a struct and
[1674.78 --> 1679.88] based on you know the header i can then like you know throw it out as json or throw it out as xml or
[1679.88 --> 1685.76] throw it out as html or whatever and so like people solving real world web problems using those core
[1685.76 --> 1691.38] building blocks that i didn't necessarily build myself you know i didn't build content negotiation into
[1691.38 --> 1696.48] martini somebody figured that out through the the building blocks that were laid out so i find i find
[1696.48 --> 1702.26] that awesome it's just super awesome to see that's kind of neat how you can lay down a set of breadcrumbs
[1702.26 --> 1707.94] and you know kind of walk away because your needs are different but others pick it up and take it there
[1707.94 --> 1714.44] yeah absolutely yes i'm looking at the list of available components in the martini-contrib repository
[1714.44 --> 1721.52] you got auth binding gzip render except blank sessions it goes on and on and on i'm assuming
[1721.52 --> 1724.92] you didn't write all these and this is these have been community contributed is that fair
[1724.92 --> 1731.08] yep a lot of them been community contributed i've contributed to um i wrote render and sessions and
[1731.08 --> 1737.80] auth and uh contributed to a couple others but for the most part all the rest are um you know fully
[1737.80 --> 1745.50] community community contributed nice so did you expect this this amount of contributions or were
[1745.50 --> 1751.50] you kind of surprised at martini success and how you know people have uh contributed to the project
[1751.50 --> 1757.18] oh i've been absolutely blown away by the reception of the project i i wasn't i honestly was not sure at
[1757.18 --> 1763.98] all what the go community would think of it because because of uh the use of reflection let's say i know
[1763.98 --> 1768.06] that's like sounds like such a petty thing to worry about but um some communities could be really
[1768.06 --> 1772.64] hardcore about use of reflection and i have gotten a little bit of friction but in general people
[1772.64 --> 1778.12] people have come to be pretty understanding and be like yeah martini is not the fastest thing on the
[1778.12 --> 1783.48] block and me saying that is like we're talking about nanoseconds here it's nanoseconds slower than
[1783.48 --> 1790.84] you know the next framework or whatever um but it man you can write some awesome code with it and
[1790.84 --> 1796.50] and very clean code um one example what is okay i was just gonna ask you for an example go ahead
[1796.50 --> 1802.22] oh cool so one example and this could be linked in the show notes is i wrote a blog post for the
[1802.22 --> 1808.00] go advent calendar which is a really awesome event put on by brian kettleson over at gopher academy
[1808.00 --> 1815.82] and eric saint martin and um they organized this 25 days of christmas kind of thing and each and every
[1815.82 --> 1820.18] single day was accompanied by a blog post by a community member in the go community
[1820.18 --> 1828.34] and uh i wrote for day 11 i think uh about how to build a simple christmas list app in martini
[1828.34 --> 1836.82] using some martini contrib um packages like render which is for html templating and rendering and um
[1836.82 --> 1842.96] what else did i use i also uh created i showed people how to create a mongo db session and use that
[1842.96 --> 1850.16] and i also used bind to bind form uh part or post form uh parameters to a struct and go and to
[1850.16 --> 1857.08] use those to um declaratively do that and it all in all it was this full like you know kind of crud
[1857.08 --> 1864.50] like wish list application in like 150 lines of go it was it was surprisingly concise and extremely
[1864.50 --> 1868.60] readable and it's a it's a really cool example to point people to because they're like whoa like
[1868.60 --> 1873.50] you're you're mapping a database and it works concurrently and it does all this cool stuff
[1873.50 --> 1880.80] and it's it's really readable very cool so as i mentioned in the pre-show i had opportunity
[1880.80 --> 1888.36] um kind of right when martini first came out to use it at a local hackathon we have a an event here
[1888.36 --> 1894.38] i'm in i'm from omaha nebraska we have an event called uh hack omaha and our team got to got to
[1894.38 --> 1900.32] kind of expose some civic data via json api and we we chose martini and had a lot of fun using it
[1900.32 --> 1906.12] one of the pain points perhaps the only pain point i can remember at the time was uh there's no there
[1906.12 --> 1910.80] was no live reload which you just kind of come to you get spoiled and you're like man i want my
[1910.80 --> 1916.42] i want to make my change and not have to restart my my little app server is that still the case with
[1916.42 --> 1922.30] martini or are there options to to get live reload or was it already out there and i had i just didn't
[1922.30 --> 1929.42] find it yeah so there are options out there um there are two one of which is written by uh by me
[1929.42 --> 1935.28] um and the other one is written by i'm gonna totally butcher his name andreas france and he
[1935.28 --> 1941.46] is um he's an italian uh goling community member and he has a he actually has a web framework called
[1941.46 --> 1947.02] traffic that's actually quite good um he wrote a project called fresh that is still generic to a
[1947.02 --> 1952.62] lot of web applications and that um that's command line app that simply does live reload
[1952.62 --> 1957.88] and that's very good i've looked at the source he's he's a very good programmer and i really like his
[1957.88 --> 1965.48] stuff um the other application is called gin uh which is you can go find it at github.com slash
[1965.48 --> 1970.74] code gangsta slash gin and it's not fully documented i still have to put together readme and we're still
[1970.74 --> 1976.00] kind of in the growing pains phases of it because it's still fairly new but i use it every day for
[1976.00 --> 1982.32] martini and it does a couple of really cool things it sets up a proxy server to actually serve the
[1982.32 --> 1986.18] requests so we can do cool things like if there are compile errors we can show them to you in the
[1986.18 --> 1993.62] browser um and we can also um compile instead of instead of rerunning the app every time after a
[1993.62 --> 2000.60] compile we actually only rerun the app after you've compiled recompiled and when a request comes in so
[2000.60 --> 2007.40] it's very much like how the play framework does uh their live reload um and it also adheres to the
[2007.40 --> 2012.00] silence is golden principle when it comes to compiles so you can keep saving your files anytime
[2012.00 --> 2017.46] you want and it won't actually like output anything until you have a compile error and then it will let
[2017.46 --> 2021.90] you know that the compile has been successful so it's a really cool tool it doesn't bother you too much
[2021.90 --> 2027.16] it's so transparent um all you don't even need to pass it any configuration it works with martini out of
[2027.16 --> 2034.36] the box you just hit gin and it just works nice yeah looking at that repo now and uh the readme says
[2034.36 --> 2042.50] gin the web development server for go and that's all that is it so yeah definitely fresh it'd be nice to
[2042.50 --> 2049.62] get uh when we can get a little bit more up there so i can at least try this somehow pretty cool yep
[2049.62 --> 2055.12] you're putting a fire under my butt now so by the time this gets posted you'll see a readme it'll be
[2055.12 --> 2064.26] like all fleshed out i'll be like ah nice yeah that's a light readme yeah shame shame so how how
[2064.26 --> 2072.12] have you handled the uh or dealt with or um enjoyed the community contributions um seem like you have a
[2072.12 --> 2077.60] very active mailing list you have very active repositories um has it been an adjustment period
[2077.60 --> 2084.00] has it been pretty easy and what are your philosophies around community um it's it it was really really
[2084.00 --> 2091.34] busy at first um i mean it as far as like github stargazers go it really shot up in popularity and
[2091.34 --> 2097.64] there's a time where i was receiving a lot of issue requests a lot of pull requests and um the last thing
[2097.64 --> 2102.76] i wanted to do was just like be lazy about and be like i'll just merge this i'll just merge this
[2102.76 --> 2109.60] uh because part of martini is about writing clean code and um i really pride myself on that there's many
[2109.60 --> 2114.90] i got a lot of feedback from people and there's just uh an immediate surprise that like you know
[2114.90 --> 2120.88] martini it's probably not the case anymore but when within the first couple weeks of release it was
[2120.88 --> 2126.30] under a thousand lines of code and it did so much and it had the possibility to do so much um through
[2126.30 --> 2132.28] through extending it and so i wanted to keep the code clean i wanted to keep the code concise and i was
[2132.28 --> 2138.96] receiving a lot of pull requests so um it was good i mean you don't want to turn people down when
[2138.96 --> 2142.72] they're when they're writing code and they're passionate about a project and they want to
[2142.72 --> 2151.74] give the code to the project um so my philosophy behind pull requests is you don't have to accept every
[2151.74 --> 2158.54] pull request it's okay people will understand but you've got to communicate it i mean you have to
[2158.54 --> 2166.16] you have to rather than just saying no i'm not going to merge this in it's better to take that
[2166.16 --> 2169.36] passion that they put together into that code because everybody kind of puts their heart into
[2169.36 --> 2174.28] code i i believe you really you know you have to do something if you're contributing to open source
[2174.28 --> 2179.82] you're definitely you're definitely passionate about it in a way um i i want to steer that passion
[2179.82 --> 2185.70] into something that in some place where it'd be more useful so if martini is not the best fit for this
[2185.70 --> 2190.84] piece of code or this um api that somebody wrote i want to be like you know what this would be
[2190.84 --> 2194.90] awesome as a third-party library and you know i'd be happy to link it in the martini read me if it's
[2194.90 --> 2201.54] great um and so that's kind of been my philosophy with with martini specifically because it needs to be
[2201.54 --> 2208.92] such a clean lean code base um martini contrib i'm a little looser on uh accepting code especially from
[2208.92 --> 2214.80] just philosophical reasons like somebody puts up a package that i wouldn't necessarily use but it's
[2214.80 --> 2220.64] very well structured code and um i will definitely accept it in because it seems useful for other
[2220.64 --> 2228.16] people and um that's just kind of in the case i'm a little looser i also give martini contrib uh
[2228.16 --> 2233.94] package owners i do give them ownership of the package by adding them as a collaborator on the repo so
[2233.94 --> 2240.20] i'm not the only one directly contributing to martini contrib like once somebody puts together a
[2240.20 --> 2246.14] package let's say binding um i gave those two guys collaborator privileges so they can update that
[2246.14 --> 2251.50] package without having to put up a pull request all the time that's why you actually have that in
[2251.50 --> 2256.40] your readme too where you say if you're if you contribute a package yourself you can so well so
[2256.40 --> 2261.32] you can so you can fix it you say i will automatically add this contributor if you contribute a package