text
stringlengths
0
1.62k
[4476.26 --> 4483.18] on the one thing and so you know there's an rfc process in gokit where you know we take we take
[4483.18 --> 4491.02] um comments from everyone and um trying to arrive at some kind of consensus and so i'm really excited
[4491.02 --> 4495.54] um for how this is going to turn out i think i think it's really promising um pete is a really
[4495.54 --> 4502.30] sharp guy i really appreciate his his sort of thoughtfulness and also his taste i think his his taste
[4502.30 --> 4509.34] aligns very much with the the taste of the go project and and sort of what that's all about so i feel like
[4509.34 --> 4515.84] that element of go's community is sort of in good hands with him and that project and so yeah i've
[4515.84 --> 4525.14] been i've been trying to to contribute i wrote a a api stability policy which is sort of centered around
[4525.14 --> 4530.00] sort of versioning package management side of things but um i i think you i think you should
[4530.00 --> 4533.78] definitely get peter on the show and talk to him because it's always interesting to listen to
[4533.78 --> 4541.62] we definitely do i know we cover that in uh in our weekly email i'm not sure which one but we
[4541.62 --> 4546.90] share so much stuff in changelog weekly that it's just hard to even remember what we shared when but
[4546.90 --> 4551.54] i know we covered gokit because i was pretty impressed with that and especially knowing knowing
[4551.54 --> 4555.52] that i wanted to have this conversation with you and sort of actually that same question which is you
[4555.52 --> 4560.58] know what can programs anticipate for and he coined it pretty well which is the modern enterprise but
[4560.58 --> 4567.20] the workplace you know so if you're anticipating there's a plant java and those kinds of you know
[4567.20 --> 4574.10] those kinds of projects in enterprise now and go is going to take over that then uh you know gokit
[4574.10 --> 4580.74] makes sense totally all right well definitely would you be interested in coming back on the show to
[4580.74 --> 4585.10] with peter or is that something i should have peter come on his own i guess you should ask him
[4585.10 --> 4592.10] i would be more than happy to do it gotcha um okay so let's let's close out the show then i got a
[4592.10 --> 4597.88] couple questions for you to close out the show some that are uh typical that we like to ask and then uh
[4597.88 --> 4604.58] that's that's how it goes but um one of our favorites and it certainly helps so you can kind of answer
[4604.58 --> 4610.76] this as deep as you'd like to it's kind of one part which is how can someone step into
[4610.76 --> 4617.56] the go project either it's learning go or it's contributing back to go or supporting the efforts
[4617.56 --> 4621.32] that you you're doing and the rest of the team's doing although they may not be google employees
[4621.32 --> 4627.24] but how can one be uh an open source contributor so what's a good way for someone to step into go
[4627.24 --> 4633.80] where are some needs in the go community right now that people can step into i really my general
[4633.80 --> 4639.52] recommendation when i'm asked this question it's just to you know solve problems that matter to you
[4639.52 --> 4646.04] and then share those solutions because programming languages is way at the bottom of the stack
[4646.04 --> 4654.26] and so everything that happens above there in that language helps that language and so you know if you
[4654.26 --> 4661.04] want to sort of get involved with go you just need to start using it and then you know sharing what
[4661.04 --> 4665.52] you've learned or what you've made um and and that just helps everyone
[4665.52 --> 4671.76] all right that's a good that's definitely a good answer and you know i actually i kind of lied it's
[4671.76 --> 4676.80] two more questions but one's really easy for you um this one maybe not so much but definitely a good
[4676.80 --> 4681.96] answer i'm hoping from you which is uh you know what's in your open source radar i can imagine that
[4681.96 --> 4688.04] go is completely your radar but let's you know whichever direction you want to go but if you had a
[4688.04 --> 4692.34] weekend clear and you didn't have anything planned and you were like i'm gonna hack on something
[4692.34 --> 4697.60] what would it be would it be go or would it be around go there's a project that i've been working
[4697.60 --> 4703.18] on for an embarrassingly long time that i've been neglecting lately um which is called sigourney it's a
[4703.18 --> 4712.22] it's an audio synthesizer uh yeah it's it's it's a modular synthesizer so you know you you it's similar
[4712.22 --> 4719.70] to environments like uh max msp or pure data that that people may have used um but basically i have a
[4719.70 --> 4726.96] a actual physical modular synthesizer which is a you you have various modules that like produce
[4726.96 --> 4733.98] waveforms and then filter them and then you know multiply them and so on and you connect the modules
[4733.98 --> 4739.14] with patch cables like actual physical patch cables and then it makes sounds that some people might
[4739.14 --> 4745.50] describe as music and um you know i wanted something similar because i travel a lot i wanted something
[4745.50 --> 4751.42] similar when i'm traveling around and i also wanted to learn about digital signal processing and so
[4751.42 --> 4757.48] i started sort of building this thing from first principles made a lot of progress pretty quickly
[4757.48 --> 4763.26] um but then i've kind of stalled on it so definitely if i had some free time and probably more importantly
[4763.26 --> 4768.50] some like free space in my brain to think um i would i would probably hack on that
[4768.50 --> 4775.26] kind of reminds me a little bit of this thing we covered uh a while ago which has probably changed
[4775.26 --> 4785.12] its name since but um i think i think it pronounced it kievl host k-i-e-v oh yeah k-i-e-v-l-l host
[4785.12 --> 4792.32] if that rings a bell to you yeah it's like a you know digital audio uh workstation kind of thing and
[4792.32 --> 4797.38] it does similar stuff where you connect different things and patch things together it's uh it's pretty cool
[4797.38 --> 4806.02] there's a lot of amazing work being done in like the electronic music making uh world you know
[4806.02 --> 4811.24] there's a it's a huge cottage industry people making both hardware and software so it's really
[4811.24 --> 4817.44] exciting time to be doing that kind of thing and you know uh i might gizump your last question now
[4817.44 --> 4822.96] if i recall correctly like what would i be doing if i wasn't working on go um yeah and the answer is
[4822.96 --> 4830.44] you know i would definitely be working in in audio hardware and software so speaking of audio um you
[4830.44 --> 4835.16] would like to hack on that if you weren't working on go what's one of your favorite podcasts you want
[4835.16 --> 4844.60] to mention here on the show um so yeah my friends mike bernstein or mrb and aaron quint um they do a
[4844.60 --> 4853.04] podcast called beats rye and types and it's about music uh like food and drinks and uh programming
[4853.04 --> 4859.62] languages and programming in general and um yeah they're just a couple of like a couple of guys
[4859.62 --> 4866.14] from you know the east coast of the states i feel a great affinity to them as as people so like
[4866.14 --> 4872.90] listening to them talk about all these topics that i'm very interested in is uh it's always entertaining
[4872.90 --> 4881.68] absolutely i got uh obviously i have a a bug for audio so and you mentioned that you might want
[4881.68 --> 4888.38] to do a podcast so if you're a listener and you were you know stuck on that give him a give andrew
[4888.38 --> 4892.96] props on twitter yeah i don't know if people think that i should do a podcast you should tell me and
[4892.96 --> 4897.46] that'll make it more likely i started doing these screencasts with brad fitzpatrick called
[4897.46 --> 4902.64] hacking with andrew and brad um and that arose because you know i thought
[4902.64 --> 4909.50] you know what i should i should stream some programming sessions and you know people like
[4909.50 --> 4913.10] the response on twitter was overwhelming they were like hey you know yeah i've watched that that'd be
[4913.10 --> 4919.02] great and so you know brad and eventually brad and i got together did one got some great feedback
[4919.02 --> 4924.66] and then we just did a second one not that long ago and we're looking forward to doing another one
[4924.66 --> 4928.74] soon is there a list of those somewhere because i'll link it up on the show notes if there is yeah if
[4928.74 --> 4936.16] you go to youtube.com slash go coding okay um there's a there's a playlist of those two videos
[4936.16 --> 4940.82] which obviously we'll add more to when we make them nice all right we'll link this up in the show
[4940.82 --> 4946.32] notes for sure well i know that i've taken you much longer than i expected as a matter of fact my clock
[4946.32 --> 4954.52] says we're 29 29 minutes over time so thank you for not getting angry and if you're a listener and
[4954.52 --> 4958.84] you're still listening right now thank you for listening all the way to the end it's kind of
[4958.84 --> 4962.60] hard sometimes though when you come into a conversation that's about the state of go and
[4962.60 --> 4967.22] there's a lot to talk about we did have a little bit longer intro than i thought we would have but
[4967.22 --> 4970.92] you know hey that's that's how it works out sometimes i'm just glad you're a good sport with
[4970.92 --> 4974.42] it and you're not upset but you are almost getting kicked out of the room so
[4974.42 --> 4980.98] i'm happy always happy to talk about that all right andrew well let's uh let's say goodbye to
[4980.98 --> 4984.46] everybody and thanks for coming on the show today man i appreciate it yeah thanks for having me
[4984.46 --> 4984.76] bye
[4984.76 --> 4984.98] you
[5010.98 --> 5011.48] you
• Microsoft's TypeScript team is discussed, with Jonathan Turner and Anders Hausberg as guests
• Introduction to Jonathan Turner, program manager, and Anders Hausberg, technical fellow, on the TypeScript team
• History of TypeScript, started in 2011 as a way to address maintenance and scalability issues in large JavaScript codebases
• Description of TypeScript's purpose, to provide a typed superset of JavaScript for growing applications
• Mention of other projects, such as Google's GWT and Microsoft's ScriptSharp, that aimed to address similar issues
• Discussion of the team's decision to productize TypeScript, rather than just a internal tool
• Anders Hausberg's background and work on Delphi and Turbo Pascal, and his correction of his native language's name as "Delphi" rather than "gif"
• The goal was to create a "best of breed" solution that solves problems on the community's terms, not on the creator's terms.
• The team put on a "javascript hat" to determine what a javascript programmer would want, and found that they needed features like classes, modules, interfaces, and static typing.
• The team's design goal was to leverage existing effort in the javascript ecosystem and not create a new language, but a superset that compiles to plain javascript.
• The team aimed to make typescript usable in existing codebases and not require a new coding style.
• Typescript was first used internally by 3 teams, including the team that would eventually become monaco, before it went public in October 2012.
• The team estimates that it took 6-12 months to go from ideation to having a usable prototype.