top 50 comments

sorted by: hot top controversial new old
[–] 47 points 1 year ago (1 child)

Before I started reading the meme I actually thought "just use Notepad++".

  • source
  • hideshow 1 child comment
  • [–] 15 points 1 year ago*

    I can't live without VIM keybinds. Maybe I'm a boomer. I do use it as a note taking or "collect my thoughts" app. Or just a place to paste shit when I'm working. Very useful for that. Though only when I'm forced to be on Windows.

  • source
  • parent
  • [–] 37 points 1 year ago (2 children)

    Also using 10GB memory ...

  • source
  • hideshow 2 child comments
  • [–] 3 points 1 year ago*

    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.

  • source
  • parent
  • [–] 37 points 1 year ago* (last edited 1 year ago) (1 child)

    I've had everything on this list with Visual Studio alone, with the exception of #2 maybe.

    1. 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.

    2. This happens every other day when working with Blazor. As an added bonus, it can never decide on spacing and will constantly change it.

    3. 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.

    4. Another symptom of blazor.

    5. Our project is too big.

  • source
  • hideshow 1 child comment
  • [–] 25 points 1 year ago (5 children)

    Just use vim, it usually comes preinstalled

  • source
  • hideshow 5 child comments
  • [–] 10 points 1 year ago* (last edited 1 year ago)

    Unless you need to work on a solution with more than a few projects, such as Unity games. Then the LSPs go haywire and eat 20+Gb of memory, while not actually working.

    Which, ofc, is Microsoft's fault, since it's their analyzer that has had the bug for years now. Rider didn't have that problem, but it shits itself when you change branches. You can't win :(

  • source
  • parent
  • [–] 7 points 1 year ago (1 child)

    For a few files, sure. Idk how I'd use that on the large corporate Java codebase that I usually work with though. Despite all its memory hogging and unnecessary features, IntelliJ also proves remarkably useful when trying to find anything in these mega projects. Features like ctrl + clicking on a method call to get to its definition (even when it is in a different project that I don't have checked out), the refactoring tools, the debugger, etc are absolutely necessary to get anything done.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 23 points 1 year ago (2 children)

    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.

  • source
  • hideshow 2 child comments
  • [–] 10 points 1 year ago (1 child)

    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:

    1. It is plugin-based

    2. 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.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 1 year ago

    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

  • source
  • parent
  • [–] 20 points 1 year ago
    [–] 18 points 1 year ago (7 children)

    I use Jetbrains IDEs now for 5 years, I've used VSCode, Sublime, Atom, Vim, Neovim but I feel like Jetbrains IDEs are just better if you have the RAM to run it.

    1. It's a setting.
    2. Doesn't happen
    3. Doesn't happen
    4. Searchable actions, just search for "encoding" in this case.
    5. That's an LSP/project mismatch usually just a setting. Most things are supported but worst case you can remove the error.
    6. Happens if you run out of RAM or open a very large file.

    So it's not all bad, but comes with a lot of good such as "invert if statement", "use template strings" and "extract method" thingies along with a load of plugins.

  • source
  • hideshow 7 child comments
  • [–] 4 points 1 year ago* (2 children)
    1. 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 🤦🤦🤦
  • source
  • parent
  • hideshow 2 child comments
  • [–] 4 points 1 year ago* (1 child)

    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.

  • source
  • parent
  • hideshow 1 child comment
  • load more comments (1 reply)
  • [–] 3 points 1 year ago*

    Agree. I used a ton of different IDEs too and I can say Rider was the least terrible one I've used professionally (mostly on Unreal Engine projects, so having the thing not kill itself when trying to compute large, complex codebases for syntax highlighting/autocomplete was a requirement).

  • source
  • parent
  • load more comments (2 replies)
    [–] 15 points 1 year ago (2 children)
    load more comments (2 replies)
    [+] 13 points 1 year ago* (last edited 2 months ago) (3 children)
  • [–] 11 points 1 year ago* (2 children)

    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.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 12 points 1 year ago

    Definitely #1. I've encountered #2 with a very specific IDE and #4 and #5 on occasion.

  • source
  • [–] 9 points 1 year ago (4 children)

    The IDE is the worst part of being an iOS developer.

  • source
  • hideshow 4 child comments
  • [–] 5 points 1 year ago* (2 children)

    Yes, and the worst part is that XCode is only available on OSX.

    I once had to make an iOS app once and didn't have a Mac so I developed the entire thing in a VM. There was no video encoding, the FPS was in the low single digits, which made it very difficult to even type. So I ended up writing the code using VSCode through SSH through Wireguard connected to the VM on the host machine, which actually worked surprisingly well. But hey, the app did work in the end.

  • source
  • parent
  • hideshow 2 child comments
  • load more comments (2 replies)
  • [–] 8 points 1 year ago

    No, no they are not.

    Bad ones? Yeah, just like that.

  • source
  • [–] 7 points 1 year ago

    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.)

  • source
  • [–] 6 points 1 year ago (1 child)

    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.

  • source
  • hideshow 1 child comment
  • load more comments (1 reply)
    [–] 5 points 1 year ago (3 children)

    I mainly code Java with IntelliJ.

    • it doesn't AFAIK have an integrated browser or if it does I have never encountered it ❌
    • I have not seen it crash a lot and certainly not for the stated reason ❌
    • if autocomplete isn't working, that is a sign something about the build process isn't set up right, so other things won't work either ❔
    • basic settings being buried deep in the menus is definitely a thing ✅
    • if it underlines something, that has always been an error, I think it calls a real Java compiler for this ❌
    • freezing at critical moments can occasionally be a thing ✅
  • source
  • hideshow 3 child comments
  • [–] 8 points 1 year ago*

    basic settings being buried deep in the menus is definitely a thing ✅

    Nah, there is:

    1. A special hotkey that allows you to find and execute virtually any command. Same in vscode with ctrl+shift+p.
    2. Text-based search in the settings dialog.

    So even though things are buried somewhere deep, it's easy to find them.

    freezing at critical moments can occasionally be a thing ✅

    Sounds like a skill hardware issue tbh.

  • source
  • parent
  • [–] 5 points 1 year ago* (last edited 1 year ago) (1 child)

    #1 and 3, definitely, although 3 is usually not really the IDEs fault.

    The others, either not really (#2, 5), who cares, (#4), or maybe occasionally but not really specific to IDEs (#6).

  • source
  • hideshow 1 child comment
  • None of those issues for my main IDE, though Rider on some occasions do get stuck marking some spelling errors after they are fixed.

    It has stuttered a few times, but pretty rare. But it does have a bug where it think it is building a project, but isn't. And requires a restart to fix... Easy to trigger if you try building a project while it's loading the project...

    Visual Stuido with Resharper is the one where things would randomly stop working though. Especially hotkeys would sometimes stop working until I restarted it. Slow and stutter too.

  • source
  • [–] 4 points 1 year ago

    At least the number of times I have to use the Clean Java Language Workspace in VS Code has declined recently. I mean, I still have to, just not as often.

  • source
  • [–] 4 points 1 year ago (2 children)

    Yeah, IntelliJ has become worse over time. Or atleast Android Studio has. IntelliJ used to be amazing.

  • source
  • hideshow 2 child comments
  • load more comments (2 replies)

    Neovim >>> any ide

  • source
  • [–] 3 points 1 year ago

    The IDEs of March

  • source
  • [–] 3 points 1 year ago

    I'd argue the benefits outweigh the downsides

  • source
  • [+] 2 points 1 year ago* (last edited 1 year ago)
    load more comments
    view more: next ›