Text editors - which ones do we enjoy, which ones have we used, and what do we actually want and need in them?Andreas has read about vim, sed and awk. Lars is quite comfortable in vim, but finds Visual studio code more than acceptable enough. Andreas is excited to show Lars how to use Vim properly. Lars considers advanced setups something of a hellscape.Lars has held a lecture about functional programming and wishes to provide a path for new .Net developers (dotnet dots?) to become free software zealots.They both share their history of editors.There are dreams of ergonomic editing - of code as well as text in general - on mobile devices.Any other editors we should be trying? No, but you could hack together collaborative vim editing. LinksHumble bundleLearning the Vi and Vim Editors - bookVimThe Anarchist CookbookThunderdomeMonadex - line editor which inspired viedsed & awk - bookAWKsedSublime textZedNeovimTmuxI3GNOMEPop!_OSKDETreesitterElixirLSFZF - fuzzy finder for the command lineRipgrepFunctional programmingMonadsFakerootNotepad.exeBorland DelphiNotepad++EclipseIntellijAndroid studioXcodeWrite/WordpadNanoPicoGeditKateNetbeansAtomScratchGNU ScreenLive Share for Visual Studio CodeQuotesLearning violent vimLike Thunderdome, but nobody leaves, everI could do that with monads insteadC's strange cousinThere's a new sed on the blockThe power of just good enoughTwo terminals beside each otherIt's all a mess in hereMy sword and lots of configuration filesThe dotnet dotsQuitters don't use VimReal code is done on the serverNotepad the way I want it to workA load-bearing noteExciting and fun, and incredibly unsafe

Ver todos los episodios