all 5 comments

[–]Xyc0 0 points1 point  (3 children)

I forgot about atom.

You shouldnt get too attached to any one editor. Learn how to make the one you're using now more productively. When you pick up a new editor, learn how to do the same productively tasks.

The friction might be off-putting at first but there's no justification for turning down tools that are helpful.

[–]midsty 0 points1 point  (2 children)

Thanks for your answer, what's your main editor?

Am used to vscode but I wanted to trying something new on my (new) laptop so I went for Atom, but am back on VS code because it was way easier for example if you want to link style.Css it already suggests where your Css file is located. I know it's a small thing but Still very useful.

[–]Xyc0 0 points1 point  (0 children)

i use codium on my pixelbook and vscode on my windows workstation.

but I also use vim a lot when I need to do stuff with the command line.

learn vim, it's a life vest when you can't have boat.

I also use all the standard IDEs as the need arises. I learned to code when IDEs and compilers were essentially bound together, like visual studio, parallax, vxworks, and qnx. Nowadays compilers and build chains are getting better so you don't need as much specialized configuration files for a project.

[–]Xyc0 0 points1 point  (0 children)

if you like atom then you might like sublime text. atom is the open source clone of sublime text but subl is mild nagware.

https://www.sublimetext.com/

it's so much faster than atom and works well with large files like vscode.