/tech/ - Technology★

terminals are terrible for complex text editing but this place is all about doing things the hard way so people shill things like vi

>>1059548 (OP)

>>1059550

Liar. Both Vi and Emacs are superior to your (((visual code))) bloated shit.

>>1059552

Its only bloat if you're working on single file projects

> Don't know shit about programming

> Can't code for shit

> Grab an IDE with good completion

> Suddenly can program because because never discovered program design or proper documentation, and an editor that autofills these things makes you actually functional

Durr. IDEs are a little more productive for experts. They are way more productive for beginners. Experts can quickly discern structure and break program flow down without much help, so IDEs mostly save typing. Beginners (and junior developers) are much more productive because they can't as quickly grok code structure or utilize documentation (and memorize the most commonly-used utilities).

For an expert, a properly-configured Emacs or Vim is just about as productive as a more fully-featured IDE (maybe a little less productive, but often far more comfortable to use, so it's a worthwhile tradeoff). Any beginner should be using an IDE for a while until they are more fluid in programming.

I might have respected what you said if you didn't post that visual pic and oust yourself as a blatent troll.

On to a more realistic discussion, for a beginner to intermediate writing python and c, would you choose geany or eclipse?

>>1059558

>for a beginner to intermediate writing python and c, would you choose geany or eclipse

Geany is a good editor, and Eclipse is a serviceable IDE, but Thonny is far better for light Python use and has really good integration with debuggers, variable inspection, AST inspection, and some other features. I haven't used a whole lot of Python IDEs, but I started using Thonny because I needed something powerful but accessible to tutor a friend in Python, and I'm impressed by how well it does.

For C, I use Vim with YouCompleteMe and it works well enough. It really depends what you want out of your editor.

>"If I cant do anything meaningful in $TEXT_EDITOR, no one can"

Cheap troll aside, I'm interested in this "psychological impact of using X piece of software" bit. There should be some studies about this.

>>1059557

Also IDEs help with errors and warnings. They will usually highlight the line(s) with erroneous code and state what the problem is in a more user-friendly way than GCC or Clang do.

>>1059548 (OP)

PyCharm or bust

I use Vim because it works for me.

Any text editor is good, as long as you don't cry about others using something else all the time. Grow up.

>>1059567

>PyCharm

A really fantastic IDE for Python.

>>1059560

>For C, I use Vim with YouCompleteMe and it works well enough.

I found YouCompleteMe to be quite a hassle to work with. I prefer a Language Server Protocol plugin with Clangd as the server. Plus you can use LSP with other language as well.

>>1059565

You don't need an IDE for that. A text editor can have a "compile" command or button (Vim has ':make'), parse the output of the compiler and show the errors to the user. The advantage of the text editor is that you can set the error format for each file type and thus get error integration for any language you want instead of just the ones the IDE supports.

>>1059568

>Any text editor is good, as long as you don't cry about others using something else all the time.

This. Of course that is if you use an editor. An IDE locks you into its workflow, the entire build process is locked inside opaque "project" files, making collaboration with people who don't use the same version of the same IDE impossible

>>1059587

YouCompleteMe has been a LSP client for a bit over a year, but LSP isn't perfect. One of the maintainers of YouCompleteMe wrote a big write-up of LSP's issues: https://archive.fo/myDyn

> You don't need an IDE for that. A text editor can have a "compile" command or button (Vim has ':make'), parse the output of the compiler and show the errors to the user

That's true, but far less useful than getting yellow lines on warnings as you type/edit and resolving them as you go.

>>1059565

> They will usually highlight the line(s) with erroneous code and state what the problem is in a more user-friendly way than GCC or Clang do.

Where exactly do you think the hints for what's wrong come from? Vim's deoplete-clangx does the same thing.

>>1059600

>Clangd

I think you mean systemd-clangd

Also IDE vs editor is like MS office vs latex

>>1059616

> clangd

> actually having to use a bloated build system like cmake because of compile_commands.json

No thanks. LSP Is overrated garbage.

>>1059548 (OP)

imagine bragging about bragging about writing a lot of code

people like you are the problem

>>1059560

This thread is sinking fast but I just wanted to say, Thonny is great, thanks.

>>1059548 (OP)

>use vscode for eight years

>never produced anything of value

>switched to nvim

>overnight I managed to create a sapient AI

<come at me bitches. Prove me wrong!

See how this works, OP?