IntelliJ IDEA

Bewertung des Programmes IntelliJ IDEA

Kommentare: Ich finde IntelliJ eines der besten, je auf den Markt gebrachten Progammierprogramme für hauptsächlich die Sprache Java.

Vorteile:

Mir gefällt besonders gut, das man bei den meisten Sachen die man programmiert schon bei dem kleinsten Fehler drauf hingewiesen wird und einem auch geholfen wird mit Tutorials (.class).

Nachteile:

Mir gefällt persönlich das neue Design nicht so, weshalb ich das alte benutze.

My experience using Intellij IDEA

Vorteile:

Mostly i have used intellij IDEA for my android application development. it gives really good code complication and provides some of the best debugging feature One more i thing i liked most is its zen feature which gives me less distraction is best when you want to focus on work.

Nachteile:

I got it from my student developer pack otherwise its quite expensive for common user to use. In begging you may need time to get used to all the capabilities of it

Jetbrains Tools make me 10x the developer I am

Kommentare: IDEA is like going from using hand tools to using power tools for the first time. It's a learning curve, but when you see what you can achieve with it, you wonder how you ever wrote code without it.

Vorteile:

I love that it indexes your entire project, so that intellisense actually suggests methods that exist and make sense rather than fuzzy matching like other IDEs do.

Nachteile:

It is expensive. If you're a developer that has to pay for these tools personally instead of paid for by a company, it's a tough pill to swallow, but very worth it.

In Betracht gezogene Alternativen: Apache NetBeans und Visual Studio Code

Warum IntelliJ IDEA gewählt wurde: The in-depth understanding the IDE has of not just the language but the databases, build tools and frameworks around the language, that make using the language easier.

Zuvor genutzte Software: Apache NetBeans und Visual Studio Code

Gründe für den Wechsel zu IntelliJ IDEA: The enterprise-grade tooling that comes with the IDE. It's not just an editor, but it's also a version control viewer, a database inspector, diagram generator and more.

The best IDE for Java and Kotlin development software

Kommentare: This is the best tool for creating software and app using Java and Kotlin. Even if the software is far from being free, there are many many features that may never be used, but if needed are a life changer !

Vorteile:

This is the best tool for Java/Kotlin development. Every tool you could ever need is included. The syntax highlighting is very important and works amazingly well !

Nachteile:

The software is very expensive, and the support isn't easy to reach (only public forums, no kind of chat/mail/phone support). Also, this software isn't beginner-friendly because many features are hidden in menus. It may take several months before being fully familiarized with the software.

I would not recommend IJ for AS3 / Flex / AIR Development

Kommentare: Extremely bad experience. It was so bad that I started to build my own AS3 / Flex / AIR build engine; it overcomes the above problems and I can use it in place of IntelliJ's build & pack functionality. It will be on GitHub soon, look for ciacob/SIRIUS

Vorteile:

It was an IDE that *somehow* filled the gap for AS3 / Flex / AIR developers after Flash Builder left the stage. With Moonshine not mature enough and Flash Developer being a rather unfriendly bunch of batch scripts that one would have to edit for things to kind-of-work, IntelliJ IDEA (plus the Flash/Flex/AIR plug-ins) stepped in to provide a solution, any solution at all.

Nachteile:

I want to make it crystal clear that I mainly use IJ for AS3 / Flex / AIR development. I do not know whether its subpar behavior is rooted in those dedicated plugins. I did use IJ for developing some Node.js applications, and experience was a little better. But this review is ONLY about using IJ for AS3 / Flex / AIR development. I very much dislike pretty everything, but the worst are: - the build process: IJ does not do any work to ease SWC dependencies management; in a world where there are tools that analyze your code for imports and class instantiations and automatically match them against projects and libraries in your workspace (I build myself such a tool, it's name is SIRIUS and will be soon out on GitHub), IJ still wants you to add by hand 25+ dependencies. - SDK handling: as any Flex/AIR developer knows, AIR SDKs have to be overlaid on FLEX SDKs and this alone is a source for countless problems; add on top that SDKs are often shipped in incomplete form (*.jar and *.swc files have to be salvaged from older SDKs) and you understand how being able to quickly patch / swap / tinker with an AIR/Flex SDK and test it's in working condition could save the day. IJ maintains some long-life caching of file listings in every SDK you throw at it; this makes it practically impossible to alter an existing SDK and have the changes reflected. The only workaround I have been able to find was to rename the SDK, add it as a new SDK, and remove the older one. - indexi CHAR LIMIT HIT.