I'm not going to do the typical assuming that so many do here about people's experience, because I don't know anything about anyone's experience. I've been coding in C for a long time now, and Construct is not exactly like programming in a language at all, so you could be the most experienced coder in the world and still be confused to no end by Construct. I know plenty of seasoned professional coders who fall right into that category who want nothing to do with event-based programs out of frustration.
Anyway, Skyhunter has raised something that should be examined respectfully. In Construct in a few of my projects, it's had trouble loading a few mere images in "Run Layout" totaling just 200 KB's each and my computer has more than enough power for Construct and is in tip-top shape. I've then taken the same images into other programs to test it, and they loaded quickly with no problems. It's not simply a hardware issue, there is something deeper. I put this in the same bin as those who've had trouble getting the 360 controller object to respond, and that was an issue that the community denied and blamed on the user (check it on search) with such gems as "you don't know programming that's why you can't get it to work" etc, the typical bull know-it-all's say around here. However, it was finally found as a problem and as you can see in the Changelogs, it was addressed by the developer.
The point is, things that are working on some machines aren't working correctly or at all on others. Some people have inferior machines and it's working fine, and then yet on superior machines it's not. It all needs further examination into why that's happening rather than the typical community dismissal.