text
stringlengths
0
2.02k
[2450.68 --> 2454.88] a real programmer or whatever don't worry about any of that but give it a try and i can name three
[2454.88 --> 2460.58] different reasons to do it and i think all of them are sufficient on their own so first rsi it'll
[2460.58 --> 2464.72] prevent injury it's a really important thing as a programmer if you want to make a career out of
[2464.72 --> 2470.50] this the second is speed vim is unambiguously faster than other editors it's not even remotely
[2470.50 --> 2475.42] controversial to say that but the question of course is going to be whether you value speed over
[2475.42 --> 2479.46] what you may be giving up things like deep language support from something like visual studio
[2479.46 --> 2484.50] or or a jetbrains ide or whatever so you're making a trade-off there but for me speed is even
[2484.50 --> 2488.58] sufficient on its own because every time you have to stop and like slowly make some edits is a chance
[2488.58 --> 2492.26] for you to forget what you were doing to lose the state in your brain and maybe you're like eight
[2492.26 --> 2496.70] levels deep in your stack and you're going to start losing those levels right if you have to get
[2496.70 --> 2503.48] distracted it's also just fun honestly to be fast and then the third reason is that vim unlike most
[2503.48 --> 2507.88] other editors is not going to go away the vim keystrokes in particular so many people have them
[2507.88 --> 2512.72] so deep in their brains that 30 years from now you will absolutely be able to get an editor that has
[2512.72 --> 2516.44] those keystrokes i don't know whether it'll be vim i don't know whether bram molinar will be
[2516.44 --> 2521.34] maintaining it but you will be able to use those keystrokes so any of those for me is sufficient
[2521.34 --> 2525.74] especially for the last one if you think about the timeline just for me right 15 years at the
[2525.74 --> 2530.14] beginning of that time textmate was just becoming popular then it was sublime text was cool
[2530.14 --> 2535.56] then atom was cool then vs code was cool a lot of people switched between two of those three of
[2535.56 --> 2539.38] those maybe all four of those and that whole time i was just getting better and better and better at
[2539.38 --> 2544.12] vim and you multiply that out by the length of a career use vim for 40 years you're going to be
[2544.12 --> 2548.10] so good at it by the end and it's still going to be totally relevant i think
[2548.10 --> 2558.06] as a companion to this episode we have three youtube videos of our guests viming with me to
[2558.06 --> 2563.66] give you a taste of what their vim life looks like links to those videos are in your show notes if
[2563.66 --> 2569.42] you've never given vim a serious try hopefully this episode of the changelog convinced you it's worth
[2569.42 --> 2575.96] your while how to go about learning vim is another conversation in and of itself drew and su's both
[2575.96 --> 2582.28] recommended vim adventures which has been described as zelda meets text editing i know i know it had
[2582.28 --> 2587.72] you at zelda unfortunately julia doesn't have any vim related zines for you but gary does plan to make
[2587.72 --> 2593.48] a vim course real soon now we also have a channel in our slack dedicated to vim i encourage you to join
[2593.48 --> 2599.12] the community which is totally free at changelog.com slash community and hop in that channel there's lots
[2599.12 --> 2604.16] of friendly and vim passionate folks in there the channel is called vim party so you know it's good
[2604.16 --> 2609.10] we put a lot of love into this episode so if you enjoyed it and want to hear more like this
[2609.10 --> 2613.76] please let us know post it on twitter submit it to hacker news and reddit tell your programming
[2613.76 --> 2618.34] pair it's a must listen write a reaction blog whatever is your pleasure we love hearing from
[2618.34 --> 2623.64] you special thanks to source graph once again for helping us ship this interruption free to break
[2623.64 --> 2628.58] master cylinder for all of the beats to adam stokowiak for his storytelling and production skills
[2628.58 --> 2634.20] and to our very special guests julia evans drew neil suce hinton and gary bernhardt y'all are awesome
[2634.20 --> 2639.64] if this is your first time listening don't forget to subscribe at changelog.com and if you love our
[2639.64 --> 2645.12] work support us directly by joining changelog plus plus that'll get you closer to the metal and make
[2645.12 --> 2651.84] the ads disappear check it out at changelog.com slash plus plus i'm jared santo and we'll talk to you next time
[2651.84 --> 2653.84] more
[2681.84 --> 2683.92] Altering
[2683.92 --> 2687.00] 解
[2687.00 --> 2692.92] 解
[2692.92 --> 2694.04] 解
[2694.04 --> 2694.60] 解
[2694.60 --> 2694.88] 解
[2694.88 --> 2695.00] 解
[2695.00 --> 2695.66] 解
[2695.66 --> 2696.16] 解
[2696.16 --> 2696.42] 解
[2696.42 --> 2696.56] 解
[2696.56 --> 2697.62] 解
[2697.62 --> 2698.66] 解
[2698.66 --> 2698.88] 解
[2698.88 --> 2699.54] 解
[2699.54 --> 2700.66] 解
[2700.66 --> 2700.72] 解
[2700.72 --> 2701.68] 解
[2701.68 --> 2702.08] 解
[2702.08 --> 2702.58] 解
[2702.58 --> 2702.72] 解
[2702.72 --> 2703.64] 解
[2703.64 --> 2704.88] 解
[2704.88 --> 2705.78] 解
[2705.78 --> 2706.06] 解
[2706.06 --> 2708.24] 解
[2708.24 --> 2708.62] 解
[2708.62 --> 2710.36] 解
[2710.36 --> 2711.48] 解
[2711.48 --> 2711.50] 解
• Mat Ryer joins the Go Time podcast as a world-renowned Captain Jack Sparrow impersonator
• Discussion of Mat's involvement with Go Time and how it's not just about the Go programming language
• Mat shares his history with Go, starting with using it for App Engine before it was released
• Discussion of the Go community's welcoming nature and diversity efforts
• Go Time podcast's origins and its relationship with the Go community
• The origins of the Go Time podcast and its welcoming, fun community
• The importance of Go Time to the Go community and its role in delivering value to listeners
• The creation of the Unpopular Opinion segment and its impact on the show
• Jerod Santo's unpopular opinion that JS Party is a better podcast than Go Time
• The lighthearted, humorous nature of the segment and the podcast
• The discussion of tech wars and the importance of collaboration and using different languages and technologies together
• Mat Ryer's experience producing JS Party and Go Time podcasts
• The idea of a "gang fight" between the two podcasts, but it's not a serious rivalry
• Mat Ryer's involvement with Bitbar, a menu bar app he created in 2014 to track Bitcoin prices
• The app's development and features, including its hackability and plugin capabilities
• Bitbar's popularity after being featured on Hacker News in 2016
• Mat Ryer's current use of Bitbar and its ongoing development
• The Hacker News post about a plugin ecosystem for a specific tool led to a surge in contributors and a community of users.
• The ease of contributing to the project, including the ability to see immediate results, was a key factor in its success.
• The original creator, Mat Ryer, attributes the project's success to a "happy accident" in its design, which allowed for a nice abstraction layer.
• The project's popularity led to a rewrite in Go, and later, a further rewrite in a new project called Wails.
• The Wails project allows for building desktop applications using JavaScript as the frontend and Go as the backend, with a native-like appearance.
• Mat Ryer and the Wails creator, Lee Anthony, discussed the possibility of creating a desktop app for the original project, but it was eventually discontinued due to lack of contributors and maintenance issues.
• Discussing the benefits of rewriting code, with a focus on the xbar project
• The importance of backwards compatibility in code rewrites
• The concept of a "prototype" or "first version" of code, and the idea of iterating and improving upon it
• The parallel between writing code and writing words, and the idea that rewrites are a natural part of the creative process
• The benefits of a rewrite in terms of learning and improving upon initial ideas
• The future of the xbar project, including its potential to become cross-platform and the need to adapt plugins to new platforms
• The design of the xbar API and the use of metadata to handle platform-specific plugins.