The Morning Brew #2299
Posted by Chris Alcock on Tuesday 14th March 2017 at 09:15 am | Tagged as: .NET, Development, Morning Brew
Information
- Visual Studio 2017 Poster – Tim Sneath
- Notes from the ASP.NET Community Standup – March 9, 2017 – Maria Naggaga
- ASP.NET Core: Environment based start-up classes – Gunnar Peipman
- Debug ASP.NET Core via lldb on Ubuntu – Wu Shuai
- Debug ASP.Net Full Framework on Server Core Container on Windows 10 – Garry Pilkington
- How to Compress and Resize/Scale Images in ASP.NET Core – Talking Dotnet
- Latency monitoring with Seq 4 preview – Nicholas Blumhardt
- Fix Visual Studio 2015 with Orleans Tools for Visual Studio 1.4.0 installed – AttilaH
- Getting Started With ASP.NET Core and Entity Framework Core – Pankaj Kumar Choudhar
- Visual Studio 2017 offline installer – Stefano Mapelli
- Threading – Under the Hood – Marco-Hans Van Der Willik
- TypeScript 2.2: Null-Checking for Expression Operands – Marius Schulz
- Chrome Deprecates Subject CN Matching – Eric Lawrence
- Communicating Sequential Processes: an alternative to async generators – Dr. Axel Rauschmayer
- Storyteller 4.1 and the art of OSS Releases – Jeremy D Miller
- Excessive explanation, part twenty-one – Eric Lippert
- How not to quit your career when Git opens a vi editor – 072 – Sara Ford
What I do not understand is how all or so many VI commands are not aligned with Bash. E.g. to go to the beginning of a line in Bash is Ctrl-A, but in VI you need to get out to command prompt and type Ctrl-0. Why?
@Arthur I believe vi was created in ’76 or ’75 and first version of Bourne shell (sh) was published in ’77. I guess authors were not aware of each other work, I am not even sure if they have any kind of network access 🙂
BTW Both vim and bash are examples of timeless tools, vim is older than any operating system I know, not to mention any programming language (maybe FORTRAN and COBOL are older, but I never wrote anything in them), and I am sure vim will be used after 5, 10, 15 years from now.