Hello, AeroSun, you wrote: AS> - "integration with "? - In it is better only if studio never used." git blame "," git rebase - interactive "," git stash "in studio already is? With normal ? AS> -"assembly"? - Studio solutions from them.props is actually the standard of the assembly, competitors are not present. Ridiculously. All topic about inability of studio to work with different systems of the assembly. AS> -"navigation"? - Here even to argue there is nothing. At first it is much more convenient than open files in . Nonsense. is a self-deception. If at you the big project at you ten open files, visual navigation on - the anti-pattern which reduces productivity. AS> in the second - besides which it is possible to add a side-about-side to hang out on remaining monitors + considering them with integration in Win a desktop - similar convenience is not given by the environment. In it is possible to open some editors and to dissolve them on different monitors, only at normal navigation it rarely is necessary AS> In one pain to edit if the code is arranged in many places. Well if to try to pass by means of a mouse - can be yes. But all power in F2 ("Follow symbol under cursor") and a locator (passage to classes, methods, files etc. including fuzzy logic) and passage forward-back as in the browser. AS> and "Peek definition"? Horror. In : F2, looked and "alt+left" to return reversely. AS> yes well after that it does not turn out to consider seriously (I it is not assured even not that there generally ever there will be a similar functionality). The studio is a deadlock way of evolution in respect of editing, nobody repeats their approach, and MSEC saw Visual Studio Code. AS> But! We not consider bare studio, and a standard development environment under with ++? In this case without VAX at all has no sense to compare. In-in, without a paid plug-in the studio is not made absolutely not (except for a debugger). AS> And with VAX: AS> - VA View - with absence of this piece at once it is possible to give-90 efficiency % on the big or unfamiliar projects. Actually it is the killer-feature - any another IDE cannot make alternative of studio if it has given piece. AS> - VA Outline - with absence of this piece it is necessary to add still-90 efficiency % on unfamiliar projects and absence of convenience at the big refactoring AS> - VA Hashtags - in heavy and big projects the invaluable help, especially rescues in AS> - additional helps AS> - additional navigation, + list methods, open correcponding file, find references (!!! Who it - is already difficult when there is no), illumination of places where the variable (the same for reading) AS> - additional means of refactoring AS> - changes (yes, they around are, but here it is the most convenient) AS> - code inspection If to translate with bird's on normal it appears that considerable part of it is in Kreatore from a box. Free of charge. . AS> Therefore against studio looks as a notepad against Word. The majority of a functional simply misses, or in embryo, or is made inconveniently. Well it is clear, as well as in a case with qbs to be beyond the learned template - in any way.