Are IDEs really like this ?
-
The IDE is the worst part of being an iOS developer.
I legit swore off the entire OS when one of my teachers forced us to use macOS + X code to write Objective C code
-
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
-
-
This post did not contain any content.
No, no they are not.
Bad ones? Yeah, just like that.
-
- can also sometimes happen when your workplaces corporate antivirus you can't uninstall, pause, or change any settings on decides to scan your project files while a build is in progress
wrote on last edited by [email protected]Oh, you get the benefit of explicit scanning?
We get the beauty of every file that's modified
being scanned before the write "completes". It's an absolute joy starting a build and watching ~80% of the available compute be consumed by antivirus software.Or, you know, normal filesystem caching as part of your tool's workflow.
Or dependency installing and unpacking....
Or anything actually that touches a lot of files.
- can also sometimes happen when your workplaces corporate antivirus you can't uninstall, pause, or change any settings on decides to scan your project files while a build is in progress
-
Oh, you get the benefit of explicit scanning?
We get the beauty of every file that's modified
being scanned before the write "completes". It's an absolute joy starting a build and watching ~80% of the available compute be consumed by antivirus software.Or, you know, normal filesystem caching as part of your tool's workflow.
Or dependency installing and unpacking....
Or anything actually that touches a lot of files.
Yeah was experiencing that for awhile, a couple of workarounds:
- run the IDE inside a VM
- Use windows "dev drive" and got the admins to exclude it from active scanning, but it seems like that setting has been lost recently
-
So, you've never actually used Emacs?
And possibly also never used vi either?
wrote on last edited by [email protected]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?
-
Also using 10GB memory ...
wrote on last edited by [email protected]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.
-
This post did not contain any content.
Too many features but also autocomplete isn't working? So I guess you do want many features?
-
Number 3 happens all the time to me when using VSCode with Copilot as autocomplete. Copilot sometimes works, sometimes doesn't. Also happens a lot when using Pycharm with Python. Sometimes it's great at autocompleting, sometimes it completely gets lost and has no idea what my Python script is doing.
Number 5 also happens a lot on VSCode + Platformio. It also frequently happens on Intellij IDEA for me, but mostly when I am concurrently running build or test while writing. My crappy work laptop suffers from Windows 11 related performance issues, and when there's not enough performance available, underlines do get wonky quite frequently.
I also had issue when I was working on a pycharm project back when I was on windows. During setup it asked me "What's your name?" and my name has a cheeky accent which Windows was decided should be the name of my Home folder. Home folder also has appdata and whatnon so which the build system didn't expect to have a an accent in the folder path.
I ended up having to create a different folder and link to it then move all the path configurations to that folder link just so I could get imports working.
-
This post did not contain any content.
Yeah, IntelliJ has become worse over time. Or atleast Android Studio has. IntelliJ used to be amazing.
-
Sublime Text + sometimes LSP is all you need. It might be difficult for people who don't know how to use a build system directly, but those people are underachievers anyways.
Depends, for Android app dev, once you gain experience in writing code, and use Kotlin which is way less verbose, it becomes easier. But in reality, the IDE's autocompletion, syntax error highlights and other niceties do save a lot of time.
-
I just use Kate
Kate is great for being a compiled C++ program, making it nice and lightweight. Plus lots of syntax highlighting. Not quite the same as IDEs with auto completion, but pretty good for plain text editing.
-
This post did not contain any content.
This is why everyone should go back to ed
-
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.
-
Kate is great for being a compiled C++ program, making it nice and lightweight. Plus lots of syntax highlighting. Not quite the same as IDEs with auto completion, but pretty good for plain text editing.
It can give autocompletion based on the current file, which is good for writing self contained classes. You can also enable an LSP to get language autocompletion
-
Yeah, IntelliJ has become worse over time. Or atleast Android Studio has. IntelliJ used to be amazing.
IntelliJ now requires like 8GiB of RAM to even open.
-
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.
wrote on last edited by [email protected]We're not 20 years in the past, old man.
-
We're not 20 years in the past, old man.
I know, back then people knew what files and directories were. Good times.
-
I know, back then people knew what files and directories were. Good times.
wrote on last edited by [email protected]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.
-
This post did not contain any content.
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.
