With IntelliJ’s rise, NetBeans’ popularity waned with the transition from Sun to Oracle. There are many reasons why this happened. One such major case was when JetBrains paired with Google, and then Android development transitioned from Eclipse to IntelliJ. These domains brought about power popularity struggles. Over the years, significant domains controlled by Java rose. As Eclipse took over JBuilder, NetBeans began jockeying as the preferred IDE for Java.

However, in the end, it has been swallowed by Eclipse. Since IntelliJ’s inception in the new Millenium and the rise of Java, IntelliJ had entered to compete in the IDE space against NetBeans and JBuilder. IntelliJ’s strength has been supporting Java. Before we focus on the transformations, let’s explore IntelliJ’s historical origin and its tooling strengths. I’ll label these additions as serial code transformations (SECTAs). We will also review the cons of visual noise, code quality consequences, and non-deterministic code. We will review these user interface improvements with the perceived pros of readability, proper labeling, and discoverability. There could be more to come in the version series. We will discuss three additions added to IntelliJ 2016.2, 2016.3, and 2018.1. I decided IntelliJ because there is an exciting improvement trend unfolding that I’d like to explore in its user interface. While there are many environments to choose from, my focus will revolve around JetBrains’ IntelliJ. The IDE played a crucial role in that success. One of the many great examples is what transpired over at Uber. From the individual to the collective, IDEs can cradle and support extensive team efforts. The IDE and its tooling are what make developers productive. The IDE has been and still is the extension of the developer’s hands. With thirty plus years under his belt, he had seen many IDE environments from visual to textual and back again. IntroductionĪs I was chatting on Workplace with our SVP of Engineering about his new post on Kotlin, our conversation shifted from his trials as a young engineer to how terrifyingly awesome the recently integrated development environment (IDE) experience has become. We will call these serial code transformations. Our integrated development environment has introduced user interface improvements that may profoundly impact the way we code.

Jetbrains webstorm 11 serial