Hi Rob, Thanks for the link to that talk. I had many of the same early experiences, including using an IBM keypunch and interacting with an IBM 360 (programming in APL) over a modem line.
My first programming job was in 1981 on a VAX11/780 running UNIX/32V (with 7th edition manuals) in the Caltech High Energy Physics Department. ed wasn't just the *standard* text editor, it was the *only* text editor, so I used it a a lot! When I got an account on the Computer Science Department's BSD 4.1 system months later, I learned to use vi immediately, and loved it. It was a huge upgrade from ed. It was really helpful that I had already learned to use ed, since the commands are all available within vi. Since then, I've never found any other editor that felt like an upgrade. Nowadays I use vim because there are a few nice things about it that aren't in vi. At least, vim is ok after you turn off syntax highlighting and all the other newbie crutches. :-P Seriously, how many people can't read or write in English (or their native language) if the verbs, nouns, and prepositions are the same color? I don't get it. About early mice: Later in 1981, I was working for the Computer Science Department on a software development project in semiconductor design. We had custom-made 512x512 pixel color raster graphics terminals with 3-button mice. I think the mice were made by a graduate student or something like that. They used a steel ball bearing rolling against steel rods, so they slipped a lot. So that's another early appearance of mice. On Thursday, November 22, 2018 at 4:32:22 PM UTC-7, Rob 'Commander' Pike wrote: > > And 15 years later, so one hopes for an improvement. > > The thing people ignore, or perhaps just don't know, about ed was that it > was a breath of fresh air compared to all the commercial editors available > at time. People judge it by the standards of today; by the standards of the > time it was created, it was mind-expanding. > > I spoke about this some in my recent personal story of Unix history: > https://www.youtube.com/watch?time_continue=226&v=_2NI6t2r_Hs > > -rob > > > On Fri, Nov 23, 2018 at 7:58 AM Dave MacFarlane <dri...@gmail.com > <javascript:>> wrote: > >> But sam is a pretty solid improvement over ed. >> >> On Tue, Nov 20, 2018 at 6:04 PM Rob Pike <r...@golang.org <javascript:>> >> wrote: >> > >> > Ed is the standard text editor. >> > >> > -rob >> > >> > >> > On Wed, Nov 21, 2018 at 8:15 AM <buc...@gmail.com <javascript:>> wrote: >> >> >> >> >> >> Another vote for VS Code. I'm a hobbyist and have tried lots of >> editors. >> >> >> >> On Tuesday, November 20, 2018 at 1:52:11 PM UTC-7, Pat Farrell wrote: >> >>> >> >>> I know, this is both a FAQ and an unanswerable question. I'm an old >> programmer who has used nearly every editor known to man. I am not a fan of >> whole-universe IDEs, but can use them. I also speak vi/vim pretty fluently. >> >>> >> >>> What editors do folks use for go? I'd like something that can >> complete function names, understand imports, and give some assistance. >> >> >> >> -- >> >> You received this message because you are subscribed to the Google >> Groups "golang-nuts" group. >> >> To unsubscribe from this group and stop receiving emails from it, send >> an email to golang-nuts...@googlegroups.com <javascript:>. >> >> For more options, visit https://groups.google.com/d/optout. >> > >> > -- >> > You received this message because you are subscribed to the Google >> Groups "golang-nuts" group. >> > To unsubscribe from this group and stop receiving emails from it, send >> an email to golang-nuts...@googlegroups.com <javascript:>. >> > For more options, visit https://groups.google.com/d/optout. >> >> >> >> -- >> - Dave >> > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
