Choosing between Dreamweaver and Webstorm

Question

HTML

The question may be a little strange, but...

I have a small dispute with the layout designer: he is madly in love with Dreamwever, but for a number of reasons I want to transfer him to WebStorm

. I understand that you will not be forced to be nice. By and large, you can leave Dw, but now I don’t hear good arguments for Dw.

Help me understand - what is the Dw kill feature? What is there that is not in WebStorm. I personally tried both products, but apparently a superficial comparison is not enough.

Answer 1

These are completely different tools, dw is an editor, webstorm is an ide. It's like, for example, he now has a microwave with two handles, time and power. And she heats food perfectly, and nothing more is needed from her. And you want to give him a bunch of modes, a grill, airflow from all sides and a control panel like a starship.
If he doesn’t need to write rollicking js, then you will greatly reduce his speed if you drag it with dw and it’s not a fact that over time it will return to the current one.

Answer 2

I only know the self-kill feature of Dw - a visual html editor that terribly crap in the code, and for the use of which some colleagues want to hit the fingers with a ruler)

Answer 3

For some, it’s generally more convenient to type in a notebook, for example, in sublime text and you don’t need anything else in life, but of course, when you type only in Dreamweaver, a notebook will seem like something scary.
Suggest to the layout designer as an experiment to switch to Webstorm for a month, you can add a little financial motivation.

Answer 4

I think you should quit your business. What is the point of transplanting this? What problem do you want to solve?
Convenience for the designer is a killer feature that does not require additional arguments.

Answer 5

With your layout designer, everything is clear in principle, he uses Dw because he is used to it. Therefore, it is necessary to show him the Webstorm killer features as soon as possible. And exactly what to show, at least a few videos to show, with the same LiveEdit. So that he sees that some of his actions can be done faster and more conveniently. And just to put him behind WebStorm for a month will be of little use, because. without the desire to explore its advanced features, he will perceive it as a Dw with an unusual interface.

Answer 6

Dreamweaver is native and beautiful, WebStorm is Java and scary.
I understand him very much. But I myself use WebStorm :(

Answer 7

I sat on Dw for a long time, then moved to WebStorm, which I never regret. For example, there is no need to poke ctrl + s every time, everything is automatic. The most convenient integration with all possible version control systems. A bunch of options for code highlighting, code verification, in the 6th, besides, all sorts of LESS, SASS, CofeeScript, etc. were added. So any layout designer will find convenience in it. + everything is customizable. When I switched to it from Dw, I set up code highlighting exactly as in Dw, and everything went smoothly.

Answer 8

so ask the coder why he is in love with Dreamwever =)

Answer 9

Tell your coder that without explicit arguments, he will definitely be transferred to WS. It is advisable to do this by letter. Then he will have the opportunity to think about making a response list.
In a verbal conversation, many thoughts scatter, and he doesn’t say anything intelligible, most likely because he doesn’t realize that you need to hear it from him.
Written correspondence with a specific question will give you a specific answer.

Answer 10

Don't torment the coder, let him stay on Dreamweaver. I myself would not sit down for anything other than Dreamweaver, if I had to make up again.