gorohoroh

Yes Roslyn is first party and it naturally does load, and it's very memory-intensive. You can see it happening without any extensions installed.

Frontend is in Java (and Kotlin), indeed, as it's a part of the IntelliJ platform. However, the backend that actually provides IDE features for C# is written in .NET. The backend is actually the same ReSharper logic that runs in Visual Studio but in headless mode.

This is not necessarily true, especially with VS2015 RTM (Update 1 is a bit better): https://twitter.com/hmemcpy/status/687257223081377792

It's not built from scratch. It makes full use of the existing ReSharper code base.

This is not a plugin but a standalone product. Essentially this is standalone IntelliJ shell that communicates with a ReSharper process.

You're not.

If you look at the underlying markup, you can see that the web site was designed to be responsive. The sad part however is that it's going to take a bit more time for mobile resolutions to be supported properly.

Yes, our free products (IntelliJ IDEA and PyCharm Community Editions, dotPeek) are not affected by these changes. They'll be available as before.

JetBrains rep here.

"Phoning home" is actually not new. We've introduced JetBrains Account as a way of authorizing a product instance (as an alternative to license keys) for a couple of years now.

Current student licenses work exactly the same way, as well as a part of classroom and OS licenses AFAIK. A lot of current personal and some commercial licenses are managed through a JetBrains Account as well.

With the new scheme, JetBrains Account will simply gain more usage than now, hard-coded license keys will eventually go away, but a license server option for environments that have restricted Internet connection will be provided the same as it is now.

Now, there might be certain additional steps we might need to take to ensure license delivery in certain scenarios but we'll be handling this as we receive specific problem reports.

This is the licensing model that's used now, not the new one introduced in November.

Probably by virtue of total karma lost by JetBrains reps here.

That's a great comment, thank you. Let me check how all the prices relate once again and come back to you.

We're not changing anything in this regard: if it works now, it will work the same way with new subscription licenses.

If you encounter a case when a setup like this doesn't work, please contact JetBrains and we'll look into resolving the problem.

Yes, nothing changes in this respect: you can run multiple instances of Visual Studio with ReSharper on the same machine.

Co-using IJ and ReSharper should be fine as well, as long as it's you and only you using them.

Yes, the change applies to corporate licenses, too. As a bonus for them, there's a transparent model of discounts based on number of licenses and term of payment (https://www.jetbrains.com/toolbox/#commercial)

We're used to helping users of commercial licenses who are faced with delayed payments in their companies, and I'm sure we'll be doing this with the new model as well.

I see this is turning into a conspiracy theory )

Fortunately, there's a little thing called competition that prevents raising rates at will without facing the consequences, and JetBrains is no exception: we're no monopoly.

I'm sure different product teams here at JetBrains will adapt to the new model in a different way. My hope is that the change will contribute to a focus switch from a race to provide new features to ensuring better stability, performance and UX.

Your understanding of how perpetual licenses with upgrade subscriptions work is correct.

Also, you can still be pretty confident that as a language support by an IDE (PhpStorm in your case) evolves, new versions will be supported by this very IDE, and we don't have any plans to release a separate Php7Storm :)

I was referring to a different kind of change where you might switch from PHP to Ruby, from C# to Java. C# and PHP are naturally not the best combination to support in the same IDE, meaning you might switch your tools as you go from language to language.

IntelliJ IDEA Community Edition, dotPeek and all other free tools stay free as before. Nothing changes in this respect.

For commercial PhpStorm licenses a rough comparison would as follows.

Before November 2: First year: $199 a seat Each subsequent year: $129 a seat

After November 2: First year and each subsequent year: $119-149 a seat (with/without a promotion available)

Your understanding of the agreement is correct.

On the other hand, as languages and frameworks change, they will not necessarily be supported by your current IDE. In this case, with a perpetual licensing model you're simply left with a license that you don't use anymore, and you're buying a new license to another IDE. With subscriptions, you switch between them as necessary: either by cancelling subscription to one of them and subscribing to another or by maintaining a subscription to all IDEs (which will also be available starting Nov 2.)

If you have an existing perpetual license, you can use it infinitely, just as the license agreement stated when you purchased it.

We do however offer a switch to the new model if you like it and if you're interested in new versions that your perpetual license doesn't cover. If you do switch to the new model, you pay as long as you need to use a tool, and you always get the latest version.

IntelliJ Ultimate will continue to offer language plugins, nothing changes in this regard.

Let's discuss. Why do you think this is bad?

A lot. Definitely a similar set of code inspections/quick-fixes and navigation actions. Not sure about the set of refactorings and context actions (intention actions in their terms) but based on history of IntelliJ IDEA based products that CLion is, I think they won't disappoint in this regard, too.

Second-long freezes... could be ReSharper, could be a different plug-in or a VCS integration interfering with ReSharper. Unfortunately you got rid of it so I guess we'll never know for sure )

I think it should definitely get better with SSD although not sure if it would be completely OK: 500k is quite a lot, at least by v1.0 standard. Give it a try when/if you're on a SSD. Do get in touch with us (https://youtrack.jetbrains.com/issues/rscpp) if still too slow by then, we'll try to see what can be done.

Mixed comments on resource usage so far. Some examples: * "Besides beeing a bit slow, VS suddenly felt like a proper IDE" * "a bit more sluggish than using vanilla VS, but made up for it in terms of usability" * "even after I've opened the project and everything is parsed, Visual Studio slows down too much for it to be acceptable" * "once resharper had completed (warning up) though, everything was fine and Visual Studio + performance was pretty good"

(these are all from a recent reddit thread: http://www.reddit.com/r/programming/comments/31xbrt/jetbrain...)

Seems that it depends on the size and complexity of a solution, takes trying to see if it's acceptable in a given environment. That said, a lot of performance work is ahead provided that the team has input on what's going wrong and in what circumstances.

First of all ReSharper C++ offers ~60 real-time code inspections. Things like unreachable code, hiding local declarations, dependent type without 'typename' keyword, non-inline function definition in a header file, boost::format with too many or too few arguments, invalid printf format specifiers, redundant keywords ('else', 'static', 'template' etc).

Quick-fixes are provided for many of the inspections so that if you want to act on an inspection, you can have R# C++ do the editing for you.

AFAIK Visual Assist has very limited code analysis capabilities.

Refactorings/transformations such as "Substitute macro call", "Initialize field from constructor parameter", "Merge nested if statements", "Replace redundant parentheses", "Move method implementation out of class scope" or "Replace 'auto' with explicit type" are also unique to ReSharper C++ AFAIK.

Also I don't think VAX has navigation to derived/base symbols or specializations.

Some of the things that VAX has but R# C++ doesn't include Document method, auto-inserting underscores after 'm' and Header hierarchy view.

Here's how a dev on the R# C++ team has summarized differences between the tools in a comment last year: http://www.reddit.com/r/cpp/comments/29k4fb/resharper_for_c_...

(Disclaimer: I'm with JetBrains, the company behind ReSharper C++. If you want to take the above with a grain of salt, feel free to.)

It's true that PyCharm doesn't let you work with files out of project. AFAIK this should change later this year in all IntelliJ IDEA-based products including PyCharm.