Need advice about which tool to choose?Ask the StackShare community!
ESLint vs IntelliJ IDEA: What are the differences?
Introduction
ESLint and IntelliJ IDEA are two popular tools used in software development to improve code quality and catch bugs early in the development process. While both tools serve the same purpose, there are several key differences between them.
Integration with IDE: One of the main differences between ESLint and IntelliJ IDEA is their integration with an IDE. ESLint is a JavaScript linter that can be used in various text editors and IDEs, while IntelliJ IDEA is a full-fledged integrated development environment that offers built-in support for code analysis and debugging.
Language Support: ESLint primarily focuses on JavaScript and provides extensive support for various ECMAScript standards. On the other hand, IntelliJ IDEA supports a wide range of programming languages, including but not limited to JavaScript, Java, Kotlin, Python, Go, and PHP. This makes IntelliJ IDEA a versatile tool for developers working on multiple projects in different languages.
Customization and Extensibility: ESLint allows developers to customize and extend the linting rules by creating their own rule sets or by using plugins. It provides a high degree of flexibility and control over the linting process. IntelliJ IDEA, on the other hand, offers predefined code inspections and various configuration options. While it does provide some customization options, the level of customization is not as extensive as ESLint.
IDE-Specific Features: Since IntelliJ IDEA is an IDE, it offers a wide range of features that go beyond code analysis and linting. It provides powerful code completion, intelligent refactoring, version control integration, debugging tools, and many other productivity features. ESLint, being a linter, focuses primarily on code quality and does not provide these additional IDE-specific features.
Real-time Analysis: IntelliJ IDEA performs real-time code analysis as you type, providing instant feedback on potential issues and suggesting quick fixes. ESLint requires a separate linting step to be performed, either manually or through integration with a text editor or build system. This difference in analysis workflow can impact developer productivity and the ability to catch issues early.
Community Support and Adoption: ESLint has gained significant community traction and is widely adopted in the JavaScript ecosystem. It has an active open-source community, which regularly contributes new rules and plugins. IntelliJ IDEA, being a commercial IDE, also has a strong user base and support from JetBrains, the company behind the IDE. The level of community support and adoption may differ based on the programming language and specific use case.
In summary, ESLint is a versatile JavaScript linter that can be used in various text editors and IDEs, providing extensive customization options and community support. IntelliJ IDEA, on the other hand, is a feature-rich integrated development environment with support for multiple programming languages, offering built-in code analysis and a wide range of productivity features.
UPDATE: Thanks for the great response. I am going to start with VSCode based on the open source and free version that will allow me to grow into other languages, but not cost me a license ..yet.
I have been working with software development for 12 years, but I am just beginning my journey to learn to code. I am starting with Python following the suggestion of some of my coworkers. They are split between Eclipse and IntelliJ IDEA for IDEs that they use and PyCharm is new to me. Which IDE would you suggest for a beginner that will allow expansion to Java, JavaScript, and eventually AngularJS and possibly mobile applications?
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.
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.
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.
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.
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 :)
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.
Easy to learn and everything you need
Scenario: I want to integrate Prettier in our code base which is currently using ESLint (for .js and .scss both). The project is using gulp.
It doesn't feel quite right to me to use ESLint, I wonder if it would be better to use Stylelint or Sass Lint instead.
I completed integrating ESLint + Prettier, Planning to do the same with [ Stylelint || Sasslint || EsLint] + Prettier.
And have gulp 'fix' on file save (Watcher).
Any recommendation is appreciated.
In the case of .js files I would recommend using both Eslint and Prettier.
You can set up Prettier as an Eslint rule using the following plugin:
https://github.com/prettier/eslint-plugin-prettier
And in order to avoid conflicts between Prettier and Eslint, you can use this config:
https://github.com/prettier/eslint-config-prettier
Which turns off all Eslint rules that are unnecessary or might conflict with Prettier.
you don't actually have to choose between these tools as they have vastly different purposes. i think its more a matter of understanding how to use them.
while eslint and stylelint are used to notify you about code quality issues, to guide you to write better code, prettier automatically handles code formatting (without notifying me). nothing else.
prettier and eslint both officially discourage using the eslint-plugin-prettier way, as these tools actually do very different things. autofixing with linters on watch isnt a great idea either. auto-fixing should only be done intentionally. you're not alone though, as a lot of devs set this up wrong.
i encourage you to think about what problem you're trying to solve and configure accordingly.
for my teams i set it up like this: - eslint, stylelint, prettier locally installed for cli use and ide support - eslint config prettier (code formatting rules are not eslints business, so dont warn me about it) - vscode workspace config: format on save - separate npm scripts for linting, and formatting - precommit hooks (husky)
so you can easily integrate with gulp. its just js after all ;)
Pura vida! Well, I had a similar issue and at the end I decided to use Stylelint + Prettier for that job, in our case, we wanted that our linting process includes the SCSS files and not only the JS file, base on that we concluded that using only ESLint to do both things wasn't the best option, so, we integrated prettier with Stylelint, and for that we used a neat plugin that allowed us to use Prettier inside Stylelint here is the link, https://github.com/prettier/stylelint-prettier#recommended-configuration, I hope that this can help you, hasta pronto!, :)
I originally chose IntelliJ over Eclipse, as it was close enough to the look and feel of Visual Studio and we do go back and forth between the two. We really begin to love IntelliJ and their suite of IDEs so we are now using AppCode for the IOS development because the workflow is identical with the IntelliJ. IntelliJ is super complex and intimidating at first but it does afford a lot of nice utilities to get us produce clean code.
Pros of ESLint
- Consistent javascript - opinions don't matter anymore8
- Free6
- IDE Integration6
- Customizable4
- Focuses code review on quality not style2
- Broad ecosystem of support & users2
Pros of IntelliJ IDEA
- Fantastically intelligent301
- Best-in-class ide242
- Many languages support190
- Java158
- Fast121
- Code analysis82
- Reliable79
- Out of the box integration with maven, git, svn76
- Plugin architecture64
- Integrated version control61
- Code refactoring support12
- Best java IDE11
- Local history7
- Code Completion6
- Kotlin6
- Integrated Database Navigator6
- Built-in terminal/run tools6
- All5
- Free for open-source development, students and teacher5
- Base for Android Studio5
- Free If you're a Student5
- ERD Diagrams4
- Free4
- Cross platform4
- IDE4
- Database/Code integration4
- Out Of The Box features3
- Column Selection Mode3
- Server and client-side debugger3
- More than enough languages for any developer3
- Typescript support3
- Multicursor support3
- Reformating Code3
- Intuitive3
- Command-line tools3
- Android Integration3
- Vim support3
- Special icons for most filetypes in project list3
- Supports many frameworks3
- Built-in web server3
- Live Templates3
- Scala support3
- Works fine with mac os catalina2
- A lot of plugin2
- Just works2
- Integrated Ssh/Ftp Managers2
- Full support2
- Task managers2
- Diff tools2
- File Watchers2
- Support for various package managers2
- Integrated Code Linting2
- Clean UI2
- Open source2
- So modernised2
- Efficient, one Stop solution2
Sign up to add or upvote prosMake informed product decisions
Cons of ESLint
Cons of IntelliJ IDEA
- Large footprint required to really enjoy (mem/disc)20
- Very slow16
- Bad for beginners8
- UI is not intuitive7
- Not nearly as many tools to integrate as vs code5
- Constant reindexing5
- Needs a lot of CPU and RAM power4
- Built in terminal is slow3
- Doesn't work that well with windows 10 edu3
- Ruby is a plug in1
- Pesky warnings increase with every release1
- AAD0