Pycharm is great for python development, but can feel sometimes slow and community version has Somme very annoying restrictions (like they disabled jupyter notebooks plugin and made it premium feature). I personally started looking into VS Code as an alternative, and it has some very good potential. I suggest you take it into account.

The Community version of PyCharm is free and should give you what you need to get started with Python. Both PyCharm and IntelliJ are made by JetBrains. IntelliJ is initially focused on Java but you can get plugins for lots of other things. I subscribe to JetBrains' Toolbox: https://www.jetbrains.com/toolbox-app/ and have access to all of their great tools.

Hi, I will give my opinion based on my experience. I have used PyCharm, both community and Professional version. The community has limited functions, like you can't use a Jupyter notebook whereas it's available in the Professional version. PyCharm is slower compared to Visual Studio Code. Also Visual Studio Code is an editor which supports various languages. I myself have used both Visual Studio Code and PyCharm. I feel Visual Studio Code would be better choice. You may as well decide based upon your requirements.

I couldn't imagine using a development tool other than the IntelliJ IDEA Ultimate All Products Pack. A single license allows me to work directly on my server running Ubuntu and/or my workstation running Windows 10 Pro simultaneously. My current project uses HTML, W3CSS, JavaScript, Java, Groovy, Grails, C, GO, Python, Flask, and Rust. For me it's worth every penny of the $150 license fee. And you can try it for free.

Visual Studio code is easy to use, has a good UI, and a large community. Python works great with it, but unlike some other editors, it works with most languages either by default or by downloading a plugin. VS Code has built in linting, syntax coloring, autocompletes (IntelliSense), and an api for plugins to do there own tooling.

I'd personally recommend Visual Studio Code as it gives you the flexibility of working in any language, so long as there are extensions to support it. It gives you the flexibility to learn Python, venture into Java, Javascript, and eventually AngularJS, and potentially mobile applications. It's also free and you can install it on your personal computer. I think Visual Studio Code would serve your intended use case best.

IntelliJ really is the best for Java, I switched from eclipse years ago and never looked back. As for javascript, python and angular either using the standalone products from jetbrains (pycharm for python, webstorm for js) or installing the relevant plugins for InteliJ will be your best bet. Pycharm etc. are really just InteliJ with some additional plugins installed.

If you starting with Python then PyCharm is better. For Java I would suggest to go with IntelliJ IDEA but people also prefer eclipse so I would say try both and then decide. For JS/Angular/React I would suggest go with VSCode. I personally use it and prefer as its light weight and have good integration with chrome for frontend development.

PyCharm, IntelliJ IDEA are both products of JetBrains. They have a free (limited feature) and paid edition. Eclipse is free. VSCode is also free.

Easy to learn and everything you need

This is a very easy to use tool and gives you the opportunity to start coding right after the installation with almost everything setup automatically by the tool.

All three are great, however, I believe that IntelliJ IDEA's multiple IDE's are slightly more straight-forward and more up-to date than Eclipse. If I had to choose one specifically for Python projects I would go with PyCharm.

Pycharm is all you need to get start coding in python or any of its framework. Its an awesome tool you should give it a try :)

We use Yarn because it allows us to more simply manage our node_modules. It also simplifies commands and increases speed when installing modules. Our teams module download time was cut in half after switching from NPM to Yarn. We now require all employees to use Yarn (to prevent errors with package-lock.json and yarn.lock).

I use npm since new version is pretty fast as well (Yarn may be still faster a bit but the difference isn't huge). No need for other dependency and mainly Yarn sometimes do not work. Sometimes when I want to install project dependencies I got error using Yarn but with npm everything is installed correctly.

p.s.

I am not sure about the performance of the latest version of npm, whether it is different from my understanding of it below. Because I use npm very rarely when I had the following knowledge.

------⏬

I use Yarn because, first, yarn is the first tool to lock the version. Second, although npm also supports the lock version, when you use npm to lock the version, and then use package-lock.json on other systems, package-lock.json Will be modified. You understand what I mean, when you deploy projects based on Git...

I use npm because I also mainly use React and TypeScript. Since several typings (from DefinitelyTyped) depend on the React typings, Yarn tends to mess up which leads to duplicate libraries present (different versions of the same type definition), which hinders the Typescript compiler. Npm always resolves to a single version per transitive dependency. At least that's my experience with both.

As far as I know Yarn is a super module of NPM. But it still needs npm to run.

Yarn was developed by Facebook's guys to fix some npm issues and performance.

If you use the last version of npm most of this problem does not exist anymore.

You can choose the option which makes you more confortable. I like using yarn because I'm used to it.

In the end the packages will be the same. Just try both and choose the one you feel more confortable. :)

I am a minimalist too. I once had issues with installing Nuxt.js using NPM so I had to install Yarn but I also found that the Dev experience was much better

I use npm because its packaged with node installation and handles npm tokens in CI/CD tools for private packages/libraries.

I use npm because it has a lot of community support and the performance difference with alternative tool is not so significant for me.

Yarn made it painless for the team to sync on versions of packages that we use on the project <3

I use Yarn because it outputs nice progress messages with cute emoji and installs packages quickly if the package is cached. Also, Yarn creates yarn.lock file which makes the developer use the consistent environment.

You should use whichever had the best DX (developer experience) for your team. If you are doing a massive front-end project, consider yarn if not only because it makes it a snap to go from zero to ready. What some people say about npm being more stable or easier for smaller projects is highly true as well. (not to mention, you sometimes have to install yarn) But, note that official NodeJS Docker images ship with both npm and yarn. If you want to use yarn, put package-lock=false and optionally save-exact=true in your project's .npmrc file. Compare whether you prefer the ergonomics of yarn global add over npm install -g or see fewer meaningless warnings for the specific set of dependencies you leverage.

I use npm because its the official package manager for Node. It's reliability, security and speed has increased over time so the battle is over!

We tend to stick to npm, yarn is only a fancy alternative, not 10x better. Using a self -hosted private repository (via sinopia/npm-mirror) make package locking (mostly) pointless.

I use Yarn because it process my dependencies way faster, predictable deps resolution order, upgrade-interactive is very handy + some Yarn specific features (workspaces, Plug’n’Play alternative installation strategy) ...