Dreamweaver CC slow typing performance [ awfully slow ]

I just upgraded from Dreamweaver CS6 (worked like a dream) to the latest CC... What a disappointment. Slow, slow, slow... Seems like this problem exist for four years now and Adobe didn't come with any solution.
Can anyone suggest a good alternative to Dreamweaver? I'm not paying £250 / year for wasting my time waiting for the code to appear...

DreamWeaver has always done this for years! Every since CS 5.5 it is the worst text editor in the world for performance! (At least on a PC) Glad you guys have Brackets as that's now my go to... I really only used DW when I need to do Directory Level Find and Replaces... besides that I got sick of the performance issues and cancelled my CS subscription. Granted performance is better in CS than 5.5 but as far as I am concerned their is no excuse for the development team to have such a hog for a text editor.

Dreamweaver 2015.3 release very slow when you try and type code this is really a pain and make for a very bad experience. I have tried all the suggestions from above and nothing works even on small files.

Too much time spent here trying to fix this problem and not getting any work done.

Any solutions.

Does any one please have any tips for Mac users...? This is just dreadful...

LIVE view OFF

Tool tips OFF

Reset prefs. DONE

And still its a bag of s***

Help would be massively appreciated.

Kind regards.

I'm experiencing slowness with Dreamweaver in code view on both my 2014 iMac and home and my brand new work PC. It's to the point that I literally cannot even use Dreamweaver any more.

Luckily I just discovered a trick that makes Dreamweaver at least usable again, which is to completely disable code hinting. Once I did that on my Mac typing performance is back to what I'd consider normal. I tried putting code hinting back on and deselecting all the code hinting libraries that aren't relevant to me but even with only 3 libraries checked performance was terrible again.

So I can use dreamweaver again but without any of the functionality that I like about it as a code editor.

I should point out that I'm coding up content using Google Polymer and it has a syntax which might be new to dreamweaver's code hinting, but it shouldn't be destroying performance the way it is.

I know this is an old thread, but would like to chime in. Recently upgraded to CC 2015.2 release under Windows 7 and experiencing everything OP described. Typing codes in code view yield a very, very slow response.

Even updating images in design view takes 10 seconds to "complete" before I see the mouse cursor blink again. This happens every time I change an image/media or make direct modification to the source code in code view. This means if I changed 10 images in a given HTML document, I'd have to wait a total of 100 seconds, or a minute 40 seconds, which is unacceptable. I tried toggling a few options here and there to no avail.

Finally, I right click on the app's icon to view its launch property and noticed that "Windows 7" was checked under "Run this program in compatibility mode" drop down. I unchecked it and voila, Dreamweaver ran like its former glory - fast with absolutely no lag at all.

Several months, a new monitor, computer, and OS later...I'm still having the same problem that I did. We've seemed to isolate it to using a second monitor. Now, originally it was that "there seems to be a conflict with the monitor" I was using as my secondary (an inexpensive 18" monitor from some other system). But when I replace it with my original Cinema display, and used a new Thunderbolt display as my primary....the same thing happened!

So for you designers that use two displays (which a LOT of us do)...Dreamweaver will be a problem for you.

Still frustrated that I'm paying for a product that I'm not receiving full use of

Wow, a discussion that spans over two years. I found this one because the issue was just reported – again. Impossible to tell if the original issue was fixed and resurfaced, or if it never really was resolved.

Interesting to read it all as a collection and to watch the group dynamic. First is the reported problem and attempts made to resolve it. Adobe rep joins discussion (when did this change – used to be user-to-user only). That seems to invite more people to report the problem, then seemingly having the attention of Adobe, it becomes a catch all for all issues DW. Then Adobe goes dark, prompting anger. Why aren’t they talking to us? Answer: nothing new to report. Then comes the next phase: this software is unusable, I should get a refund, I canceled my subscription. Adobe returns, announcing a new update. Feedback is ambiguous.

There were more people than usual report an issue in this thread. But still, only a small percentage of the entire user base. But – was their software unusable as well? Or did they learn from history so as not to repeat it. One simple fact:

ALL software updates and upgrades are always, without exception, (essentially) – beta. What is this unquenchable need to always have the latest and greatest, most recent, newest version? Why is either not upgrading or God forbid, rolling back the update, a workaround, a “temporary” solution?

I started out in IT, Desktop Support, before going into web development. My one takeaway from that time – nothing gets installed, gets rolled out – until fully tested. They did it themselves, didn’t even trust the reviews and reports on the net. Why was the CC developed in the first place? By the time of CS5, the financial officers of companies large and small put their collective feet down. They stopped approving upwards of two-grand per user per year for the next CS upgrade. Developers and designers all over murmured and complained, but they soon realized they could get all their work done with “last year’s model”.  Vendors actually breathed a sigh of relief if they collaborated with the clients that they didn’t have to have the program that could only work with CS6 programs. Funny thing though, open a CS5 file in CS6, but if you edit and save, oops – can’t open it again in 5. But why then is a PSD always a PSD? Good to know that some things are still sacred.

New Year’s resolution for all teams: take one two-year-old MBP that nobody wants, and two PC’s, one with Win 7, one with Win 10. Grab that empty office (everyone has at least one these days now), set up the machines, print and tape to the door (in Word, 72 pt. font, Comic Sans: TESTING LAB

I am having a similar problem, trying to view large single-line javascript files in Code View only. I just upgraded to Mac OS 10.11.1 (with quad core i7 3.4GHz, 8GB RAM) and Dreamweaver 2015.0 (7714).

A good example is the minified jquery source. If I open the minified version (http://code.jquery.com/jquery-1.11.3.min.js) the entire application slows to a crawl. However with that minified code file open, but in the background, all my other files work at full speed until I bring the minified code window to the foreground again. Turning "Code View Options -> Word Wrap" ON improves performance, but only slightly.

And it seems to be only files with very long single lines (like minified code), because if I open a CSV file with over 300,000 short individual lines everything is fine.

A Possible Fix ....

I have been having the problem for many many months, incredibly frustrating and like you all have tried almost everything. Again I started searching today and was getting nowhere Until I stumbled on this tip from a guy elsewhere.

Simply put - disable Code Hints. Or at the very least move it to 5 seconds. This has made a HUGE difference for me. I was seeing 7 ~ 10 seconds delay in clicking between Code and Design, and moving the scroll bar was trying to move a rock, just kept stalling.

I'm running an i7 with 8Gb  

Edit > Preferences > Code Hints > uncheck Enable Code Hints.

http://biostall.com/stop-adobe-dreamweaver-hanging-or-freezing-on-large-files

Another thing that has helped a bit was Excluding virus scan (using Avast) from scanning my standard include files particularly .js as these never change and antivirus causes delays every time scanning these.

But definitely try the Disable Code Hints.