• Tramort@programming.dev
      link
      fedilink
      arrow-up
      8
      ·
      2 months ago

      Oh my God. That’s awful.

      Thanks for posting about jet brains coopting and closing the rust plug-in. Yuck!

  • masterspace@lemmy.ca
    link
    fedilink
    English
    arrow-up
    18
    arrow-down
    5
    ·
    2 months ago

    VSCode & VSCodium are also free for commercial use.

    Why learn an IDE you won’t use anywhere else?

    • ADTJ@feddit.uk
      link
      fedilink
      arrow-up
      7
      ·
      2 months ago

      C# Devkit will do in a pinch but it’s still second class in VS Code compared to languages like TypeScript.

      Since MS killed off MonoDevelop and Visual Studio is Windows only, it’ll be good to finally have a free proper C# IDE again on Linux.

    • CodeMonkey@programming.dev
      link
      fedilink
      arrow-up
      7
      arrow-down
      3
      ·
      2 months ago

      Why would you use a library or framework when you can code everything from scratch? It probably depends on how good the VSCode extension is vs how bad the IDE is.

      For the languages I have tried (mostly GoLang plus a bit of Terraform/Terragrunt), VSCode plugins can do code highlighting, can highlight syntax and lint errors, can navigate to a methods implementation, the auto-complete seems to pick random words from the code base, and can find the callers for a method. It is good enough for every day use.

      IDEs I have used (Eclipse for Java, PyCharm, InteliJ for Kotlin) offer more. They all have starter templates for common file types. The auto-complete is much more syntax aware and can sometimes guess what variables I intend to pass in as arguments. There is refactoring which can correctly find other usages of a variable and can make trivial code rewrites. There are generators for boilerplate methods. They all have a built in graphical debugger and a test runner.

    • Rogue@feddit.uk
      link
      fedilink
      arrow-up
      2
      ·
      2 months ago

      Jetbrains licenses are like £100 a year. What commercial project isn’t able to cover that cost.

      • EowynCarter@lemm.ee
        link
        fedilink
        arrow-up
        2
        ·
        2 months ago

        I’m just hopping the price won’t rise in return.

        Yet I’m not going back to eclipse.

        • Rogue@feddit.uk
          link
          fedilink
          arrow-up
          1
          ·
          2 months ago

          They give incremental discounts each time you renew so even if the price increases you’ll probably find you’re spending less each time.

          • EowynCarter@lemm.ee
            link
            fedilink
            arrow-up
            2
            ·
            2 months ago

            I’ve been on the lower price forever as I had a licence from before the switch.

            It’s already expensive. And having a comercial option that is affordable for normal people rather than $$$ entreprise would be good. Quitte a few paying of their own because their entreprise won’t.

        • zlatko@programming.dev
          link
          fedilink
          arrow-up
          1
          ·
          2 months ago

          I would expect it to rise. I still think it’s worth it, if it’s a good tool for you. IntelliJ is really a good product, even if they do have their downsides. In a commercial environment, it’s totally worth it to buy a licence per developer, if it makes them more productive.

    • TJA!@sh.itjust.works
      link
      fedilink
      arrow-up
      0
      ·
      edit-2
      2 months ago

      I am kind of using intellij ideas for everything. They are just so much better.

      I don’t think I would want to work for an employer that is too cheap for an IDE license

  • thepiguy@lemmy.ml
    link
    fedilink
    arrow-up
    8
    ·
    2 months ago

    This is great. Rider pretty much carried me through my first year at uni, considering that visual studio does not work on Linux. The neovim plugin for C# that I used kept crashing for me, glad to see non students also getting a chance to try out this software.

    • JakenVeina@lemm.ee
      link
      fedilink
      English
      arrow-up
      2
      ·
      2 months ago

      I suspect this is because of the looming end of Windows 10. There’s a large segment of Windows users, myself included, with Visual Studio being the only remaining tie to the Windows ecosystem. Extremely smart move by JetBrains, if true.

  • moreeni@lemm.ee
    link
    fedilink
    arrow-up
    2
    arrow-down
    14
    ·
    2 months ago

    I am yet to meet someone who doesn’t use VSCode for web development.

    • TxzK@lemmy.zip
      link
      fedilink
      arrow-up
      14
      ·
      2 months ago

      I know plenty of people that use vim/neovim for web development. I am also one of them

      • moreeni@lemm.ee
        link
        fedilink
        arrow-up
        2
        ·
        2 months ago

        Woah, that’s pretty cool! i installed an extension for vim keybindings inside VS Code recently, as I find them very powerful. Unfortunately, I rely on VSC’s plugin ecosystem and thus can’t fully switch over to neovim, but I’ve liked it so far for everything else I do on my system, like writing bash scripts.

        • MajorHavoc@programming.dev
          link
          fedilink
          arrow-up
          2
          ·
          edit-2
          2 months ago

          If you’re feeling bold, check out the NeoVim VSCode plugin. It’s delightful.

          It’s essentially the VSCode remote plugin, but connecting to the NeoVim back-end.

          It gives all the functionality of NeoVim along with all the functionality of VSCode.

          Also, annecdotaly, it’s substantially faster than the VSVim plugin.

          • moreeni@lemm.ee
            link
            fedilink
            arrow-up
            2
            ·
            2 months ago

            I’ve had issues with that one because I’m using VS Codium flatpak. I’ve exposed system binaries and the extension found the nvim binary, yet it kept erroring out with the message that Nvim was disconnected. VSVim is better in that regard for my case, because it is a stand-alone extension.

            • MajorHavoc@programming.dev
              link
              fedilink
              arrow-up
              2
              ·
              edit-2
              2 months ago

              I saw an error like that, too. (Also with the flatpak.)

              I want to say I had an error in my init.vim that was the underlying cause, and the error message cleared up once I had that fixed. I also had to make sure both executables were on my path, and I had to correct where the NeoVim plugin was looking for Nvim, as well, in settings.json.

              • moreeni@lemm.ee
                link
                fedilink
                arrow-up
                2
                ·
                edit-2
                2 months ago

                I didn’t have any errors in the init.vim file because I didn’t have any. I added an example init.lua file with contents from here and configured the extension to pull this config file, yet it still says Nvim disconnected each time I restart it. I just gave up and resorted to VSVim

                • MajorHavoc@programming.dev
                  link
                  fedilink
                  arrow-up
                  3
                  ·
                  2 months ago

                  That makes sense. Did you also set the path to Nvim in settings.json? I had to do so to clear at least one error.

                  I also sometimes get that “disconnected” error too, but the have it work fine. I think there’s a race condition and it raises the error right after it starts, but then connects anyway, once everything else is set.

      • lysdexic@programming.dev
        link
        fedilink
        English
        arrow-up
        1
        arrow-down
        3
        ·
        2 months ago

        You’ve never met an average ASP.NET developer?

        OP is right. For web development with JavaScript frameworks (React, Angular, etc) with Node and even Typescript, you either use vscode or you haven’t discovered vscode yet.