For 7 years in a row, Rust has been the most loved programming language! Find out why Rust is so popular and how you can learn it for free.

This is a multipart series on building Fleet, a next-generation IDE by JetBrains. Part I – Architecture OverviewPart II – Breaking Down the EditorPart III – State ManagementPart IV – Distributed TransactionsPart V – The Story of Code CompletionPart VI – UI With Noria In Part V of this series, we discussed code completion, which is just one of Fleet’s services. Now it’s time to talk about something as big as our very own declarative UI framework for JVM, Noria. We built Fleet with Noria. Let’s look at the ideas behind Noria, the main concepts, and other exciting features. Where it all

We use a lot of tools for software development. Compilers, linkers, package managers, code linters, and, of course, IDEs are essential parts of our work and life. There are areas where single-tool efforts are not enough to provide the best user experience. In Rust, macro support is definitely something we can’t wholly tackle without broad community understanding and collaborative effort. We, the IntelliJ Rust plugin team, are now partially enabling support for procedural macros, specifically enabling function-like and derive procedural macro expansion by default while hiding support for att

Build scripts is a Cargo feature that allows executing any code prior to building a package. We implemented support for build scripts evaluation in the IntelliJ Rust plugin a long time ago, but up until now, we hid it under the org.rust.cargo.evaluate.build.scripts experimental feature. As we are now enabling this feature by default, we’ve decided to explain what it means for our users. What is a build script, and why should we care? Most Rust projects use build scripts to deal with native dependencies, configure platform-specific options, or generate some source code. Let’s recall the b

This is a multipart series on building Fleet, a next-generation IDE by JetBrains. Part I – Architecture OverviewPart II – Breaking Down the EditorPart III – State ManagementPart IV – Distributed TransactionsPart V – The Story of Code CompletionPart VI – UI with Noria In Parts III and IV of this series, we discussed the complicated abstract architectural concepts involved in state management and how they are synchronized across Fleet’s distributed components. Now it’s time for us to look at a more familiar function – Code completion – and see how it is implemented in Fleet. Fleet is no

This is a multipart series on building Fleet, a next-generation IDE by JetBrains. Part I – Architecture OverviewPart II – Breaking Down the EditorPart III – State ManagementPart IV – Distributed TransactionsPart V – The Story of Code CompletionPart VI – UI with Noria In Part III of this series, we focused on how we represent, store, and change elements of Fleet’s state. In this part, we’ll talk about Fleet as a distributed IDE and how it guarantees the consistency of data across all of its distributed components. Fleet is a platform for real-time remote collaboration between developer

This is a multipart series on building Fleet, a next-generation IDE by JetBrains. Part I – Architecture OverviewPart II – Breaking Down the EditorPart III – State ManagementPart IV – Distributed TransactionsPart V – The Story of Code CompletionPart VI – UI with Noria In previous parts of this series, we looked at an overview of the Fleet architecture and discussed the algorithms and data structures that are used under the hood in the editor. In this part, we’ll start looking at the approach we take to implement state management. This is a complicated topic, so we’ll devote a couple of bl