I just wanna get my work done.🤓

  1. This is where a good tool is even more important. Code reading is infinitely more pleasant when your editor lets you zip around code easily (or rather, when you know how to use those features of your editor). Then there's planning/notes, Inspection of logs, etc. Not needing to context switch for these things to a different tool is, IMO, a great thing.

  2. I literally told my supervisor this the other day because our project is behind schedule and client was told the shit is done when I've been screaming it's not.

  3. Just use search commanda via the terminal, grep "syntax" -f file if I remember correctly. That works so fast on log files that end up in the millions of rows

  4. Don't forget Everything Search because I can't be bothered to organize my computer. I have no idea where that 25GB log file even is.

  5. I exclusively use notepad++ to do regex searches and find and replace. There's probably a plugin for vs code, but vs code chokes on large files.

  6. I find Notepad++ really bad at handling large files, especially when some syntax highlighting or line wrapping is active. And it becomes impossible if it tries to add folding to large xml files.

  7. One time I was a backend dev and I INSISTED on doing all my Java dev in atom. I really liked how "hackable" it was and I installed a million helpful packages to make it usable. None of these plugins were intellisense so I'd literally just have docs open all the time.

  8. NeoVim, after adding easily installable plugins, can become an IDE (albeit a very lightweight and fast IDE). The issue is learning the impulse control of not messing with configs all day.

  9. I have yet to work on a project that vim didn't do everything I needed it to. Before then I used sublime text, eclipse for java project (that shit sucked), AdaGIDE for ada, etc.

  10. Vim is useful when remoting to servers and needing to edit some files there. Or if you need to edit a script inside a container. But same concept. Anytime you need to edit a file where there is no UI option.

  11. Not saying that this is necessarily the case here, because vim can be pretty useful, but a lot of people in tech have this strange hard-on for tools and utilities just because those tools and utilities are perceived as the "legit" and "hardcore" way of doing things.

  12. Idk if I’m just showing my age here or what, but when I first learned git, GUIs for git were an absolute nightmare to use(complex AND would sometimes fuck up for no reason and be very difficult to debug) and it was much easier and more productive to just learn the handful of commands needed to check out a branch, make a commit, and push to the remote repository.

  13. There definitely is some elitism around tools in tech. Ideas about how it "should" be done and what "real" programmers use. And that's all bullshit of course.

  14. For the most part, I am much quicker at using git on the terminal that I am using a GUI, specially after some fancy scripts or aliases.

  15. I like Emacs but not gonna lie, JetBrains products are just too damn good. For the price of 1 beer per month it makes programming way more pleasant.

  16. Right there is an upfront cost for neovim, but what you get in the end is a very versatile and personalized pseudo-IDE.

  17. What about the days before editors? My first programming on a TRS-80 was right from the command line!

  18. neovim is the best tool I know of for quickly editing stuff, config files, etc since I'll do that while already in a terminal

  19. I used VSCode for a bit until it started to fail with large C++ codebases. Specifically Unreal Engine. Now I use Visual Studio for it in Windows or Eclipse CDT (gross) for linux.

  20. Text editors and ides are like apples and oranges. Of course they are much more similar compared to whales and tables, yet there are differences.

  21. I use vim if I need to ssh into something and make some quick changes or parse logs or whatever. I get the appeal of using vim shortcuts in an IDE in theory, but I’m skeptical about how much it would matter in practice. The vast majority of my time writing code isn’t spent literally writing code, so I can’t see shaving a couple seconds off of my keyboard time over the course of a day really making any difference. If we’re just talking about adding a VS plug-in, then you can argue that there’s no reason not to — and sure, fair enough. For day to day coding work though, I’d never choose vim over an IDE, and I don’t know any senior devs who do.

  22. I'm sure there are a lot of people who are great at vim and it's really fast for them but most people I've encountered who are really pretentious about vim, they press a lot of keys very fast to do very little and convince themselves it's faster because of how many buttons they have to press lol

  23. Meh. Currently learning Rust right now and using Vim for it. It's just lazily simple to have the Rust code open, then either spawn a term in Vim or open a new tab (for notes and compiling).

  24. Just saying, if you haven’t used vim, you don’t know how fucking productive it is. especially if you don’t work in bloated code bases

  25. Vim ia productive once you get used to it. Until then it feels like a Sysphisian task to do anything other than basic editing. It's been my daily driver ten years which is why it's productive for me. If I had been using Visual Studio or some other editor for that long, I'd be just as productive in that. No sense in this "you aren't really productive until you've used ${EDITOR}" mumbogumbo.

  26. Vim + tmux + ssh is all I need. I work remotely from a MacBook Pro but write all my code on my Linux desktop which sits securely at my desk (which I haven’t used in 2+ years).

  27. Productive because you navigate the text slightly faster? idk about you but I spend most of my time thinking about the code, not actually typing.

  28. I’ve worked with a few vim users. They were the least productive members on the team. We forced them onto an IDE, and suddenly they could keep up just fine

  29. nah vim stays forever, nothing beats being able to edit a file with a lightweight easy to use text editor, in a terminal

  30. I hate these god damn bell curve memes. Use the tool that fits the needs of the job. Preferring a particular IDE or language doesn’t make you 3 million IQ hackerman, and acting as if it does is an indication of the opposite

  31. Yeah, makes me think the person who created this meme doesn't know a lot of smart programmers (doesn't mean a smart programmer wouldn't use an IDE, but I've met a lot of them using vim).

  32. If you actually know how to use Vim or Emacs they can absolutely be more productive than VSCode. VScode is easier to use and set up tho.

  33. I'm so institutionalized to nano that I often find myself using nano in the VS Code terminal window, having forgotten that I was already in a text editor ...

  34. I see tons of people complaining about vi/vim/nvim without ever having given it a try. If you try and then decide that you don’t like it, that’s fine. Everyone is different, so let people choose their own editor and stop bashing each other’s setup lol

  35. For the last 4 years all my dev work at my job required connecting to a remote linux server using putty, so vim was my best option. I'm very comfortable with it, and use it for my home development work as well.

  36. I've never had a stable experience with Visual Studio. Probably the worst IDE I've used, although I've only tried to use it for python and C++.

  37. I never used him and I probably won’t ever use it. I did use the com extension for vscode for a few days because people told me "oh wow it’s so good" but after that I uninstalled it and never used it again.

  38. Completely different programs. VSCode is more lightweight, extension-based, and open source. Visual studio is geared towards a few languages while vscode is generic.

  39. Visual Studio is an ancestor of the original VisualC++ (and PWB before that) from the '90s. It's written mostly in C++ with some .NET code in more recent versions.

  40. if you just hit `Ctrl+Enter` in vscode's git commit message then it'll open a new document `COMMIT_EDITMSG` where you can type your msg.

  41. I'd consider using something other than emacs if it wasn't for all the emacs features I am unwilling to give up. Org is the big one though. I can't go back and you can't make me.

  42. I honestly can’t program unless it’s in Visual Studio; the layout and keyboard commands built in, just make it so easy; along with so much programmatically correcting ahead of time and not at build.

  43. I went to Emacs for a few weeks here between 4th and 5th semester over the summer and recently i just noticed that I'm spending a lot more time in library documentation than I did before because I don't know how to set proper autocompletion up

  44. VScode has boosted my productivity more than any other tool. I al ways get excited when new releases/features drop.

  45. For a long time i used to use IDE but with time i realised on Competitive Programming is the thing anyone gives shit About, so i deleted the ide, now i always search an online IDE runs my code submit it & pray it get accepted

  46. What about simple editors like gedit? Should be very left for the absolute beginners, and very right for the absolute experts, right?

  47. I don't care what I'm programming in as long as it has syntax highlighting, "go to definition", and vim keybindings.

Leave a Reply

Your email address will not be published. Required fields are marked *

Author: admin