Are IDEs really like this ?
-
Can someone tell me if I'm just stupid and doing something wrong ?
Neovim with Python lsp works 90000% better than any Python extension on vscode for me. I don't hate vscode and I occasionally use it but it kind of sucks for python ? Does anyone have any kind of info that could help, what extensions are you using ?
-
Can someone tell me if I'm just stupid and doing something wrong ?
Neovim with Python lsp works 90000% better than any Python extension on vscode for me. I don't hate vscode and I occasionally use it but it kind of sucks for python ? Does anyone have any kind of info that could help, what extensions are you using ?
vscode isn't an ide either. one of the big problems i've seen with its python lsp server is that it doesn't work if the project structure is "wrong", which means that usability is limited.
-
I do all my edits using sed inserts, like a real dev.
Just use
edlike the gods intended -
Oh I don't know. 1,3,5 and 6 resonate strongly with me for Visual Studio 2022. The only reason 4 doesn't is because instead of looking for a setting I DDG "how do I do X in VS2022"
-
Just use
edlike the gods intendedI use butterflies
-
Pfff, all these amateurs here using Vim. Y'all should use Emacs. You still have all of these problems, but you get to act all superior about it. /s (except for the superiority complex; that's real)
-
vim evangelists incoming although they are on panel 3
Well, my autocompletes works fine but I thinks it's a lot thanks to vscode, which seems to have pushed LSP.
-
Install the right plugin and IntelliJ will act like Eclipse ten years ago. Bonus points for the plugin being a mandatory part of your company's work flow with no alternatives other than a command line nobody can help you with.
-
Just use
edlike the gods intendedWhat about Edd and Eddy?
-
modern IDEs are dog shit. If I needed a glorified clippy telling me how to do my job I'd smash my brains out all over my keyboard.
Give me an editor with the following and I'll be good for life.
- syntax highlighting/error flagging
- project scoping
- script injection
- ftp/scp
nice to have:
- db viewer (SQL/sqlite)
- json viewer
- diff
- git/vcs
if an editor can do all that I can make it do whatever I need.
-
That is a pretty good way to look at it.
-
One doesn't know how to code if they cannot spell the whole word.
(Turn off autocomplete for a day and test your actual knowledge.)
Nah thanks, I want to program by solving logic problems, not syntax problems.
-
Actually Clion is prone to eating all your RAM randomly. It's Java after all.
Java can only eat RAM up to a limit. So while it is memory hungry, it won't be randomly "eating all your RAM". Rather, more predictably it'll eat a lot more of your RAM than you'd like.
-
Are you even a real programmer if you haven't fixed a prod critical but in notepad++ because your ide won't open for whatever reason?
I've lost track of the number of Report Builder files I've had to update via Notepad++ - the intended editor has so many weird kinks and corner cases it's often easier to just edit the file directly!
-
Pfff, all these amateurs here using Vim. Y'all should use Emacs. You still have all of these problems, but you get to act all superior about it. /s (except for the superiority complex; that's real)
I use Emacs honestly just because it’s more FUN for me. It’s such an open book internally that when things break, I find I can usually figure it out. There aren’t that many environments that really feel that way. I get that it’s not everybody’s cup of tea, but man am I glad to have it.
-
modern IDEs are dog shit. If I needed a glorified clippy telling me how to do my job I'd smash my brains out all over my keyboard.
Give me an editor with the following and I'll be good for life.
- syntax highlighting/error flagging
- project scoping
- script injection
- ftp/scp
nice to have:
- db viewer (SQL/sqlite)
- json viewer
- diff
- git/vcs
if an editor can do all that I can make it do whatever I need.
I had similar opinion, but I’ve changed my mind. Now I can barely do any serious work without an IDE.
The main feature I’m after is code completion. Just getting a peek of which methods are available is something I can’t be without.
Code hints like ”this expression will always evaluate to false” is great to capture difficult to spot mistakes.
Code usage it’s is a must when doing refactors. It makes it easy to analyze how a method is used before I commit to a refactor.
Debugger and profiler is also nice to have.
-
Something something, use Linux.
-
I know you joke but topheavy IDEs are discouraging new coders at an alarming rate
-
I hate how IDEs with error checking check the code at every character. Like my dude, we got this shit right with text editors having spell check back in 1997. Wait just a moment before checking please. All the time when I'm typing the editor freaks the fuck out, this is wrong, this is wrong, here is an error, wtf is this supposed to mean? And then when I type the ) or whatever, all is well. Just give me a freaking second to work and think.
You can thank search engines on mobile for that, pure idiocy
-
I had similar opinion, but I’ve changed my mind. Now I can barely do any serious work without an IDE.
The main feature I’m after is code completion. Just getting a peek of which methods are available is something I can’t be without.
Code hints like ”this expression will always evaluate to false” is great to capture difficult to spot mistakes.
Code usage it’s is a must when doing refactors. It makes it easy to analyze how a method is used before I commit to a refactor.
Debugger and profiler is also nice to have.
I'd say that's true for most devs.
personally though, all that is noise to me and is difficult to maintain focus when it's got all these popups and autofills.
I'm currently maintaining a codebase that's got something like 900 methods/functions across multiple classes, modules, and other objects. It follows a pattern and is pretty easy to maintain though.
another project I'm inheriting is doesn't have any logical flow or pattern and is a shitstorm of JS Christmas trees. I'll likely need to used something that will trace through the callbacks just to see what the fuck is going on.
my point though, is if you depend on the tools that make it easy to write sloppy code, you will write sloppy code because the key feature of the tool allows you to do it without repercussions.
building something without effort rarely ends with a result you can be proud of. this is true for development and in life, IMO.
