So I adopted a mentality from bash of "do one thing well" I would rather use single tools that are really good at what they are trying to do than use one tool that does a lot of things but not very well, another aspect is that tools should have good integration layers so it's easy to connect them together, just my 2 cents though. All the best, Scott
Gentoo Linux and VIM worshiper, C developer, network protocol dissector implementer,socket/network programmer, recently entered the embedded world, hater of buzzwords and made up titles
Totally agree, we share a similar mindset; I use Vim with some plugins and do compiling and debugging manually. Never been a fan of all-in-one solutions like IDEs.
This is how I work these days:
Damir Franusic
@vimmer9
@MasteringVim@turnoff_us Couple of years ago.. actually like 12..my first reaction to #vim was "man, I need like extra set of hands and maybe an extra hind-brain to master this"... ffd to present day and I can't exit 😂.. and not because I don't know how lol
10:26 AM - 13 Jul 2019
0
2
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
So I adopted a mentality from bash of "do one thing well" I would rather use single tools that are really good at what they are trying to do than use one tool that does a lot of things but not very well, another aspect is that tools should have good integration layers so it's easy to connect them together, just my 2 cents though. All the best, Scott
Totally agree, we share a similar mindset; I use Vim with some plugins and do compiling and debugging manually. Never been a fan of all-in-one solutions like IDEs.
This is how I work these days: