- cross-posted to:
- comicstrips@lemmy.world
- cross-posted to:
- comicstrips@lemmy.world
I’ve had everything on this list with Visual Studio alone, with the exception of #2 maybe.
-
All the AI shit they’re adding, plus the millions of windows you can pull up that are all hidden in different places. The only way this is remotely usable is with the search.
-
This happens every other day when working with Blazor. As an added bonus, it can never decide on spacing and will constantly change it.
-
Probably a symptom of using legacy code and modern code at the same time, but good god the settings for everything are in a million places.
-
Another symptom of blazor.
-
Our project is too big.
You should refer to Visual Studio by its full title: “Visual Studio (not responding)”.
-
VSCode is the first development environment I’ve used that doesn’t make me feel like this. It’s not perfect but the base application is rock solid and the full DE experience is the more reliable than any other DE I’ve used.
P.S. I specifically said DE for those people who say VSCode isn’t an IDE. Personally I don’t see the point in differentiating.
P.P.S. Sublime is not a DE in my opinion. It’s an excellent text editor with syntax highlighting. The plugins were an afterthought and it was never intended to provide the full experience. Granted I haven’t used it in years.
VSCode is by far and away the best thing Microsoft has ever done. (I’m sure therefore they will ruin it eventually, but that’s a separate issue)
Its good for two main reasons IMO:
-
It is plugin-based
-
It is (therefore) language-agnostic
Plugins mean the DE starts as a very lightweight thing that is basically nothing more than a text editor. You can then add as much or as little as you want to get the level of features you are comfortable with but without being too bloated.
And then, because it’s all plugins, you can work with any language and still stay within the same editor. Divine.
I personally love how lightweight it is compared to a full IDE because I don’t like it when IDEs hide the magic behind UI. Press the button and it compiles huh? But how? What’s going on there? What toolchain and commands are being executed?
I much prefer a good MAKEFILE where you know what your entry points are and what is going on, because it makes everything so much more portable and also improves your own knowledge and understanding.
Yeah it’s great because even without a make plugin, you can just add your make command to the vscode actions that’ll run your makefile.
Or even better, get the plugin which will auto populate targets from the makefile lol
-
Meanwhile: vim and Emacs users, constantly installing and configuring plugins to emulate a fraction of the power of IDEs, go “just use vim/Emacs”.
Easymotion is the only plugin I need to be happy.
So, you’ve never actually used Emacs?
And possibly also never used vi either?
LOL. Let me guess “just use Emacs/vim”?
No thank you bruv. Been there, done that. Terrible experience.
https://github.com/emacs-tw/awesome-emacs
https://github.com/lunarvim/lunarvim
All of these emulated only a fraction of the power of IDEs, even after weeks of trying to get them configured properly.
Inb4 “you’re doing it wrong”. Nah mate, IDEs work out of the box and don’t require opening a text file to change settings while going through reams of documentation.
I right click in a file and it shows me the most important contextual commands. No need to find the " leader key", scroll through all the 1 billion commands, I don’t have to “download a LSP and DAP” then “configure treesitter” or whatever the fuck kind of apes are in the editor.
Those editors have steep learning curves and get you productive eventually. IDEs get you there much more quickly. Yeah yeah, they hide complexity and “people don’t know what’s actually going on anymore” but sometimes I just want to get going instead of fighting my editor first. Feel me?
All those wondrous IDEs were nowhere to be found 20 years ago, especially if you didn’t run windows. While Emacs did it all and more.
So yes, you had to read the documentation. That’s what we did back then. We still do it when someone can be arsed to write one.
We’re not 20 years in the past, old man.
I know, back then people knew what files and directories were. Good times.
That knowledge is gone. Everything is a web app running JavaScript in a browser. We don’t need to be encumbered by pesky things like pages and folders. 😋
I only use nerdtree, and bind some scripts to F-keys. Haven’t updated in a couple years, just works.
What is that hyperlink?
I swear to God if it is what I think it is, I’m going to jump into fucking traffic carrying as many baby ducks as I can.
What do you think it is?
It looks like they put a license of use on their comment
All of those are things that have happened to me (except an IDE that could not handle externally edited files). They are very rare occurrences, but still annoying when I have to get something done.
Also using 10GB memory …
Hah, per window.
When I started working for my current employer, I was surprised by how much ram my VDI has. We’re not allowed to code on our own devices (but those are still specced out) but 64 Gs of ram in a virtual desktop was a welcome environment to work in.
I’d argue the benefits outweigh the downsides
XCode would randomly stop syntax highlighting for years because their engineering was so shit.
In the JetBrains IDEs (which, relatively speaking, I like), I have to use “Invalidate caches and restart” several times a day just to get past all the incorrect error highlighting.
Ah, is that the way to address that? I don’t run into incorrect error highlighting often, and it’s mostly great, but when it gets it wrong, it can be very stubborn about it.
It usually works, but it takes a few minutes to reprocess the files if your project or solution is big.
Obligatory XKCD https://xkcd.com/378/
Definitely #1. I’ve encountered #2 with a very specific IDE and #4 and #5 on occasion.
The IDEs of March
This is why everyone should go back to ed
I just code in Notepad++. I make an error, I fix it. It doesn’t work, I just dump variables to see what I did wrong and where.
No, no they are not.
Bad ones? Yeah, just like that.
Too many features but also autocomplete isn’t working? So I guess you do want many features?
It’s almost enough to make me feel nostalgic for the DOS version of Borland Turbo Pascal, which wasn’t bright enough to do any of this stuff. (Well, it could freeze up, I suppose, but the only time I actually managed to do anything like that, it involved a null pointer dereference that would have triggered a segfault on any modern system.)