my editor SAN DIEGO, CA JULY 25 2019 REBECCA STAMBLER Go, Go, please Go, please stop breaking my editor! Rebecca Stambler Software Engineer, Google @stamblerre Why doesn’t my editor have saying? Quotes from Go survey, 2018 Hard to install and configure Inadequate documentation My editor isn’t working! 1. There are many different editors and many different features What are users saying? Pretty slow in large projects Performance is very poor Quotes from Go survey, 2018 My editor isn’t working! 1. There are many different editors and many different features 2. Many features

letter, during compilation. These errors are reported in the terminal window or directly in the editor or IDE. When no errors are found or after all errors have been fixed, the compiler generates highly while i < 100: inc(i, 1) inc(sum, i) echo sum We write Nim programs as plain text files using an editor tool, and you will learn how to create them soon. We call these text files the source code of the using an editor. Don’t try to load the executable files generated by the Nim compiler into a text editor, as the content is not plain text, but numeric machine code that may confuse the editor. On the

letter, during compilation. These errors are reported in the terminal window or directly in the editor or IDE. When no errors are found or after all errors have been fixed, the compiler generates highly while i < 100: inc(i, 1) inc(sum, i) echo sum We write Nim programs as plain text files using an editor tool, and you will learn how to create them soon. We call these text files the source code of the using an editor. Don’t try to load the executable files generated by the Nim compiler into a text editor, as the content is not plain text, but numeric machine code that may confuse the editor. On the

letter, during compilation. These errors are reported in the terminal window or directly in the editor or IDE. When no errors are found or after all errors have been fixed, the com­ piler generates highly while i < 100: inc(i, 1) inc(sum, i) echo sum We write Nim programs as plain text files using an editor tool, and you will learn how to create them soon. We call these text files the source code of the using an editor. Don’t try to load the executable files generated by the Nim compiler into a text editor, as the content is not plain text, but numeric machine code that may confuse the editor. On the

letter, during compilation. These errors are reported in the terminal window or directly in the editor or IDE. When no errors are found or after all errors have been fixed, the compiler gener­ ates highly while i < 100: inc(i, 1) inc(sum, i) echo sum We write Nim programs as plain text files using an editor tool, and you will learn how to create them soon. We call these text files the source code of the using an editor. Don’t try to load the executable files generated by the Nim compiler into a text edi­ tor, as the content is not plain text, but numeric machine code that may confuse the editor. On the

letter, during compilation. These errors are reported in the terminal window or directly in the editor or IDE. When no errors are found or after all errors have been fixed, the com­ piler generates highly while i < 100: inc(i, 1) inc(sum, i) echo sum We write Nim programs as plain text files using an editor tool, and you will learn how to create them soon. We call these text files the source code of the using an editor. Don’t try to load the executable files generated by the Nim compiler into a text editor, as the content is not plain text, but numeric machine code that may confuse the editor. On the

letter, during compilation. These errors are reported in the terminal window or directly in the editor or IDE. When no errors are found or after all errors have been fixed, the compiler gener­ ates highly while i < 100: inc(i, 1) inc(sum, i) echo sum We write Nim programs as plain text files using an editor tool, and you will learn how to create them soon. We call these text files the source code of the using an editor. Don’t try to load the executable files generated by the Nim compiler into a text edi­ tor, as the content is not plain text, but numeric machine code that may confuse the editor. On the

letter, during compilation. These errors are reported in the terminal window or directly in the editor or IDE. When no errors are found or after all errors have been fixed, the compiler gener­ ates highly while i < 100: inc(i, 1) inc(sum, i) echo sum We write Nim programs as plain text files using an editor tool, and you will learn how to create them soon. We call these text files the source code of the using an editor. Don’t try to load the executable files generated by the Nim compiler into a text edi­ tor, as the content is not plain text, but numeric machine code that may confuse the editor. On the

letter, during compilation. These errors are reported in the terminal window or directly in the editor or IDE. When no errors are found or after all errors have been fixed, the compiler gener­ ates highly while i < 100: inc(i, 1) inc(sum, i) echo sum We write Nim programs as plain text files using an editor tool, and you will learn how to create them soon. We call these text files the source code of the using an editor. Don’t try to load the executable files generated by the Nim compiler into a text edi­ tor, as the content is not plain text, but numeric machine code that may confuse the editor. On the

letter, during compilation. These errors are reported in the terminal window or directly in the editor or IDE. When no errors are found or after all errors have been fixed, the compiler gener­ ates highly while i < 100: inc(i, 1) inc(sum, i) echo sum We write Nim programs as plain text files using an editor tool, and you will learn how to create them soon. We call these text files the source code of the using an editor. Don’t try to load the executable files generated by the Nim compiler into a text edi­ tor, as the content is not plain text, but numeric machine code that may confuse the editor. On the