this post was submitted on 29 Jun 2024
45 points (92.5% liked)

Learn Programming

1625 readers
1 users here now

Posting Etiquette

  1. Ask the main part of your question in the title. This should be concise but informative.

  2. Provide everything up front. Don't make people fish for more details in the comments. Provide background information and examples.

  3. Be present for follow up questions. Don't ask for help and run away. Stick around to answer questions and provide more details.

  4. Ask about the problem you're trying to solve. Don't focus too much on debugging your exact solution, as you may be going down the wrong path. Include as much information as you can about what you ultimately are trying to achieve. See more on this here: https://xyproblem.info/

Icon base by Delapouite under CC BY 3.0 with modifications to add a gradient

founded 1 year ago
MODERATORS
 

The project home page.

The Github

Looks just like VS Code and I think it's still built on electron so take that as you will.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] Xabis@lemmy.world 2 points 4 months ago (1 children)

I use vs code for programming a node based application written in Typescript.

The only thing I find insufficient is the source control integration. Editing and debugging are well done in my opinion, at least for my target language.

What do you find lacking that you feel makes it not a worthy ide?

[โ€“] orclev@lemmy.world 3 points 4 months ago

Most of the tools that make an IDE an IDE. Refactoring abilities are very limited and basic. Quickly navigating complex code bases becomes tricky. The code completion and type annotations are often missing or just plain wrong. When compared to something like essentially any IDE offered by JetBrains it just doesn't stack up. Prior to RustRover being released I briefly tried to use VS Code for Rust using its LSP plugin, but it was just really bad in general, it utterly failed to analyze the code and provided almost no contextual help.