Skip to main content
B i r n o u
B i r n o u
Legend
December 10, 2019
Question

Dreamweaver always subject to resource indigestion

  • December 10, 2019
  • 1 reply
  • 2827 views
 
 

Hello Everyone,

not a month goes by without someone complaining about slow processes and jerky user interface activity, so today I'm back in charge.
the new version of Dreamweaver is totally unusable... at least as long as it is not in demo mode... i.e. working on C:/, one site at a time, teamwork reduced to a single collaborator, etc... etc....
and then this Adobe Dreamweaver Helper... what a greedy one... couldn't we reduce its activity somehow without loosing the real use of the helper ?
fortunately Sublime Text can help me at these times....

 

This topic has been closed for replies.

1 reply

pziecina
pziecina
Legend
December 10, 2019

Hi Birnou, doing nothing today, so thought I would look in on the forum.

 

I don't think Dw is meant for users who are building anything more than 1 site at a time, or more than 1 user working from the local drive. So anything more than those users should not be using Dw. Even modern client side code has fallen way behind what is possible, (or required in many cases), with only code support for those who are building small 'cheap' or 'demo/personal' sites.

 

Dw was built, (years ago) for such type of user, and over the years bits have been added for such users. Without a complete rewrite of the underlying Dw code it has reached its limit of possibilities. All the updates to Dw since CS6, have simply been add-ons to support the single user, (designer not developer). Slowing it down completely once more is asket of it.

 

Who is to blame for this, is irrelevant now. Simply because to get it working correctly for anything more is not going to happen, as the underlying code that ties everything together is too old and slow, and Adobe either is not interested, or does not 'see' Dw as more than it currently is.

B i r n o u
B i r n o uAuthor
Legend
December 10, 2019

hello Paula,

cool to see you again on the forum... well, actually, since the new forum is in place, I'm not as assiduous as I used to be.
it's too much mess if we're registered in various forums...

 

we get tons of mail without filtering possibilities by forums, by subject or anything constructive... everything happens in the same funnel... results, I only catch a thread, at random, once in a while


So let's get back to our business....


I share your opinion on the user target and the context of use, however... following Dreamweaver's digestive slowness, I opened the preferences... I unchecked... without thinking too much
- activate the integrated 2-byte input
- activate code indicators
- enable descriptive bubble information
- Auto insertion of braces
- Auto insertion of quotation marks
- Enable Linting
then I relaunched Dreamweaver,
I opened the task manager, and stopped Dreamweaver Helper, (the one who is an atonome singleton) not the one included in Dreamweaver's internal tasks.
and since then...


Dreamweaver works without slowdown, on server, and with multiple users

pziecina
pziecina
Legend
December 10, 2019

You have just confirmed what I thought, (the underlying Dw code is to old), by that I mean the code that ties it all together.

 

The disabled features you mentioned, are mainly from Brackets based code, which is much more modern than the code on which Dw is still based -

Dw's base code goes back to html2, in-line css, javascript v2 all of which is then tied together using c++ from the 90's, (Windows 95/98/xp, or whatever the Apple OS was at the time, just recompiled). That's why I think the performance has dropped off so dramatically over the years, as more and more has been asked of Dw, without the base Dw code keeping up.

 

Yes, it could be argued that as computers have gotten faster, (remember a fast computer at the time of xp's release was still only about 1ghz, and ram about 512Mb), so the performance of Dw's base code should have increased, the trouble is, as we both know, there comes a point when it starts to drop off, which I think was reached in the late 00's.

 

There is also the problem of Dw now using 2 (or more) very different code bases, (1 from Dw before 2017 version, 1 from the Brackets code editor, and others from the different 3rd party features). All of which will have been incorporated using the 'quick and dirty' coding methods that have become very prevalent in programming over the years, (or to rephrase the methology, 'get it working, and that is good enough').

 

 

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices