At the very least, I can appreciate that vim is much more cross-platform, and stable across time, than any other text editor I’ve ever put up with. I’m trying to convince myself that the time investment is worth it. It’s not a gimmicky gadget, it’s a powerful tool: a programmer’s text editor. I can appreciate that a lot of thought was put into its design. I don’t know how to use vim, but I think I’d like to learn. I’m 31, and I can’t help but want to take a step back. It’s alright, but like gedit, it has its annoying quirks. Not knowing where to run, I started using the GitHub atom editor. The MacOS port of gedit is like one of those freak creatures in a horror movie that begs you to pkill -9 it. Pressure to get things done quickly Given tight assignment deadlines, I didn’t really feel like spending 10 or 20 hours familiarizing myself with vi or emacs, or dealing with people who would tell me to go RTFM (Read the Fucking Manual). I went with gedit because it was intuitive and comfortable, as shitty as it was.Īt my current workplace, we run MacOS, and well, while there is a port of gedit (not even kidding), it’s a fairly miserable experience. Needless to say, there was a lot of pressure. We worked our asses off. Some semesters, I remember having as much as 40 hours of homework per week. I stuck with it because of habit.ĭuring my undergrad, we were given assignments with tight deadlines. I started using gedit because it was the default on the Linux distro my university ran at the time. The craftsmanship of programming, so to speak. I learned about programming languages, operating systems, compiler design, and all those wonderful things, but all this time, I was never given the opportunity to sit down and think about the tools I was using. I think the problem is, in university, there was never any class that was really about teaching us how to use properly and efficiently use tools. I had the ramen right here at home, no cash on hand, and well, I was hungry. If you were to think of emacs as a sushi meal prepared by an experienced chef, then you could think of gedit as a microwaved bowl of ramen with a half cup of sriracha sauce dumped on it. It’s a fairly shitty text editor. It will freeze up if you try to open a text file more than a few hundred kilobytes, or with lines that are too long for it to properly digest. It’s the GNOME text editor. Its noteworthy features are syntax highlighting, and the ability to have multiple tabs open at once. Most of it on Linux, and most of it using a text editor called gedit. It’s probably because as a teenager, I grew up with Windows 98, and on that platform, back then, command-line tools were very much second-class citizens. In university, I was introduced to Linux and somehow, over the years, I became hooked. I spent a total of 11 years in university, and over that course, I probably wrote over 400K lines of code. I’ve been programming since I was 16, but all this time, I’ve never learned how to use a “proper” text editor.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |