I started using Neovim a few years ago and immediately grew to be over 6'7" and instantly sold my company for a billion dollars. Thank you TJ, very cool.
folke (the creator of LazyVim, lazy.nvim, tokyonight.nvim, flash.nvim, etc.) I think has acquired the role that tpope had for regular vim. The man is creating so many extensions and plugins of such high caliber. And maintaining ALL OF THEM, the guy is insane.
20:58 Nails it for me. It's basically like if 85% of the world use Phillips (plus-shape) head screws and 2% of the world use Robertson (square-shape) screws. People carrying Phillips screwdrivers want to screw every hole, and then see a square and get mad. People carrying Robertson screwdrivers never had the need to screw every single hole in existence, if they did they'd never buy a Robertson. So when they see a plus they aren't bothered, and they are content with screwing just their own holes. 24:55 VSCode settings configuration generally does not involve heavy json digging. Just press Ctrl+{comma} and text search for the setting you want to change and it is presented to you with a clean GUI.
but you have to know what you are searching for. its a heavy search first design and if you want anything programmatic, it becomes impossible (for some things)
@@ThePrimeTimeagen Nothing's totally foolproof if the user is unfamiliar with the system, but compared to NVim (or even JetBrains offerings) it's straightforward, comparatively reliable, and flexible. And when there's a desire for stitching together chunks of someone else's config the JSON is there for you. Heck, if you commit the workspace .vscode directory into source control, the editor will do the stitching for you. Commit a .devcontainer config and VSCode will stitch in a docker container too.
Nah VSCode is extremely time-consuming when you need to change some really specific setting in the editor because 9/10 times it's not even documented, if you haven't encountered this, you just don't configure settings outside what VSC is prepared for so it works for you
"There is an idea that you have to have that NEWEST thing" Realized that a couple of months ago. Started asking myself "What the hell I switch to %that new thing% for?" and most of the time sticked to things that are just GOOD ENOUGH - saved huge amount of time.
The thing about VSCode is it works with a single click until it doesn't at which point you'll be spending 10 times the amount of time fixing the issue because all our traffic goes through a proxy. So you're just digging through json files trying to find the correct option, except it's not documented basically anywhere.
@@gagagero The obvious thing....??? The only obvious thing about programming is that there is no "one way" for every problem or use case. But I agree, we should all use the one editor that's worked so well it stands the test of time.... The obvious one size fits all "One Way" Notepad :D
As neovim newbie (about a week) I am genuinely impressed how solid the documentation and guides are for it, at this point I have it looking nice I have lsp stuff autocomplete etc. a debug setup updated manuals for C++ and a bunch of other things all integrated in with very little conflict and I'm pretty much happy and setup for everything I would want.
@@stefanplusplus917 Not saying it was easy it was just a lot easier than I expected haha and to update that I started to have some trouble when I tried to integrate gdb to debug cpp it works but not smoothly at all
I think the people complaining about the time to setup Neovim do have a point. Vim/Neovim get a lot of flack for vim motions but these should be treated as a separate thing at this point, pretty sure most IDEs have plugins for vim motions at this point so you don't need to use Neovim for vim motions. No, Neovim is for people who legitimately like to customize their environment. For us, that "time it takes to setup" is the whole point. It changes the way you think about UIs, actually. You take that to the next level and you get ricing Arch Linux enthusiasts.
This is mostly true, but pretty much all of those editor plugins are missing some of vim motions. And the motions themselves tend to be harder to customize than in nvim.
Blessed be the day upon thou fellow traveler, may thy path be full of riches and thy spirit led by light. Wouldst thou like to talk about our savior, Richard Stallman? He hath a message of joy to be delivered unto the world.
Here's the thing: once you've configured nvim to work with your specific workflow, there's hardly ever anything to setup. Your config is a git pull away. One can get lost in customizing vs code to their hearts content as well, that isn't a vim-specific thing.
VSCode plugins are always breaking, there's a 10% probability that pylint will work correctly on a given machine. The broke attaching to pods in kubernetes with 1.80.
@pnk4996I had so many problems with pylint no longer working after an update and spend hours trying to fix it just to end up at open github issues with no answer.
13:00 no way, the neovim community is SO HELPFUl. no RTFM attitude, it's supremely wholesome. in reddit i have NEVER seen any hostile/abrasive behavior. there is a great community of supporting new plugins and knowledge sharing. the neovim community is so wholesome
I think that by "using vim for small changes", people mean stuff like editing nginx configs or htaccess files, browsing through logs, that kind of stuff. Small server-side jobs that are a lot faster in vim than in nano, but still take less than 1% of their overall coding time.
Now in defence for some of the people that struggle with the Nvim community. Because i do think that the culture is that of someone that is expected to know a certain amount, forgetting that a new person to Neovim in this day and age does not come from Vim. They come from an IDE where you do not have to deal with plugins, a configuration language (however easy it might be) and just how these things are connected. I felt like it was a heavy hurdle to get across to customize anything outside the complete standard of NvChad which is what i ended up with. If not for Vim motions (before realizing i could just set this up in Vscode) i'd prolly just bail that ship in the first place. It's not easy if you're not used to it.
I honestly cannot fathom how neovim could be hard at such stage, maybe because I started programming outside of an IDE, I used notepad++ and opened windows terminal to compile my code with mingw. Neovim is 1000x simpler than Emacs, honestly if you just follow the ChrisAtMachine series you'll basically end up with a good setup
I recently started I did find a lot of cases of assumed knowledge but there is so much documentation and so many guides that I just had to go read for a while and I was able to get everything working.
Python folks can't argue about the package manager complaint. Making, distributing, maintaining, and even just installing deps for a script or app is kinda a nightmare in python, ngl.
How so? It's literally just pip install -r and passing in a literal txt file? There isn't a lot of guess-work involved unless your requirements file grows to something over 10 or 15 direct dependencies (not counting dependencies of your dependencies). That + virtualenv takes care of MOST of the problems you could POTENTIALLY have in Python. PIP is such a god-send compared to package managers in most other languages.
@@malaista pip has struggled with nested dependency resolution in the past; idk about now. Plus there is pipenv, poetry, conda. Then virtualenv isn't alone either, with pyenv and pyvenv. Then distutils used to not use TLS, so you had to use twine, but maybe distutils uses TLS now, so unclear. That's just it, nothing is very clear with python build and distribution. Some people like that. Some don't. Should I build a wheel? Or maybe pants and pex? Hmm. Give me cargo, or give me cake.
You're over exaggerating, for large projects it's possible and even likely without the right tools but not for a script, for that and even simple projects venv alone get you covered, add piptools for more goodness, pyenv optionally if you want a specific python version and your distro doesn't easily give that
@@theherk PIP has gotten better at dependency resolution but it's obviously not perfect like most package managers with big dependency sets. PIP and virtualenv are packaged with Python since Python 3, no reason not to use them since they use TLS natively. Conda is the choice thwt only made sense whrn Python2 was the standard. Always build wheels. (Organized and Standardized by a PEP). ALL else is fluff and shouldn't be used in general.
my story with vim was slow, mainly i started using it and stuck with it for a few years. first it was low stakes stuff at first, home sysadmin type stuff like editing conf files, then I used it as a personal typewriter (editing copy made me fall in love with modal text editing). with little bit of time you pick up more and more things, apply it to more diverse tasks, and now it fits like a glove. i totally get it being hard at first but very worth to stick with it
One of the things I've noticed change in my behavior when I gave neovim a try for nearly 7 months was that I was adapting my behavior and my interests around what I can do well in neovim while thinking that I'm adapting neovim to my interests. I spent so damn much time trying to even get comfortable with somewhat above basics and once I had to stop using it for a month, almost everything felt like out of touch with my "nervous system" if I can put it this way.
It would be awesome call folke to a chat, the audience gonna sky rocketed. How is it possible for a human to create so many vim plugins, plugin manager, vim distro, the best tokyonight I ever seen, cool stuffs, maintain them, and have a life/run a enterprise/be surfist idk? He's like a Terry A. Davis vim version, but with social life.
Learned VIM early on. Switched to VSCode for a windows project, using VIM extensions. One day I went to write an edit macro on a 20k line legacy file... it took 10 minutes to execute. What? I thought this was instant in VIM. So I got MINGW installed and set up, tested the same macro in vim... Instant. never looked back. (Although I occasionally use emacs + evil mode too!)
I recently started my Neovim journey (I tried the vscode vim extension thing it didn't click, so I just jumped right in to vim.) While I don't know if all the setup will be worth it productivity wise I will say that the learning experience is absolutely necessary. A while ago I got stuck after a vscode extension broke. I spent hours trying to figure out what the problem was, only to find out that it was a glitch, I then spent hours trying to find a work around before giving up and putting my project on hold. The problem is that I didn't know what the plugin was doing under the hood, and I didn't know how it was doing it. With Neovim it is not only necessary, but also easier to learn how your tools work. Even if I have to go crawling back to vscode one day (please no) I am fairly certain that what I learned setting up a Neovim configuration will still be valuable.
I avoided Neovim for a while because I thought it took many hours of study to set up. Then found it actually took me roughly 20 mins to set up with all the major features. Downloaded Kickstarter then googled and copy pasted the lines to activate my LSPs or minor things like tab space number for different languages. I've no idea what most of my init.lua even does. And I love it! My absolute favourite feature is that in insert mode there are no ugly lines or pop ups, so I'm not disturbed while typing. Then in normal mode I immediately see any mistakes with unobtrusive error message boxes that are away from the text. The constant yellow or red underlines in VS code annoyed me a lot while typing.
13:50 i really don't agree. referring back to another section of documentation is practically zero cost if you do know the feature, and it makes it **far** easier to read documentation and understand the context of something when all you have to do it `CTRL-]` a phrase and then `CTRL-^` back or whatever.
20:18 feels like the task is just being done backwards. like if i have a formatter `format-code`, it would be nice if i could just do `:%format-code -` and then a `:w` rather than trying the other way around i guess. i just feel like that could have gone *slightly* better lol.
Must say, Helix is growing on me. I am going to give it a shot, in theory is solving all the major annoyances I am having with Nvim. It tampers a bit with the motions but it doesn’t seem too big of a change. Will I leave VSC for good? Final test will be using it on the monorepo Edit: forgot to say, Helix offers out of the bat what I like the most of both VSC and Nvim combined
For me, helix is missing three things. A file viewer to see files in the current project, an integrated terminal like vscode and a plugin system. Once these are added, I will switch to helix too.
@@bhallu9250 it runs in the terminal you can execute any shell cmmands by pressing : and sh please try going through the tutor. A plugin system is coming but you can do most things via shell commands and pipes. you can see files but presing the space bar and f which also has fuzzy search.
If it has different movements that vim, what’s the point. You’ll invest time in learning it and that knowledge won’t be transferable anywhere. With vim movements it’s totally different story. There are vim plugins for everything including google docs. Not to mention every server comes with it.
@@wawbagel The motions are not that different from vim. Most of the motions are transferable so this is incorrect. and anywhere it differs you can usually just change to be helix keymap. I did this with vimium.
This guy making poke at vscode for taking up few gigs is such a fckin red flag xd At least he did it at the beginning so we know with whom we’re dealing with
The #1 grip I have with vs code: that thing is just bloat. From memory, to crazy cluttered UI, to clunky UX. Bom opens a file in under a second, and I'm out editing away, and I can easily focus on the code, not the thousands of panes with the millions of buttons surrounding the code. Everything, i mean literally everything is a keyboard shortcut away.
Going to go against the grain; If you use the same tool for 10s of hours every week you absolutely should master the tool, really perfect it for your use The Pragmatic Programmer talks about mastering your tools and that helped inspire me to really get into the neovim rabbit hole and I'm glad I did
I change my file structure for personal projects the moment I feel it would "make more sense", I absolutely WILL spend all my time configuring vim. So no. Not using it.
If VSCode isn't for everyone, neovim is for pretty much no one. I mean, you know you're lying to yourself if you think customizing the hell out of your (pseudo-GUI) editor every week while you should be coding is not productive.
@@Amaraticando Nobody edits configs every week, lol. You edit once how you like and you're good. And many people find keyboard-oriented editors more productive. It's simply faster to make short keybinds than to click around menus. It can most definitely be more productive. If you've seen a vim guru work they can chop up and rearrange files like you've never seen. That type of thing is simply not possible with VSCode, even with the vim plugin.
As someone who uses VSCode, I've mainly used Vim for simple text editing if I'm in the terminal and want to make like a one line change and I don't have VSCode open already or if I'm on my company's remote box and I don't want to connect to it with VSCode to make that change. I would like to start using Vim more and phase out VSCode entirely, I just need to put the time in to it to work at the speed I do in VSCode.
Like a car with a manual transmission, its "THE" perfect interface to control a car .... vim motions is the perfect interface for navigating inside a document with your keyboard ... just like the manual transmission, once you have the feel for the interface it becomes a natural extension of intent
I am so glad Helix exits, Its basically vim, but it takes no configuration, just install the required LSP on the system. My config is just about 40 lines for extra formatters, theme, special cursor for insert mode and some Shortcuts
Brilliant video, I think... hmmm, it's also I think how neovim and a standard set of packages extend your mind and abilities. Vscode extends your mind by showing u which tabs you have open, provides you a terminL, provides you a tree, shows you your current like active path for thr language... as well as LSP and spelling All very useful. Personally for me, neovim extends my mind better in the ways I need/want it. Navigation is just insane with neovim, editing is insane. Auto collapse of functions and hiding of docstrings allows me to look at the code, but also write excessive documentation in functions which is encouraged... Go to definition in python just jumps to the top of thr file, I might try to sort it out. Also that edit list thing looked awesome, as well as pin. Will look into soon, in another month I will give my config a bit of a look 😊
The big issue IMHO is most people seem to think you install neovim and you are suddenly on prime's level of ability when you start neovim up. Thats simply not the case. You can learn 80% of what you need to be productive in an afternoon of using neovim tutor. Then you use neovim until you find something that is a pita, annoying, or something that you seem to be manually repeating. 9 times out of 10 there will be something built in to neovim to turn a 10 minute repetitive chore into muscle memory that takes less than a second. If there isnt something built in or the built in solution isn't to your liking, there is a 99% chance there is an easy to install plugin that solves the issue or improves default behavior. Repeat the above until eventually you go from "OMG how do I quit vim" meme to nearing Primeagen level vim god. Neovim and vscode are like comparing apples to oranges. Both may be text editors (fruit) but 1 is packaged into neat self contained sections and the other you create the sections yourself based on your own preferences.
I have heard the same for Eclipse, Idea, NetBeans, VS Studio, WebStorm, RubyMine, PyCharm, Atom and even DreamViewer. Nowadays, I just use Sublime because it's fast and doesn't have any complex features w/o plugins. I don't want to learn any more shortcuts or plugins to current best IDE that would slip and fall down in 2-5 years.
21:50 if you use ESLint as a formatter than Ideally you don't use Prettier or at least use the Prettier ESLint plugin and still disable Prettier in your ide because ESLint can autofix on save or be used as a formatter
I've never used any of these distros, just slowly built upon my config adding features as i felt i needed them, and i have to say i've never had the "i updated something and now everything is broken" meme happen, i usually just update all plugins at once without much thought and stuff keeps working as normal
I'm exclusive neovim user and configured everything to my preference; I know there is a lot of documentation but I never really understand it so I just ask Chatgpt or Google instead... Skill issue
Learn to code first instead of configuring your vim personal development environment (PDE). If you think that your vim configuration is not good enough, you will burn yourself out configuring your setup, rather than productively coding.
I started coding recently, Seeing videos about neoVim was a hype, the inferface seems cool and the speed people program incited me to pursue how to install and use neoVim. My experiences with code are barely zero and my IDE was vsCode, trying to use neoVim was really exhaustive even tho I'm still trying. The hype was the principal factor and how light it is really inspires me to keep trying. But understanding basic linux and basic plugin-management seems nothing basic to someone as new to codingo as I am. I know it's different, but I'm one of those who struggled a lot with it. Happily I was able to quit it in the first try but I had to research. I intend to go try neoVim but right now my understanding is not compatible. I know coding is very hard, but even in the most advanced medicine you can find people who just settle for what they already know.
4 months ago i was just the same, truggle with even install a plugin them followed Prime's and switch to Lazy by my own, right now i barely can config anything my own just but i can set up basic stuff and i have so much value time configuring neovim and linux, it helps me have more understand about how the machine works than just doing homework at my frontend bootcamp
I think when you start to code vscode/intellij(jetbrains) is totally fine. There you can install vim motion plugin if you are ready. After getting used to coding, vim motions and the linux terminal it's way easier to go full nvim. If you go nvim start with primegeans setup videos and build it from zero. Also, its easier to know what you NEED from nvim after experience with an IDE. One really nice thing about nvim is the ability to go minimal. The longer I do this job the less I need.
The time you invested could be used for something useful. However, learning Vim motions is useful, as a lot of programs support them and you eventually have to SSH into servers with no editor but Vim (not neovim).
@@Amaraticando I'd argue that learning vim motions is about as useful as learning to play hacky sack. You're not going to be more productive nor are you going to be faster, therefore learning it becomes a recreational activity you do for fun.
can you please increase your mic volume. Every time I check your stream I am in need of increasing my laptop volume and when I go to another video I need to go down
28:41 Obviously, the comment is ripping on VSCode which is considered good "out-of-the-box" with limited NEED for configuration. The reference to "professional" settings represent these default settings. I think this comment is dumb, since you can be perfectly productive with whatever you decide on using, and VSCode has relatively good configuration options, which should be okay for most users. The difference lies in if you are (a) willing to get "caught" in the MS ecosystem, and (b) if you're comfortable with a GUI editor which soaks up resources. Besides this, the discussion is inane, and I couldn't care less what everyone else is doing.
I love how people say they work on a server so they need to know vim. I remember time when my whole team used remote machines for python development, and Emacs Tramp was killer feature for me (edit remote files on local machine and sync it for you via protocol you like). Ping was not great so vim was luggy, decisions with rsync also was annoying.
I am definitely NOT in the "I want to be able to customize everything" camp. I don't even change my default desktop wallpaper. Using VSCode with the popular plugins means one less thing I have to worry about. Definitely no NeoVim for me.
Just use whatever works for you. I see all this vscode vs vim thing kinda stupid. All these guys probably code in languages which have to deal with backend, web development or system level programming. They forget that there is whole world of programming outside this scope. E.g game development. Android/ios app development. Thay all need their own set of tools and no point in configuring vim to do that as it will never come close to original tools and support by the company. I my self have been using vim for my entire development career but never have i ever pushed someone to use it. use whatever gets the job done.
@@Trizzi2931 This! My rule for tools is that the correct tool for the job is whatever allows you to get your work done to the standards expected of you in the time required of you. We see this kind of complaining with calculators, too, where people who use HP's 'RPN' entry tend to extol its virtues in such a manner as to intentionally make people using 'normal' scientific calculators feel like they're supposed to be inferior or something. It's just a calculator -- it's just an IDE. If they're giving you work that works, then just leave people be!
1:50 OMG I remember that majkinetor guy from 15 years ago when I was using AutoHotkey on Windows! Dude, if you by random chance read my comment here, hello. Long time not seen.
My complaint about nvim is that the ecosystem is a collection of constantly shifting, sparsely documented, adhoc scripts which make poor assumptions about my environment and curl random binaries to random locations. My experience with VSCode is it's that but exponentially worse and more opaque. If you like VSCode, you're using a common OS and it hasn't broken on you yet despite its inherently fragile design.
13:49 I would say it is a bit unwelcoming, becasue you only rely on small group of people and their belives that everyone should begin journy of using vim from rtm and not from dead simple open, type. guys trying to advocate simplicity but like ignoring fact that this is kind of stick versus automate, it is simplicity of a tool not a simplicity of usage.
@@terryriley6410 I like laying in bed and playing video games. But there is a reason for not doing this things all the time, even if I like them. I get that people like to discuss editors or politics, but at certain point this discussion is becoming pointless and just waste of time. Especially if they pretend like this pedantic managing of their editors somehow saves them time.
@@anj000 The only reason is that you like other things as well or you have to stay productive otherwise you can't sustain playing videogames all day. It is highly probable that people discussing editors and configuration have similar conditions and behaviours. You are judging your imaginary vim users who waste away talking about vim and never doing anything else.
Nowadays almost every language be it their linter formatter, etc has got a setup video on RUclips as well as a hell lot of articles saying line by line what to do as well as the source code. If you are trying to use NeoVim and want to make it an ide (which I don't understand why) you should be aware that you will need to understand lua and their manual and you have got the videos as well (you may say some videos are old but most probably they'll still work since a lot of people are using those 1 to 2 year old configurations and plugins' updates) but the control you will have is godly, default vim gives so much control only using the keyboard and the plugins on top is like 🤯👌
@@sumitmamoria the pragmatic engineer did a whole blog post about it. Just search for it. There even are alternatives that were trained using more ethical way, not simply stealing licensed code like Microsoft did it.
I have installed and configured by my self nvim, but i don't use. Use a jetbrains product because they have a better git client, and other stuff. I don't use nvim even is configured by me for me, i recognise nvim have same functionality what is common jetbrains product have. So why i should to move? i have install vim plugin remap some keybing for different mode and go ahed.
For those wondering what makes LazyVim different, as a happy user since it came out I can try. The magic comes from the core plugin, lazy.nvim, which, IMHO completely revolutionized plugin management. Lazy works by only loading plugins when you need them, such as plugins that you only need for a keymap, or one that is only loaded as a dependency to another. LazyVim is your opportunity to see how the inventor of lazy would use it to optimize a config, and as such has all of the great lazy loading knowledge to keep the distro powerful yet still super fast. Lazy also makes it easy to extend a plugin by leveraging the lua table syntax to just combine all the configurations you may have defined in different files. The result is that you don't even need to do any fiddling with the after folder, most of your logic will just sit in the plugins folder where you will define some tables to both grab and configure all in one place. You can download a new plugin, overwrite, or even extend the current implementation using just the facilities of lazy. No more defining the plugins in a different file from where you configure them, and it makes adding dependencies to existing plugins like telescope a breeze
Well sort of, just that tags don't know about scope, overloads/ad-hoc polymorphism, aliasing etc etc. Consequently tags work OK with pretty much exactly C and nothing else. If you want go to definition to actually work reliably in most programming lamguages you're not getting around actually parsing your code.
So basically 0 to 50 in 5 seconds but then you're stuck and can't go near 100 since there are no plugins, it's sometimes useful to have libraries like that that get you started quickly but for your text editor ? I do't think so
@@heroe1486 it's great if you want an editor that is fast, modal, and has a lot baked in. So far helix has done everything I need. If you want a fully customizable to make the editor your own neovim is better. I find I just want to learn a set of tools that does what I need and get to coding. Otherwise I tweak and tweak and tweak and don't get as much done. 80/20 rule basically. To get that last 20 percent requires a lot of work that I can be spending coding instead.
@@marcs9451 sorta, because with helix I just do 'pacman -S helix-editor' and code away since it has everything baked in. With neovim there is a lot more to do after I install to get it to a state that helix is by default (even if using a neovim distro). Depends what you want. Easy install and get running. Or do I want to fully make editor my own with tweaking. For me I just want to install and code, as long as editor does what I need (which helix does and neovim does not)
There is no way to get my workflow without hussle into NeoVim. I define infrastructure in yaml & hcl, build pipelines for jenkins, do data analysis and visualization with python, write backend with java & go... much luck using NVim if you don't do any specialized work. Oh... and debugging.
I do use nvim for simple editing just because my pc is refusing to run nvim properly but it's more convinient for simple edits because it doesn't load for 2000 years. ( I use vim emulator so vim motions isn't an issue for me )
I'd prefer Borland Turbo Pascal IDE for Rust development. Most of my development is done with screen + joe, mostly due to Wordstar shortcuts. Local development is done with Visual Studio Code, though I don't like it that much, but it does the needful.
I'm a proponent of the "distros". I've been using NvChad for a little while, but I want to try out LazyVim, because I haven't settled down yet. I like the richness, but I'm not a huge fan of over-customizing my own config. I hate choosing new keymaps. My muscle memory can learn pretty much anything, but inevitably I choose something that clashes with the default keymaps in something else I want to use and then I have to remap that and before I know it I have to remap everything in a huge chain. It's so much better to just get used to default keymaps and if everyone else does the same, usually they work together reasonably well 😅
Have you tried webi vim-essentials? (for vim, not neovim) (it's my thing, and I'm a minimalist who wants maximum portability between computers, quickly)
Fear not, for I have noticed your habit of taking a drink when you want to read. Edit: If this whole video was just you and him talking, I'd have still watched it.
I'm 90% sure the e is pronounced /œ/ (that's like the e /ɛ/ in get or set but with rounded lips) (alternatively that's like the o /ɔ/ in off or dough but with the tongue in the front of the mouth)
I started using Neovim a few years ago and immediately grew to be over 6'7" and instantly sold my company for a billion dollars.
Thank you TJ, very cool.
How to tell you use NvChad without telling you use NvChad
Neovim also grows you an extra set
@@kenb1 And promotes you to the "1000x engineer" rank immediately upon installation.
i use almost only normal vim not neovim just some plugins and settings i prefer in vimrc, am i the weird person
Happened to me to man, its kind of weird
folke (the creator of LazyVim, lazy.nvim, tokyonight.nvim, flash.nvim, etc.) I think has acquired the role that tpope had for regular vim. The man is creating so many extensions and plugins of such high caliber. And maintaining ALL OF THEM, the guy is insane.
pillars of the community
You can't pay these people enough. I don't think I will ever be able to repay them
That guy has a life?
I’ll never understand ther stupidity of maintaining two different projects that use the same word lazy. It’s very confusing.
@@MrAlanCristhianhe runs a company I believe
20:58 Nails it for me. It's basically like if 85% of the world use Phillips (plus-shape) head screws and 2% of the world use Robertson (square-shape) screws. People carrying Phillips screwdrivers want to screw every hole, and then see a square and get mad. People carrying Robertson screwdrivers never had the need to screw every single hole in existence, if they did they'd never buy a Robertson. So when they see a plus they aren't bothered, and they are content with screwing just their own holes.
24:55 VSCode settings configuration generally does not involve heavy json digging. Just press Ctrl+{comma} and text search for the setting you want to change and it is presented to you with a clean GUI.
but you have to know what you are searching for. its a heavy search first design and if you want anything programmatic, it becomes impossible (for some things)
@@ThePrimeTimeagen Nothing's totally foolproof if the user is unfamiliar with the system, but compared to NVim (or even JetBrains offerings) it's straightforward, comparatively reliable, and flexible. And when there's a desire for stitching together chunks of someone else's config the JSON is there for you. Heck, if you commit the workspace .vscode directory into source control, the editor will do the stitching for you. Commit a .devcontainer config and VSCode will stitch in a docker container too.
Pozidrive and Torx user here.
Nah VSCode is extremely time-consuming when you need to change some really specific setting in the editor because 9/10 times it's not even documented, if you haven't encountered this, you just don't configure settings outside what VSC is prepared for so it works for you
"There is an idea that you have to have that NEWEST thing"
Realized that a couple of months ago. Started asking myself "What the hell I switch to %that new thing% for?" and most of the time sticked to things that are just GOOD ENOUGH - saved huge amount of time.
Old things people still use have proven themselves. New things still need to do this.
yup. still using perl as my goto lang....
The thing about VSCode is it works with a single click until it doesn't at which point you'll be spending 10 times the amount of time fixing the issue because all our traffic goes through a proxy. So you're just digging through json files trying to find the correct option, except it's not documented basically anywhere.
16:42
Complaint: There are multiple ways to do something.
Solution: We need a multi hammer, so we don't have to look for the right tool for the job
we need a hammer factory config factory to build right config factory to build the best tool for everyone
@@LionKing-qp1lk already exist and is called vs code
@@LionKing-qp1lk written in Java
Or how about you do the obvious thing and reduce the problem to only doing things in one way? Like every other editor out there?
@@gagagero The obvious thing....???
The only obvious thing about programming is that there is no "one way" for every problem or use case.
But I agree, we should all use the one editor that's worked so well it stands the test of time....
The obvious one size fits all "One Way"
Notepad :D
As neovim newbie (about a week) I am genuinely impressed how solid the documentation and guides are for it, at this point I have it looking nice I have lsp stuff autocomplete etc. a debug setup updated manuals for C++ and a bunch of other things all integrated in with very little conflict and I'm pretty much happy and setup for everything I would want.
liar
@@stefanplusplus917 Not saying it was easy it was just a lot easier than I expected haha and to update that I started to have some trouble when I tried to integrate gdb to debug cpp it works but not smoothly at all
@@stefanplusplus917no, same experience for me. Or i guess you could say we are both liars.
C++ mentioned
There's almost too much documentation in my experience. I am liable to fall into a bottomless rabbithole any time I try to look up something simple.
I think the people complaining about the time to setup Neovim do have a point. Vim/Neovim get a lot of flack for vim motions but these should be treated as a separate thing at this point, pretty sure most IDEs have plugins for vim motions at this point so you don't need to use Neovim for vim motions. No, Neovim is for people who legitimately like to customize their environment. For us, that "time it takes to setup" is the whole point. It changes the way you think about UIs, actually. You take that to the next level and you get ricing Arch Linux enthusiasts.
That’s why there are setups like lazyvim that are ready to use with good defaults
This is mostly true, but pretty much all of those editor plugins are missing some of vim motions. And the motions themselves tend to be harder to customize than in nvim.
This.
I rice Arch, btw.
Blessed be the day upon thou fellow traveler, may thy path be full of riches and thy spirit led by light. Wouldst thou like to talk about our savior, Richard Stallman? He hath a message of joy to be delivered unto the world.
Here's the thing: once you've configured nvim to work with your specific workflow, there's hardly ever anything to setup. Your config is a git pull away. One can get lost in customizing vs code to their hearts content as well, that isn't a vim-specific thing.
VSCode plugins are always breaking, there's a 10% probability that pylint will work correctly on a given machine. The broke attaching to pods in kubernetes with 1.80.
@pnk4996I had so many problems with pylint no longer working after an update and spend hours trying to fix it just to end up at open github issues with no answer.
13:00 no way, the neovim community is SO HELPFUl. no RTFM attitude, it's supremely wholesome. in reddit i have NEVER seen any hostile/abrasive behavior. there is a great community of supporting new plugins and knowledge sharing. the neovim community is so wholesome
I think that by "using vim for small changes", people mean stuff like editing nginx configs or htaccess files, browsing through logs, that kind of stuff.
Small server-side jobs that are a lot faster in vim than in nano, but still take less than 1% of their overall coding time.
35:00 how do you do that thing where you pin the context to the top?
neovim-treesitter-context
@@ThePrimeTimeagen this is nice. I like it
Now in defence for some of the people that struggle with the Nvim community. Because i do think that the culture is that of someone that is expected to know a certain amount, forgetting that a new person to Neovim in this day and age does not come from Vim. They come from an IDE where you do not have to deal with plugins, a configuration language (however easy it might be) and just how these things are connected.
I felt like it was a heavy hurdle to get across to customize anything outside the complete standard of NvChad which is what i ended up with. If not for Vim motions (before realizing i could just set this up in Vscode) i'd prolly just bail that ship in the first place. It's not easy if you're not used to it.
I honestly cannot fathom how neovim could be hard at such stage, maybe because I started programming outside of an IDE, I used notepad++ and opened windows terminal to compile my code with mingw. Neovim is 1000x simpler than Emacs, honestly if you just follow the ChrisAtMachine series you'll basically end up with a good setup
I recently started I did find a lot of cases of assumed knowledge but there is so much documentation and so many guides that I just had to go read for a while and I was able to get everything working.
Python folks can't argue about the package manager complaint. Making, distributing, maintaining, and even just installing deps for a script or app is kinda a nightmare in python, ngl.
How so? It's literally just pip install -r and passing in a literal txt file? There isn't a lot of guess-work involved unless your requirements file grows to something over 10 or 15 direct dependencies (not counting dependencies of your dependencies). That + virtualenv takes care of MOST of the problems you could POTENTIALLY have in Python. PIP is such a god-send compared to package managers in most other languages.
@@malaista pip has struggled with nested dependency resolution in the past; idk about now. Plus there is pipenv, poetry, conda. Then virtualenv isn't alone either, with pyenv and pyvenv. Then distutils used to not use TLS, so you had to use twine, but maybe distutils uses TLS now, so unclear. That's just it, nothing is very clear with python build and distribution. Some people like that. Some don't. Should I build a wheel? Or maybe pants and pex? Hmm. Give me cargo, or give me cake.
You're over exaggerating, for large projects it's possible and even likely without the right tools but not for a script, for that and even simple projects venv alone get you covered, add piptools for more goodness, pyenv optionally if you want a specific python version and your distro doesn't easily give that
@@theherk PIP has gotten better at dependency resolution but it's obviously not perfect like most package managers with big dependency sets. PIP and virtualenv are packaged with Python since Python 3, no reason not to use them since they use TLS natively. Conda is the choice thwt only made sense whrn Python2 was the standard. Always build wheels. (Organized and Standardized by a PEP).
ALL else is fluff and shouldn't be used in general.
Devs who create dependency hell daily complaining about packer and Plug lmao
my story with vim was slow, mainly i started using it and stuck with it for a few years. first it was low stakes stuff at first, home sysadmin type stuff like editing conf files, then I used it as a personal typewriter (editing copy made me fall in love with modal text editing). with little bit of time you pick up more and more things, apply it to more diverse tasks, and now it fits like a glove. i totally get it being hard at first but very worth to stick with it
I got into Vim accidently while doing a lot of Linux shell stuff myself setting up my home server network. A happy accident.
I wish everyone good fortune in the Editor War. ❤
Long live the editor war, may it never end. After all hasn't it been going on for at least 50 years now?
@@benjnseWar with Oceania never ends. Glory to Big Brother!
⚔️
Wishing you survival and success in these trying times.
@@binladen-ci7jm You don't stand a chance as long as I keep using MS Word
15:53 I love how quickly he named them all.
One of the things I've noticed change in my behavior when I gave neovim a try for nearly 7 months was that I was adapting my behavior and my interests around what I can do well in neovim while thinking that I'm adapting neovim to my interests. I spent so damn much time trying to even get comfortable with somewhat above basics and once I had to stop using it for a month, almost everything felt like out of touch with my "nervous system" if I can put it this way.
this is what addicts feel when they stop huffing their favorite brand of paint.
@@binladen-ci7jm he didn't say he was nervous. The word nervous did feature in the comment though.
@@binladen-ci7jm so you are saying that was a joke or something? Fair enough. Your joke is dumb.
It would be awesome call folke to a chat, the audience gonna sky rocketed.
How is it possible for a human to create so many vim plugins, plugin manager, vim distro, the best tokyonight I ever seen, cool stuffs, maintain them, and have a life/run a enterprise/be surfist idk?
He's like a Terry A. Davis vim version, but with social life.
21:54 formating in node got a lot of tools yes, but the one most use is prettier, and if you use deno then you can use deno format, as it is build in.
Learned VIM early on. Switched to VSCode for a windows project, using VIM extensions. One day I went to write an edit macro on a 20k line legacy file... it took 10 minutes to execute. What? I thought this was instant in VIM. So I got MINGW installed and set up, tested the same macro in vim... Instant. never looked back. (Although I occasionally use emacs + evil mode too!)
I recently started my Neovim journey (I tried the vscode vim extension thing it didn't click, so I just jumped right in to vim.) While I don't know if all the setup will be worth it productivity wise I will say that the learning experience is absolutely necessary. A while ago I got stuck after a vscode extension broke. I spent hours trying to figure out what the problem was, only to find out that it was a glitch, I then spent hours trying to find a work around before giving up and putting my project on hold. The problem is that I didn't know what the plugin was doing under the hood, and I didn't know how it was doing it. With Neovim it is not only necessary, but also easier to learn how your tools work.
Even if I have to go crawling back to vscode one day (please no) I am fairly certain that what I learned setting up a Neovim configuration will still be valuable.
I avoided Neovim for a while because I thought it took many hours of study to set up. Then found it actually took me roughly 20 mins to set up with all the major features. Downloaded Kickstarter then googled and copy pasted the lines to activate my LSPs or minor things like tab space number for different languages. I've no idea what most of my init.lua even does.
And I love it! My absolute favourite feature is that in insert mode there are no ugly lines or pop ups, so I'm not disturbed while typing. Then in normal mode I immediately see any mistakes with unobtrusive error message boxes that are away from the text. The constant yellow or red underlines in VS code annoyed me a lot while typing.
25:43 Best hot take, that is actually not hot, but cold calculated and smart.
there is a alternative to both VS and Vim, this is indeed really cold calculated move to downgrade the whole topic to MS vs Bram Moolenaar
Maybe Neovim should have a default package manager
then it would look like a proprietary garbage if that happens.
@reisaki18 so rust is proprietary because it has a default package manager 😂
it has a built-in package "manager", but it sucks for anything practical. That's why people create those lazy solutions.
13:50 i really don't agree. referring back to another section of documentation is practically zero cost if you do know the feature, and it makes it **far** easier to read documentation and understand the context of something when all you have to do it `CTRL-]` a phrase and then `CTRL-^` back or whatever.
20:18 feels like the task is just being done backwards. like if i have a formatter `format-code`, it would be nice if i could just do
`:%format-code -` and then a `:w` rather than trying the other way around i guess. i just feel like that could have gone *slightly* better lol.
Must say, Helix is growing on me. I am going to give it a shot, in theory is solving all the major annoyances I am having with Nvim. It tampers a bit with the motions but it doesn’t seem too big of a change. Will I leave VSC for good? Final test will be using it on the monorepo
Edit: forgot to say, Helix offers out of the bat what I like the most of both VSC and Nvim combined
It's great. You should do it
For me, helix is missing three things. A file viewer to see files in the current project, an integrated terminal like vscode and a plugin system. Once these are added, I will switch to helix too.
@@bhallu9250 it runs in the terminal you can execute any shell cmmands by pressing : and sh please try going through the tutor. A plugin system is coming but you can do most things via shell commands and pipes. you can see files but presing the space bar and f which also has fuzzy search.
If it has different movements that vim, what’s the point. You’ll invest time in learning it and that knowledge won’t be transferable anywhere. With vim movements it’s totally different story. There are vim plugins for everything including google docs. Not to mention every server comes with it.
@@wawbagel The motions are not that different from vim. Most of the motions are transferable so this is incorrect. and anywhere it differs you can usually just change to be helix keymap. I did this with vimium.
how you config your neovim to switch working directory in 35:18? seems like your key binding is Ctrl + f
0:22 The moment you realize that somebody only knows of insert mode of vim.
This guy making poke at vscode for taking up few gigs is such a fckin red flag xd At least he did it at the beginning so we know with whom we’re dealing with
say more..
26:00 Thats why i switch from c# to rust and from Visual Studio to VS Coden and now getting into NeoVim
@32:00 "OH ... I didn't expect to see reverse polish notation here ..."
LOL -
NOBODY expects the spani^H^H^H^H reverse polish notation.
The #1 grip I have with vs code: that thing is just bloat. From memory, to crazy cluttered UI, to clunky UX. Bom opens a file in under a second, and I'm out editing away, and I can easily focus on the code, not the thousands of panes with the millions of buttons surrounding the code. Everything, i mean literally everything is a keyboard shortcut away.
Going to go against the grain;
If you use the same tool for 10s of hours every week you absolutely should master the tool, really perfect it for your use
The Pragmatic Programmer talks about mastering your tools and that helped inspire me to really get into the neovim rabbit hole and I'm glad I did
I change my file structure for personal projects the moment I feel it would "make more sense", I absolutely WILL spend all my time configuring vim.
So no. Not using it.
You need self discipline not a new editor :/
LazyVim has been great so far for me as I got into neovim
You have to love the irony of the guy who compared code editors to planes (and cars and trousers) critiquing someone else's analogy.
Neovim is not for everyone nor is VSCode or any other editor/IDE.
But my opinion is the one and only, and I don't want to put effort into trying to see something from someone else's perspective
If VSCode isn't for everyone, neovim is for pretty much no one. I mean, you know you're lying to yourself if you think customizing the hell out of your (pseudo-GUI) editor every week while you should be coding is not productive.
I would say vs code is for everyone.
@@Amaraticando Nobody edits configs every week, lol. You edit once how you like and you're good. And many people find keyboard-oriented editors more productive. It's simply faster to make short keybinds than to click around menus. It can most definitely be more productive. If you've seen a vim guru work they can chop up and rearrange files like you've never seen. That type of thing is simply not possible with VSCode, even with the vim plugin.
35:00 wait what is he using for the context thing?
I change my config when Prime shows something really helpful that I didn't know about. Other than that, it largely remains untouched.
As someone who uses VSCode, I've mainly used Vim for simple text editing if I'm in the terminal and want to make like a one line change and I don't have VSCode open already or if I'm on my company's remote box and I don't want to connect to it with VSCode to make that change. I would like to start using Vim more and phase out VSCode entirely, I just need to put the time in to it to work at the speed I do in VSCode.
One of the extensions in vscode uses a real neovim binary to perform operations. Grab that and go.
Like a car with a manual transmission, its "THE" perfect interface to control a car .... vim motions is the perfect interface for navigating inside a document with your keyboard ... just like the manual transmission, once you have the feel for the interface it becomes a natural extension of intent
I am so glad Helix exits, Its basically vim, but it takes no configuration, just install the required LSP on the system.
My config is just about 40 lines for extra formatters, theme, special cursor for insert mode and some Shortcuts
Brilliant video, I think... hmmm, it's also I think how neovim and a standard set of packages extend your mind and abilities. Vscode extends your mind by showing u which tabs you have open, provides you a terminL, provides you a tree, shows you your current like active path for thr language... as well as LSP and spelling
All very useful. Personally for me, neovim extends my mind better in the ways I need/want it. Navigation is just insane with neovim, editing is insane. Auto collapse of functions and hiding of docstrings allows me to look at the code, but also write excessive documentation in functions which is encouraged...
Go to definition in python just jumps to the top of thr file, I might try to sort it out. Also that edit list thing looked awesome, as well as pin. Will look into soon, in another month I will give my config a bit of a look 😊
The big issue IMHO is most people seem to think you install neovim and you are suddenly on prime's level of ability when you start neovim up. Thats simply not the case.
You can learn 80% of what you need to be productive in an afternoon of using neovim tutor.
Then you use neovim until you find something that is a pita, annoying, or something that you seem to be manually repeating. 9 times out of 10 there will be something built in to neovim to turn a 10 minute repetitive chore into muscle memory that takes less than a second.
If there isnt something built in or the built in solution isn't to your liking, there is a 99% chance there is an easy to install plugin that solves the issue or improves default behavior.
Repeat the above until eventually you go from "OMG how do I quit vim" meme to nearing Primeagen level vim god.
Neovim and vscode are like comparing apples to oranges. Both may be text editors (fruit) but 1 is packaged into neat self contained sections and the other you create the sections yourself based on your own preferences.
I have heard the same for Eclipse, Idea, NetBeans, VS Studio, WebStorm, RubyMine, PyCharm, Atom and even DreamViewer. Nowadays, I just use Sublime because it's fast and doesn't have any complex features w/o plugins. I don't want to learn any more shortcuts or plugins to current best IDE that would slip and fall down in 2-5 years.
*Dreamweaver
@@baky5372 I guess my brain substituted original name for something less cringe before saving the memories
21:50 if you use ESLint as a formatter than Ideally you don't use Prettier or at least use the Prettier ESLint plugin and still disable Prettier in your ide because ESLint can autofix on save or be used as a formatter
could have just ended the title after 3 words because that's like a universal constant
I've never used any of these distros, just slowly built upon my config adding features as i felt i needed them, and i have to say i've never had the "i updated something and now everything is broken" meme happen, i usually just update all plugins at once without much thought and stuff keeps working as normal
I'm exclusive neovim user and configured everything to my preference; I know there is a lot of documentation but I never really understand it so I just ask Chatgpt or Google instead... Skill issue
I wanted to learn to code, so i went to config my vim setup. Someday ill learn to code. For now, im still setting up vim config
Learn to code first instead of configuring your vim personal development environment (PDE). If you think that your vim configuration is not good enough, you will burn yourself out configuring your setup, rather than productively coding.
@@therealg9542 thanks, it's only been 5 months though. I think another 5 months of config and I'll be ready to start coding
"Just pull a plugin from 5 years ago", "I don't know anything about React", why are you giving advises then?
I started coding recently, Seeing videos about neoVim was a hype, the inferface seems cool and the speed people program incited me to pursue how to install and use neoVim.
My experiences with code are barely zero and my IDE was vsCode, trying to use neoVim was really exhaustive even tho I'm still trying. The hype was the principal factor and how light it is really inspires me to keep trying. But understanding basic linux and basic plugin-management seems nothing basic to someone as new to codingo as I am.
I know it's different, but I'm one of those who struggled a lot with it. Happily I was able to quit it in the first try but I had to research. I intend to go try neoVim but right now my understanding is not compatible.
I know coding is very hard, but even in the most advanced medicine you can find people who just settle for what they already know.
4 months ago i was just the same, truggle with even install a plugin them followed Prime's and switch to Lazy by my own, right now i barely can config anything my own just but i can set up basic stuff and i have so much value time configuring neovim and linux, it helps me have more understand about how the machine works than just doing homework at my frontend bootcamp
I think when you start to code vscode/intellij(jetbrains) is totally fine. There you can install vim motion plugin if you are ready.
After getting used to coding, vim motions and the linux terminal it's way easier to go full nvim.
If you go nvim start with primegeans setup videos and build it from zero.
Also, its easier to know what you NEED from nvim after experience with an IDE. One really nice thing about nvim is the ability to go minimal. The longer I do this job the less I need.
I'm a developer for well over a decade. Trust me, using VsCode is perfectly fine.
VsCode is really good for a lot, a LOT of development.
The time you invested could be used for something useful. However, learning Vim motions is useful, as a lot of programs support them and you eventually have to SSH into servers with no editor but Vim (not neovim).
@@Amaraticando I'd argue that learning vim motions is about as useful as learning to play hacky sack.
You're not going to be more productive nor are you going to be faster, therefore learning it becomes a recreational activity you do for fun.
can you please increase your mic volume. Every time I check your stream I am in need of increasing my laptop volume and when I go to another video I need to go down
Theres VS Codium the VS Code without microsoft and theres lapce written in Rust
i'm also writing one with tauri
28:41 Obviously, the comment is ripping on VSCode which is considered good "out-of-the-box" with limited NEED for configuration. The reference to "professional" settings represent these default settings. I think this comment is dumb, since you can be perfectly productive with whatever you decide on using, and VSCode has relatively good configuration options, which should be okay for most users. The difference lies in if you are (a) willing to get "caught" in the MS ecosystem, and (b) if you're comfortable with a GUI editor which soaks up resources. Besides this, the discussion is inane, and I couldn't care less what everyone else is doing.
I love how people say they work on a server so they need to know vim. I remember time when my whole team used remote machines for python development, and Emacs Tramp was killer feature for me (edit remote files on local machine and sync it for you via protocol you like). Ping was not great so vim was luggy, decisions with rsync also was annoying.
I am definitely NOT in the "I want to be able to customize everything" camp. I don't even change my default desktop wallpaper. Using VSCode with the popular plugins means one less thing I have to worry about. Definitely no NeoVim for me.
Just use whatever works for you. I see all this vscode vs vim thing kinda stupid. All these guys probably code in languages which have to deal with backend, web development or system level programming. They forget that there is whole world of programming outside this scope. E.g game development. Android/ios app development. Thay all need their own set of tools and no point in configuring vim to do that as it will never come close to original tools and support by the company. I my self have been using vim for my entire development career but never have i ever pushed someone to use it. use whatever gets the job done.
@@Trizzi2931 This!
My rule for tools is that the correct tool for the job is whatever allows you to get your work done to the standards expected of you in the time required of you.
We see this kind of complaining with calculators, too, where people who use HP's 'RPN' entry tend to extol its virtues in such a manner as to intentionally make people using 'normal' scientific calculators feel like they're supposed to be inferior or something.
It's just a calculator -- it's just an IDE. If they're giving you work that works, then just leave people be!
You could also use nvim with just the popular plugins I’ve been using default vim with no plugins and it’s still amazing
1:50 OMG I remember that majkinetor guy from 15 years ago when I was using AutoHotkey on Windows!
Dude, if you by random chance read my comment here, hello. Long time not seen.
My complaint about nvim is that the ecosystem is a collection of constantly shifting, sparsely documented, adhoc scripts which make poor assumptions about my environment and curl random binaries to random locations. My experience with VSCode is it's that but exponentially worse and more opaque. If you like VSCode, you're using a common OS and it hasn't broken on you yet despite its inherently fragile design.
yeah it’s a blessing and a curse that there are so many plugins and ways of doing things for vim
What are the opinions if we compare AstroVim vs LazyVim?
I unironically do modify my own trousers so uh... neovim it is!
Hold up - you use dvorak with vim? I never tried or heard of this - wouldn't all the movement be weird with that?
13:49 I would say it is a bit unwelcoming, becasue you only rely on small group of people and their belives that everyone should begin journy of using vim from rtm and not from dead simple open, type. guys trying to advocate simplicity but like ignoring fact that this is kind of stick versus automate, it is simplicity of a tool not a simplicity of usage.
I wonder how much time would people save if they were not discussing their text editors so much 🤔
This is a flawed take. People like doing this, why would they want to save time by not doing what they like. Are you obsessed with productivity?
@@terryriley6410 I like laying in bed and playing video games. But there is a reason for not doing this things all the time, even if I like them.
I get that people like to discuss editors or politics, but at certain point this discussion is becoming pointless and just waste of time. Especially if they pretend like this pedantic managing of their editors somehow saves them time.
@@anj000 The only reason is that you like other things as well or you have to stay productive otherwise you can't sustain playing videogames all day. It is highly probable that people discussing editors and configuration have similar conditions and behaviours. You are judging your imaginary vim users who waste away talking about vim and never doing anything else.
I use vim for simple text editing :p
Every server has Docker / Podman installed, I have an image that I can move around that has my config baked in
I modify my car and my trousers, checkmate atheists.
Their reactions are pretty toxic here IMO. They personify the problems listed in the article.
Nowadays almost every language be it their linter formatter, etc has got a setup video on RUclips as well as a hell lot of articles saying line by line what to do as well as the source code. If you are trying to use NeoVim and want to make it an ide (which I don't understand why) you should be aware that you will need to understand lua and their manual and you have got the videos as well (you may say some videos are old but most probably they'll still work since a lot of people are using those 1 to 2 year old configurations and plugins' updates) but the control you will have is godly, default vim gives so much control only using the keyboard and the plugins on top is like 🤯👌
Prime, how can you say you’re on team “don’t use microsoft “ and use copilot at the same time?
The argument goes like this - "If there is something approximately equivalent to copilot, then he is willing to ditch the MS product"
@@sumitmamoria theres plenty of alternatives out there.
What’s even funnier is that he said how unhelpful it is and yet keeps using that crap
@@wawbagel What alternatives that are about as good as copilot? Genuine question.
@@sumitmamoria the pragmatic engineer did a whole blog post about it. Just search for it. There even are alternatives that were trained using more ethical way, not simply stealing licensed code like Microsoft did it.
Vs Code is such a horrid "nothing" software. Features of a text editor with the startup time and RAM usage of a full blown IDE.
I have installed and configured by my self nvim, but i don't use. Use a jetbrains product because they have a better git client, and other stuff. I don't use nvim even is configured by me for me, i recognise nvim have same functionality what is common jetbrains product have. So why i should to move? i have install vim plugin remap some keybing for different mode and go ahed.
Helix... just loving it
For those wondering what makes LazyVim different, as a happy user since it came out I can try.
The magic comes from the core plugin, lazy.nvim, which, IMHO completely revolutionized plugin management. Lazy works by only loading plugins when you need them, such as plugins that you only need for a keymap, or one that is only loaded as a dependency to another.
LazyVim is your opportunity to see how the inventor of lazy would use it to optimize a config, and as such has all of the great lazy loading knowledge to keep the distro powerful yet still super fast.
Lazy also makes it easy to extend a plugin by leveraging the lua table syntax to just combine all the configurations you may have defined in different files. The result is that you don't even need to do any fiddling with the after folder, most of your logic will just sit in the plugins folder where you will define some tables to both grab and configure all in one place.
You can download a new plugin, overwrite, or even extend the current implementation using just the facilities of lazy.
No more defining the plugins in a different file from where you configure them, and it makes adding dependencies to existing plugins like telescope a breeze
I started with vim, arch Linux, suckles, the whole thing. Now I use windows and vscode, and I am more productive than ever.
Same bro, when I'm in arch I'm always configuring my config files. Now im on windows with WSL, I just open the terminal then start coding.
@@emptybottle1200 why were you always configuring your config files ?
Not saying people need to use it, but there is an alternative to VS Code. Codium is just VS Code with all the Microsoft parts ripped out.
no copilot though? or have i been massively misinformed ?
"Go to definition" is included in default vim . . . you just need to make sure you've compiled a tags file for the project.
Well sort of, just that tags don't know about scope, overloads/ad-hoc polymorphism, aliasing etc etc. Consequently tags work OK with pretty much exactly C and nothing else. If you want go to definition to actually work reliably in most programming lamguages you're not getting around actually parsing your code.
RTFM is how Arch users say "KYS"
lsp, treesitter, are built into helix out of the box, just saying 😜 (just install and start coding)
So basically 0 to 50 in 5 seconds but then you're stuck and can't go near 100 since there are no plugins, it's sometimes useful to have libraries like that that get you started quickly but for your text editor ? I do't think so
@@heroe1486 it's great if you want an editor that is fast, modal, and has a lot baked in. So far helix has done everything I need. If you want a fully customizable to make the editor your own neovim is better. I find I just want to learn a set of tools that does what I need and get to coding. Otherwise I tweak and tweak and tweak and don't get as much done. 80/20 rule basically. To get that last 20 percent requires a lot of work that I can be spending coding instead.
Just have self discipline to not tweak endlessly, that's not an editor issue
@@marcs9451 sorta, because with helix I just do 'pacman -S helix-editor' and code away since it has everything baked in. With neovim there is a lot more to do after I install to get it to a state that helix is by default (even if using a neovim distro).
Depends what you want. Easy install and get running. Or do I want to fully make editor my own with tweaking. For me I just want to install and code, as long as editor does what I need (which helix does and neovim does not)
Any if the extra stuff you need to do in helix can be achieved by using the command line.
Vim is great for simple text editing IMO, because it’s fast and runs from terminal or with a GUI
To run a chainsaw you need fuel - it costs money, the knife just needs occasional sharpening. And when the chain breaks forget about it😅
the cost of labor overtakes the cost of equipment and the fast results pays those bills - very little is free
Maybe they’re saying they only use vim on ssh or smth although you could setup the vscode ssh server extension
Personally whenever i program i boot up good ole Emacs start vterm and then enter nvim.
There is no way to get my workflow without hussle into NeoVim.
I define infrastructure in yaml & hcl, build pipelines for jenkins, do data analysis and visualization with python, write backend with java & go... much luck using NVim if you don't do any specialized work.
Oh... and debugging.
Asides from data viz and maybe jenkins, these are all solved problems lmao.
I do use nvim for simple editing just because my pc is refusing to run nvim properly but it's more convinient for simple edits because it doesn't load for 2000 years. ( I use vim emulator so vim motions isn't an issue for me )
Why are people still arguing about this shit? Just code, you fools! Code!
I'd prefer Borland Turbo Pascal IDE for Rust development. Most of my development is done with screen + joe, mostly due to Wordstar shortcuts. Local development is done with Visual Studio Code, though I don't like it that much, but it does the needful.
Buzzword soup
@@tensor5113 could you identify some of the buzzwords? Cause I see none.
What is WordStar?
What is Joe?
@AllanSavolainen Erm could you identify those buzzwords 🤓🤓
How's the modern vim drew neil?
I'm on nvi or vim-tiny, which is VIM but lots of stuff removed, so I'm on smaller than vanilla VIM.
I broke my arm. Good thing i know vim so i can work well even with just one hand.
Good news. Japanese scientists did experiments on humans. Even without a brain, people can use vim. It's all about muscle memory
I wonder if either of these guys has looked at amp, the vim competitor written in rust
I'm a proponent of the "distros". I've been using NvChad for a little while, but I want to try out LazyVim, because I haven't settled down yet. I like the richness, but I'm not a huge fan of over-customizing my own config. I hate choosing new keymaps. My muscle memory can learn pretty much anything, but inevitably I choose something that clashes with the default keymaps in something else I want to use and then I have to remap that and before I know it I have to remap everything in a huge chain. It's so much better to just get used to default keymaps and if everyone else does the same, usually they work together reasonably well 😅
Have you tried webi vim-essentials? (for vim, not neovim)
(it's my thing, and I'm a minimalist who wants maximum portability between computers, quickly)
Vim 8 has had native plugin support for the past 7 years (which is all we use for Webi). Just sayin'.
remember theres code oss and codium, they are literally the same as vscode without the spyware
I have a Macro on my keyboard, it does the same as Prime describes, plus some little stuff like push lines up and down.
Fear not, for I have noticed your habit of taking a drink when you want to read.
Edit: If this whole video was just you and him talking, I'd have still watched it.
I don't get this nvim elitism. Let people use whatever they're comfortable with...
People pronounce him Folkee... I'm never gonna finish learning English
That's because he's Belgian.
@@Jmcgee1125 but shouldn't it be "Folkė" with the short "e" sound?
¯\_(ツ)_/¯ idk I'm not a Belgian - I technically don't even know if they have it correct.
@@Jmcgee1125 Belgian speak french or flemish ( a sort of dutch I guess), it's definitely not french so we should ask a dutch !
I'm 90% sure the e is pronounced /œ/ (that's like the e /ɛ/ in get or set but with rounded lips) (alternatively that's like the o /ɔ/ in off or dough but with the tongue in the front of the mouth)
Guess you're not gonna be treesitting with a chainsaw. :) Now I get it.