intellij vs intellij idea

PyCharm and IntelliJ Idea were both developed by Jet Brains, and there is one key difference that may dictate which one you might be interested. Difference between IntelliJ Idea and Eclipse · IntelliJ Idea. IntelliJ IDEA is the most powerful, popular, and fully-featured IDE for Java Developers, which was. The major difference among the above-mentioned three IDEs is that IntelliJ IDEA is for Java programming, PHPStorm is for PHP language and.

Intellij vs intellij idea -

Difference between IntelliJ Idea and Eclipse

next →← prev

IntelliJ Idea

IntelliJ IDEA is the most powerful, popular, and fully-featured IDE for Java Developers, which was released for the public in 2001. It is developed and maintained by Jet Brains Company. It is licensed by Apache 2.0.

IntelliJ Idea is available in two editions:

Community Edition: It is available for free and mostly used for Java and Android developers. It supports most of the languages such as Java, Kotlin, Groovy, Clojure, Scala and others. It includes features like Code Completion, Deep static analysis, intelligent refactoring, debugger, test runner, etc.

Ultimate Edition: The ultimate edition has the most advanced set of features for developing web and desktop application. It supports the integration of spring framework, web development framework like Node.js, Angular, and React, Java EE support such as JSF, JAX-RS, JPA, CDI, etc.


Eclipse is an open-source IDE for developing applications using the Java, Python, Ruby, C, C++, etc. The IBM released it in 2001 under the Eclipse Public License (EPL). It became popular soon for developing free and commercial projects. Today, it became the most popular Java IDE. It contains a base workspace and an extensible plug-in system for customizing the environment.

IntelliJ Idea vs Eclipse

There are lots of disputes on this topic which makes it difficult to decide which of them are the most important. As a result, most of the developers claim that both IDEs are equal in their capabilities, and choosing any of them is a matter of taste. But, I assume that it's not a matter of taste only. There are reasons which help you to distinguish the differences between both of them.

1. System Requirements

We can install IntelliJ Idea on Windows, macOS and Linux with the following hardware:

  • 2 GB RAM minimum, 4 GB RAM recommended
  • 1.5 GB hard disk space + at least 1 MB for caches
  • 1024�768 minimum screen resolution

We can run Eclipse IDE on any platform that supports JVM including Windows, macOS, Linux and Solaris. It demands the following hardware:

  • 0.5 GB RAM minimum, 1+ GB RAM recommended
  • 300 MB hard disk space minimum, 1+ GB recommended
  • Processor speed of 800 MHz minimum, 1.5 GHz or faster recommended

2. Debugging

As of the debugging process, sometimes we want to evaluate some expression to see its value. In Eclipse, you need to select the whole expression. Otherwise, the eclipse cannot evaluate it. But, with IntelliJ Idea, you do not need to select the whole expression. You just put the cursor at any place inside the expression and press Alt+F8. IntelliJ Idea understands which expression you have a need and shows a dialog window suggesting several possible variants for the expression. You can also edit and evaluate the expression in this dialog window.

3. Autocomplete

Autocomplete is an option which differs the any IDE from notepad. Here, feeling the context gives IntelliJ Idea a qualitative advantage over Eclipse. For example, we started writing a code:

Now, we want to find what options can start with letters "vi". IntelliJ immediately understands the method that wants a Condition class instance as a second parameter, which is Condition.visible. So, IntelliJ immediately suggests the only valid option for the method, whereas Eclipse cannot understand the valid context quickly. It does not know that the cursor is located where the second parameter of the method should place. So when you press the Ctrl + Space, Eclipse shows everything that begins with the letters "vi" which useless information.

4. Refactoring

All the modern IDE provides a very impressive set of refactoring. But, IntelliJ Idea refactoring is more intelligent as compared to other IDE. It can easily understand what you want and provides many options which are suitable for most situations.

5. Plugins

Eclipse marketplace provides more than 1250 plugins, whereas IntelliJ Idea offers approx. 750 plugins only. But, the plugins difference doesn't make much difference because plugins for new technology usually created mainly for the Eclipse.

6. Performance

The more plugins installed in the IDE make it more heavy for your computer. However, Eclipse handles the large projects faster as compared to IntelliJ Idea because it indexes the entire project on start-up. But, when you are working on an existing project, IntelliJ Idea works faster and smoother as compared to Eclipse.

7. Usability

IntelliJ is much easier to use as compared to Eclipse. The learning curve is far faster in IntelliJ, which makes developing easier and more natural. Code completion, Dropdowns, quick view, project wizards, etc. are all possible in both Eclipse and IntelliJ, but the user experience in IntelliJ is much more satisfying.

Next TopicIntelliJ IDEA Window Elements

← prevnext →


IntelliJ IDEA overview

IntelliJ IDEA is an Integrated Development Environment (IDE) for JVM languages designed to maximize developer productivity. It does the routine and repetitive tasks for you by providing clever code completion, static code analysis, and refactorings, and lets you focus on the bright side of software development, making it not only productive but also an enjoyable experience.


IntelliJ IDEA is a cross-platform IDE that provides consistent experience on Windows, macOS, and Linux.

Supported languages

Development of modern applications involves using multiple languages, tools, frameworks, and technologies. IntelliJ IDEA is designed as an IDE for JVM languages but numerous plugins can extend it to provide a polyglot experience.

JVM languages

Use IntelliJ IDEA to develop applications in the following languages that can be compiled into the JVM bytecode, namely:

Other languages

Plugins bundled with IntelliJ IDEA and available out of the box add support for some of the most popular languages, namely:

C/C++ are not officially supported in IntelliJ IDEA, but you can use CLion.

You can browse the JetBrains Marketplace to find an official plugin that adds support for almost any language, framework or technology used today, or for third-party plugins. See Manage plugins for details on how to manage plugins in IntelliJ IDEA.

Do I need a language plugin for IntelliJ IDEA or a separate IDE?

IntelliJ IDEA Ultimate is a superset of most IntelliJ platform-based IDEs. If the bundled language plugins are enabled, it includes support for all technologies that are available within our more specific IDEs, such as PyCharm, WebStorm, PHPStorm, and so on.

So, for example, if your application's codebase is mainly in Java, but it also uses Python scripts, we recommend using IntelliJ IDEA in combination with the bundled Python plugin. If your codebase is mainly in Python, PyCharm is the right IDE for you.

IntelliJ IDEA editions

IntelliJ IDEA comes in three editions:

  • IntelliJ IDEA Ultimate: the commercial edition for JVM, web, and enterprise development. It includes all the features of the Community edition, plus adds support for languages that other IntelliJ platform-based IDEs focus on, as well as support for a variety of server-side and front-end frameworks, application servers, integration with database and profiling tools, and more.

  • IntelliJ IDEA Community Edition: the free edition based on open-source for JVM and Android development.

  • IntelliJ IDEA Edu: the free edition with built-in lessons for learning Java, Kotlin, and Scala, interactive programming tasks and assignments, and special features for teachers to create their own courses and manage the educational process (see IntelliJ IDEA Edu).

See the IntelliJ IDEA editions comparison matrix.

The Early Access program

IntelliJ IDEA Ultimate is available for free within the Early Access Program (EAP). EAP builds are published before the release of a stable product version, and you can download them to try out the new features before they are publicly available in return for your feedback. EAP builds are configured to collect feature usage statistics, and are a valuable source of information for our developers. You can also report an issue if you encounter any problems.

Release Candidate (RC) builds published before a release are also available for download, but require a paid license.

Preview builds published after the release of a stable version that are followed by an official update, also require a paid license and cannot be evaluated for free.

User Interface

IntelliJ IDEA provides an editor-centric environment. It follows your context and brings up the necessary tools automatically to help you minimize the risk of interrupting the developer's flow.

Take a guided tour around IntelliJ IDEA user interface.

Ergonomic design and customizable appearance

One of the best things about IntelliJ IDEA is its tunability. You can configure virtually anything: the IDE appearance, the layout of tool windows and toolbars, code highlighting, and more. There are also numerous ways you can fine-tune the editor and customize its behavior to speed up navigation and get rid of any extras that distract you from code.

  • Configure the colors and fonts for your source code, console output, debugger information, search results, and more. You can choose from a number of predefined color schemes or customize a scheme to create a unique working environment.

  • Learn how to configure the editor settings, including appearance, font, code formatting, and more.

  • Customize menus and toolbars to spare the annoyance of looking for an action among a dozen buttons you never use.

Shortcuts for everything

In IntelliJ IDEA, you have shortcuts for nearly every action, including selection and switching between the editor and various tool windows.

Use the most useful shortcuts to invoke frequent actions without switching your focus from the editor and tune your keymap to assign custom shortcuts for your favorite commands.

Watch this video to learn about some of the most useful shortcuts:

Navigation and search

IntelliJ IDEA provides quick navigation not only inside source code files but also throughout the entire project.

One of the most useful shortcuts that is worth remembering is that brings up the Search Everywhere dialog: start typing and IntelliJ IDEA will look for your search string among all files, classes, and symbols that belong to your project, and even among the IDE actions.

search everywhere animation

Here are some of the most useful navigation shortcuts:



Search everywhere

Go to file

Go to class

Go to symbol

Go to declaration

See Source code navigation for more hints on how to navigate through the source code, and learn the most useful shortcuts that help you quickly switch between the editor and various tool windows, switch focus, jump to the Navigation bar, and so on.

Recent files and locations

Normally, you work with a small subset of files at a time and need to switch between them quickly. The Recent Files action is a real time-saver here. Press to see a list of last accessed files. Note that you can also use this action to open any tool window:

Recent Files popup

Apart from jumping to a recent file, you can also get quick access to Recent Locations- that is code snippets you last viewed or edited. Press and you'll be able to jump to a particular line you modified lately:

Recent Locations popup

File structure

Press to open the file structure popup that gives you an overview of all elements used in the current file and lets you jump to any of them:

File structure popup

Alternatively, use the Structure tool window

Find action

If you don't remember the shortcut or the menu path for an action you want to use, press and start typing the action name:

Find Action popup

Coding assistance

Code completion

IntelliJ IDEA helps you speed up the coding process by providing context-aware code completion.

  • Basic completion helps you complete the names of classes, methods, fields, and keywords within the visibility scope:

    Basic code completion
  • Smart completion suggests the most relevant symbols applicable in the current context when IntelliJ IDEA can determine the appropriate type:

    Smart code completion

For more information on the different types of code completion available in IntelliJ IDEA with examples and productivity tips, see Code completion.


IntelliJ IDEA offers a comprehensive set of automated code refactorings that lead to significant productivity gains. For example, when you rename a class, the IDE will update all references to this class throughout your project.

You don't even need to bother to select anything before you apply a refactoring. IntelliJ IDEA is smart enough to figure out which statement you're going to refactor, and only asks for confirmation if several choices are possible. Just press to open a list of refactorings available in the current context:

refactor this popup

See section Refactoring code for a full list of available refactorings with usages scenarios and the before and after examples.

Learn some of the most useful refactoring shortcuts:



Refactor this


Extract variable

Extract field

Extract a constant

Extract a method

Extract a parameter




Static code analysis

IntelliJ IDEA provides a set of inspections that are built-in static code analysis tools. They help you find potential bugs, locate dead code, detect performance issues, and improve the overall code structure.

Inspections not only tell you where a problem is but also provide quick fixes that help you deal with it right away. Click the red bulb next to the highlighted code, or press to choose a fix:

Intention action

Apart from quick-fixes, IntelliJ IDEA also provides intention actions that help you apply automatic changes to code that is correct. For example, you can inject a language, add Java annotations, add JavaDoc, convert HTML or XML tags, and much more. To view a full list of intention actions, in the Settings/Preferences dialog , go to Editor

How is IntelliJ better than Eclipse? [closed]

I work with Intellij (9.0.4 Ultimate) and Eclipse (Helios) every day and Intellij beats Eclipse every time.

How? Because Intellij indexes the world and everything just works intuitively. I can navigate around my code base much, much faster in Intellij. F3 (type definition) works on everything - Java, JavaScript, XML, XSD, Android, Spring contexts. Refactoring works everywhere and is totally reliable (I've had issues with Eclipse messing up my source in strange ways). CTRL+G (where used) works everywhere. CTRL+T (implementations) keeps track of the most common instances that I use and shows them first.

Code completion and renaming suggestions are so clever that it's only when you go back to Eclipse that you realise how much it was doing for you. For example, consider reading a resource from the classpath by typing at this point Intellij will be showing you a list of possible files that are currently available on the classpath and you can quickly drill down to the one you want. Eclipse - nope.

The (out of the box) Spring plugin for Intellij is vastly superior to SpringIDE mainly due to their code inspections. If I've missed out classes or spelled something wrong then I'm getting a red block in the corner and red ink just where the problem lies. Eclipse - a bit, sort of.

Overall, Intellij builds up a lot of knowledge about your application and then uses that knowledge to help you write better code, faster.

Don't get me wrong, I love Eclipse to bits. For the price, there is no substitute and I recommend it to my clients in the absence of Intellij. But once I'd trialled Intellij, it paid for itself within a week so I bought it, and each of the major upgrades since. I've never looked back.


Android Studio and IntelliJ

Installation and setup

Follow the Set up an editor instructions to install the Dart and Flutter plugins.

Updating the plugins

Updates to the plugins are shipped on a regular basis. You should be prompted in the IDE when an update is available.

To check for updates manually:

  1. Open preferences (Android Studio > Check for Updates on macOS, Help > Check for Updates on Linux).
  2. If or are listed, update them.

Creating projects

You can create a new project in one of several ways.

Creating a new project

To create a new Flutter project from the Flutter starter app template:

  1. In the IDE, click New Project from the Welcome window or File > New > Project from the main IDE window.
  2. Specify the Flutter SDK path and click Next.
  3. Enter your desired Project name, Description and Project location.
  4. If you might publish this app, set the company domain.
  5. Click Finish.

Setting the company domain

When creating a new app, some Flutter IDE plugins ask for an organization name in reverse domain order, something like . Along with the name of the app, this is used as the package name for Android, and the Bundle ID for iOS when the app is released. If you think you might ever release this app, it is better to specify these now. They cannot be changed once the app is released. Your organization name should be unique.

Creating a new project from existing source code

To create a new Flutter project containing existing Flutter source code files:

  1. In the IDE, click Create New Project from the Welcome window or File > New > Project from the main IDE window.

    Important: Do not use the New > Project from existing sources option for Flutter projects.

  2. Select Flutter in the menu, and click Next.
  3. Under Project location enter, or browse to, the directory holding your existing Flutter source code files.
  4. Click Finish.

Editing code and viewing issues

The Flutter plugin performs code analysis that enables the following:

  • Syntax highlighting.
  • Code completions based on rich type analysis.
  • Navigating to type declarations (Navigate > Declaration), and finding type usages (Edit > Find > Find Usages).
  • Viewing all current source code problems (View > Tool Windows > Dart Analysis). Any analysis issues are shown in the Dart Analysis pane:
    Dart Analysis pane

Running and debugging

Note: You can debug your app in a few ways.

  • Using DevTools, a suite of debugging and profiling tools that run in a browser and include the Flutter inspector. DevTools replaces the previous browser-based profiling tool, Observatory.
  • Using Android Studio’s (or IntelliJ’s) built-in debugging features, such as the ability to set breakpoints.
  • Using the Flutter inspector, directly available in Android Studio and IntelliJ.

The instructions below describe features available in Android Studio and IntelliJ. For information on launching DevTools, see Running DevTools from Android Studio in the DevTools docs.

Running and debugging are controlled from the main toolbar:

Main IntelliJ toolbar

Selecting a target

When a Flutter project is open in the IDE, you should see a set of Flutter-specific buttons on the right-hand side of the toolbar.

Note: If the Run and Debug buttons are disabled, and no targets are listed, Flutter has not been able to discover any connected iOS or Android devices or simulators. You need to connect a device, or start a simulator, to proceed.

  1. Locate the Flutter Target Selector drop-down button. This shows a list of available targets.
  2. Select the target you want your app to be started on. When you connect devices, or start simulators, additional entries appear.

Run app without breakpoints

  1. Click the Play icon in the toolbar, or invoke Run > Run. The bottom Run pane shows logs output.

Run app with breakpoints

  1. If desired, set breakpoints in your source code.
  2. Click the Debug icon in the toolbar, or invoke Run > Debug.
    • The bottom Debugger pane shows Stack Frames and Variables.
    • The bottom Console pane shows detailed logs output.
    • Debugging is based on a default launch configuration. To customize this, click the drop-down button to the right of the device selector, and select Edit configuration.

Fast edit and refresh development cycle

Flutter offers a best-in-class developer cycle enabling you to see the effect of your changes almost instantly with the Stateful Hot Reload feature. See Hot reload for details.

Show performance data

Note: To examine performance issues in Flutter, see the Timeline view.

To view the performance data, including the widget rebuild information, start the app in Debug mode, and then open the Performance tool window using View > Tool Windows > Flutter Performance.

Flutter performance window

To see the stats about which widgets are being rebuilt, and how often, click Show widget rebuild information in the Performance pane. The exact count of the rebuilds for this frame displays in the second column from the right. For a high number of rebuilds, a yellow spinning circle displays. The column to the far right shows how many times a widget was rebuilt since entering the current screen. For widgets that aren’t rebuilt, a solid grey circle displays. Otherwise, a grey spinning circle displays.

The app shown in this screenshot has been designed to deliver poor performance, and the rebuild profiler gives you a clue about what is happening in the frame that might cause poor performance. The widget rebuild profiler is not a diagnostic tool, by itself, about poor performance.

The purpose of this feature is to make you aware when widgets are rebuilding—you might not realize that this is happening when just looking at the code. If widgets are rebuilding that you didn’t expect, it’s probably a sign that you should refactor your code by splitting up large build methods into multiple widgets.

This tool can help you debug at least four common performance issues:

  1. The whole screen (or large pieces of it) are built by a single StatefulWidget, causing unnecessary UI building. Split up the UI into smaller widgets with smaller functions.

  2. Offscreen widgets are being rebuilt. This can happen, for example, when a ListView is nested in a tall Column that extends offscreen. Or when the RepaintBoundary is not set for a list that extends offscreen, causing the whole list to be redrawn.

  3. The function for an AnimatedBuilder draws a subtree that does not need to be animated, causing unnecessary rebuilds of static objects.

  4. An Opacity widget is placed unnecessarily high in the widget tree. Or, an Opacity animation is created by directly manipulating the opacity property of the Opacity widget, causing the widget itself and its subtree to rebuild.

You can click on a line in the table to navigate to the line in the source where the widget is created. As the code runs, the spinning icons also display in the code pane to help you visualize which rebuilds are happening.

Note that numerous rebuilds doesn’t necessarily indicate a problem. Typically you should only worry about excessive rebuilds if you have already run the app in profile mode and verified that the performance is not what you want.

And remember, the widget rebuild information is only available in a debug build. Test the app’s performance on a real device in a profile build, but debug performance issues in a debug build.

Editing tips for Flutter code

If you have additional tips we should share, let us know!

Assists & quick fixes

Assists are code changes related to a certain code identifier. A number of these are available when the cursor is placed on a Flutter widget identifier, as indicated by the yellow lightbulb icon. The assist can be invoked by clicking the lightbulb, or by using the keyboard shortcut (+ on Linux and Windows, + on macOS), as illustrated here:

IntelliJ editing assists

Quick Fixes are similar, only they are shown with a piece of code has an error and they can assist in correcting it. They are indicated with a red lightbulb.

Wrap with new widget assist

This can be used when you have a widget that you want to wrap in a surrounding widget, for example if you want to wrap a widget in a or .

Wrap widget list with new widget assist

Similar to the assist above, but for wrapping an existing list of widgets rather than an individual widget.

Convert child to children assist

Changes a child argument to a children argument, and wraps the argument value in a list.

Live templates

Live templates can be used to speed up entering typical code structures. They are invoked by typing their prefix, and then selecting it in the code completion window:

IntelliJ live templates

The Flutter plugin includes the following templates:

  • Prefix : Create a new subclass of .
  • Prefix : Create a new subclass of and its associated State subclass.
  • Prefix : Create a new subclass of and its associated State subclass, including a field initialized with an .

You can also define custom templates in Settings > Editor > Live Templates.

Keyboard shortcuts

Hot reload

On Linux (keymap Default for XWin) and Windows the keyboard shortcuts are ++ and +.

On macOS (keymap Mac OS X 10.5+ copy) the keyboard shortcuts are + and +.

Keyboard mappings can be changed in the IDE Preferences/Settings: Select Keymap, then enter flutter into the search box in the upper right corner. Right click the binding you want to change and Add Keyboard Shortcut.

IntelliJ settings keymap

Hot reload vs. hot restart

Hot reload works by injecting updated source code files into the running Dart VM (Virtual Machine). This includes not only adding new classes, but also adding methods and fields to existing classes, and changing existing functions. A few types of code changes cannot be hot reloaded though:

  • Global variable initializers
  • Static field initializers
  • The method of the app

For these changes you can fully restart your application, without having to end your debugging session. To perform a hot restart, don’t click the Stop button, simply re-click the Run button (if in a run session) or Debug button (if in a debug session), or shift-click the ‘hot reload’ button.

Editing Android code in Android Studio with full IDE support

Opening the root directory of a Flutter project doesn’t expose all the Android files to the IDE. Flutter apps contain a subdirectory named . If you open this subdirectory as its own separate project in Android Studio, the IDE will be able to fully support editing and refactoring all Android files (like Gradle scripts).

If you already have the entire project opened as a Flutter app in Android Studio, there are two equivalent ways to open the Android files on their own for editing in the IDE. Before trying this, make sure that you’re on the latest version of Android Studio and the Flutter plugins.

  • In the “project view”, you should see a subdirectory immediately under the root of your flutter app named . Right click on it, then select Flutter > Open Android module in Android Studio.
  • OR, you can open any of the files under the subdirectory for editing. You should then see a “Flutter commands” banner at the top of the editor with a link labeled Open for Editing in Android Studio. Click that link.

For both options, Android Studio gives you the option to use separate windows or to replace the existing window with the new project when opening a second project. Either option is fine.

If you don’t already have the Flutter project opened in Android studio, you can open the Android files as their own project from the start:

  1. Click Open an existing Android Studio Project on the Welcome splash screen, or File > Open if Android Studio is already open.
  2. Open the subdirectory immediately under the flutter app root. For example if the project is called , open .

If you haven’t run your Flutter app yet, you might see Android Studio report a build error when you open the project. Run in the app’s root directory and rebuild the project by selecting Build > Make to fix it.

Editing Android code in IntelliJ IDEA

To enable editing of Android code in IntelliJ IDEA, you need to configure the location of the Android SDK:

  1. In Preferences > Plugins, enable Android Support if you haven’t already.
  2. Right-click the android folder in the Project view, and select Open Module Settings.
  3. In the Sources tab, locate the Language level field, and select level 8 or later.
  4. In the Dependencies tab, locate the Module SDK field, and select an Android SDK. If no SDK is listed, click New and specify the location of the Android SDK. Make sure to select an Android SDK matching the one used by Flutter (as reported by ).
  5. Click OK.

Tips and tricks


Known issues and feedback

Important known issues that might impact your experience are documented in the Flutter plugin README file.

All known bugs are tracked in the issue trackers:

We welcome feedback, both on bugs/issues and feature requests. Prior to filing new issues:

  • Do a quick search in the issue trackers to see if the issue is already tracked.
  • Make sure you have updated to the most recent version of the plugin.

When filing new issues, include the output of .


IntelliJ IDEA vs JetBrains Rider

IntelliJ IDEA vs JetBrains Rider: What are the differences?

Developers describe IntelliJ IDEA as "Capable and Ergonomic IDE for JVM". Out of the box, IntelliJ IDEA provides a comprehensive feature set including tools and integrations with the most important modern technologies and frameworks for enterprise and web development with Java, Scala, Groovy and other languages. On the other hand, JetBrains Rider is detailed as "A cross-platform .NET IDE based on the IntelliJ platform and ReSharper". It supports .NET Framework, the new cross-platform .NET Core, and Mono based projects. This lets you develop a wide array of applications including .NET desktop applications, services and libraries, Unity games, Xamarin apps, ASP.NET and.

IntelliJ IDEA and JetBrains Rider belong to "Integrated Development Environment" category of the tech stack.

Some of the features offered by IntelliJ IDEA are:

  • Smart Code Completion
  • On-the-fly Code Analysis
  • Advanced Refactorings

On the other hand, JetBrains Rider provides the following key features:

  • live code inspection
  • fast
  • responsive

Lyft, Asana, and Square are some of the popular companies that use IntelliJ IDEA, whereas JetBrains Rider is used by UGroop, Quote Software, Inc., and Hivemind. IntelliJ IDEA has a broader approval, being mentioned in 815 company stacks & 1067 developers stacks; compared to JetBrains Rider, which is listed in 6 company stacks and 5 developer stacks.


VS Code vs IntelliJ IDEA

I use VS Code for a number of things. It has all sorts of handy extensions. I have written a number of simple Java text file parsers and converters with it. I find it very easy to write and run single file stuff in it. I have not done a large project with it.

I have used InteliJ a little and Eclipse a lot. From what I understand InteliJ is the better of the two and the most popular. Next Java project I do I want to try InteliJ.

They’re are not really apples to apples. InteliJ is a full blown IDE. VS Code is a text editor, albeit a fancy one. You may be able to approach the capabilities of an IDE with enough extensions but out of the box VS Code does not compare.

As for noob tips, use InteliJ or Eclipse. IDEs exist for a reason and are helpful. Once you get used to the anatomy of a Java project and the tools in the IDE you should try going at it with a text editor and command line. I am not comfortable enough to attempt a large project outside of an IDE but I prefer it for simple stuff.

1 Like

intellij vs intellij idea

Notice: Undefined variable: z_bot in /sites/ on line 107

Notice: Undefined variable: z_empty in /sites/ on line 107

4 Replies to “Intellij vs intellij idea”

  1. I will! Taking a little break right now to finish some music projects but I'll be starting a series for Live 11 this year.

  2. What is old is new again. I used to do this for friends and acquaintances to make a little extra money back in the day. 🤗😍. So funny to see this again.

Leave a Reply

Your email address will not be published. Required fields are marked *