Forums

This topic is locked

dreamweaver mx slow as hell on mac os x

Posted 14 Dec 2002 12:26:05
1
has voted
14 Dec 2002 12:26:05 FUCK YOU ASSHOLE posted:
Does anyone know why Dreamweaver is so slow?

Opening a new file.... takes about 5 seconds. (Five FULL SECONDS)
Closing a file... about 5 seconds

selecting text and:
- changing font in properties window - 3 seconds
- font to actually change on screen - 3 seconds
- selecting size of font in properties window - 3 seconds
- size to actually change on screen - 3 seconds

TWELVE FULL seconds to change the font and size of any text!!

My system:
Powerbook Titanium 400 mhz
1 GB of RAM
2.5 GB free HD space

Fresh install of Mac OS 10.2.2

any ideas?????????

Replies

Replied 15 Dec 2002 08:04:14
15 Dec 2002 08:04:14 Dan The Man replied:
your processor is what is causing the slow down
Replied 15 Dec 2002 08:29:24
15 Dec 2002 08:29:24 FUCK YOU ASSHOLE replied:
<BLOCKQUOTE id=quote><font size=1 face="Verdana, Arial, Helvetica" id=quote>quote:<hr height=1 noshade id=quote>
your processor is what is causing the slow down
<hr height=1 noshade id=quote></BLOCKQUOTE id=quote></font id=quote><font face="Verdana, Arial, Helvetica" size=2 id=quote>

That's BS. No Adobe software has these problems. No Apple software has these problems. Just Macromedia software. So a 400 mhz G4 is not powerful enough to handle opening a file in Dreamweaver? But opening a 300 dpi 11x17 image in Photoshop works fine?

I guess my question then is this:
Does everyone with a 400 mhz G4 have the same problem???
Replied 15 Dec 2002 12:24:55
15 Dec 2002 12:24:55 Dan The Man replied:
i got a 1.1gHz AMD processor my computer runs like a champ
doing the same task as you complained about take less than half a second
Replied 15 Dec 2002 13:10:42
15 Dec 2002 13:10:42 FUCK YOU ASSHOLE replied:
So your solution is to get a PC? Well that's not good enough. I already have a PC (1.8 Ghz Celeron). My laptop is a mac though, and I use it when I am mobile.

The same tasks also take half a second on my mac, with Adobe software.

So just wondering if anyone on mac os x has had these Macromedia problems. I would assume a newer faster mac doesn't have these problems? Any ideas?
Replied 17 Dec 2002 08:21:27
17 Dec 2002 08:21:27 lalo camacho replied:
I have the same problem. I've got a Cube 450, 768 MB Ram, 12 GB free space, OS X 10.2.2.
Replied 17 Dec 2002 08:32:52
17 Dec 2002 08:32:52 FUCK YOU ASSHOLE replied:
<BLOCKQUOTE id=quote><font size=1 face="Verdana, Arial, Helvetica" id=quote>quote:<hr height=1 noshade id=quote>
I have the same problem. I've got a Cube 450, 768 MB Ram, 12 GB free space, OS X 10.2.2.
<hr height=1 noshade id=quote></BLOCKQUOTE id=quote></font id=quote><font face="Verdana, Arial, Helvetica" size=2 id=quote>

Sorry to hear that, dude. I bet Macromedia is not skilled enough to make software that works well on a processor as "slow" as a &lt;500 mhz G4.

The only reason I don't really go out looking for a solution or complaining is because I know Macromedia software is shabby in general, while Adobe software is always fast, powerful, and almost 100% bug-free.

Anyone with a faster mac have the same problem?
Replied 19 Dec 2002 11:00:10
19 Dec 2002 11:00:10 Dave Clarke replied:
Just my 2 pence worth .. If you dislike Macromedia so much .. don't use it.. problem solved.

ASP|VBScript|IIS5.1|Access|WinXPPro & WinXPHome
Replied 19 Dec 2002 12:28:16
19 Dec 2002 12:28:16 Owen Eastwick replied:
I know Mac and Intel processors aren't directly comparable, but until recently I developed on a PC with dual Pentium PIII 500Mhz processors and 512Mb RAM. While it was little sluggish compared to newer 2Ghz + PC's, it was useable and no where near as slow as say your Mac is.

With larger dynamic, database integrated sites there was a noticeable pause when you opened a file before you could edit text etc., a second or two perhaps, but definately not 5. Smaller HTML only sites were no problem at all. I guessing you are not using a database and creating dynamic sites if you are developing on a Mac.

I wouldn't imagine there's that much difference in performance between a PIII 500 and a Mac 400 processor which would suggest that it is a problem with the Macromedia/Mac/OS combination rather than purely a lack of processor oomph.

Regards

Owen.

Multiple Parameter UD4 / Access 2000 Database Search Tutorial:
www.tdsf.co.uk/tdsfdemo
Replied 27 Dec 2002 19:25:29
27 Dec 2002 19:25:29 Carolus Holman replied:
Dude you're not alone, I have the same issues when opening files in DWMX with the the Update running on a Dual Pentimum3 with 512MEgs of ram. Every other program runs fine, from Photoshop to VisualStudio.Net enterprise Architect, as well as SQL Server 2000. I can run all of these on my machine at the same time. When I switch over to DWMX, it's like I have entered the SLOW ZONE. I try to open a 50K .asp page it takes like 20 Seconds, then it refreshes the site, which takes it 25Secs-3 minutes. I tried moving the Levels of Undo down to like 5, still no help. Rumours are that Microsoft has it's eye on Macromedia, it would be a good fit for Microsoft, and good for everyone else, maybe they good fix the memory management problems this software seems to have. Example when I open my Site, which is only about 600 Pages, it starts using about 30 megs of RAM, I then open a page, now it's up to about 100 Megs of RAM! WOW what a HOG! My pages typically have 3 or 4 SSI's, About 3-4 Database calls, and 3 or more Javascript links. It seesm that DWMX puts all of these objects into memory for some reason, even if you are in Text - mode... DWMX is a good tool but it needs a real thorough tune up.

--Los is a Ghost

Reply to this topic