Please, tell me this is Adobe trying to mock IE. It has to be, right? I mean, they've always sort of not valued source code, but this is beyond torturing it. This is so inspirationally horrible someone spent hours remaking it, like it should've been: http://studentweb.infotech.monash.edu/~wlay/FIT1012/muse-dem... .
Indeed. The inefficiency here is astounding, especially considering the relatively straightforward page layout involved. Original: 1496 lines, 77.9kB Your version: 104 lines, 4.75kB I'd thought we'd progressed beyond the state of a decade ago where Dreamweaver or what-have-you would build you a cumbersome and baroque html splooge to match whatever you had done in the designer, but I guess we haven't advanced that far…
Oh, Adobe... read the copy, then view the source.
11–20 of 151 posts
Re: Oh, Adobe... read the copy, then view the source.
#12Re: Oh, Adobe... read the copy, then view the source.
#13Re: Oh, Adobe... read the copy, then view the source.
#14Re: Oh, Adobe... read the copy, then view the source.
#15Has anyone seen the video? They're trying desperately to map print paradigms to the web. It's a major fallacy which many developers (and product managers) fall into.
Re: Oh, Adobe... read the copy, then view the source.
#16Please, tell me this is Adobe trying to mock IE. It has to be, right? I mean, they've always sort of not valued source code, but this is beyond torturing it. This is so inspirationally horrible someone spent hours remaking it, like it should've been: http://studentweb.infotech.monash.edu/~wlay/FIT1012/muse-dem... .
Re: Oh, Adobe... read the copy, then view the source.
#17Earlier quoted context omitted.
Indeed. The inefficiency here is astounding, especially considering the relatively straightforward page layout involved. Original: 1496 lines, 77.9kB Your version: 104 lines, 4.75kB I'd thought we'd progressed beyond the state of a decade ago where Dreamweaver or what-have-you would build you a cumbersome and baroque html splooge to match whatever you had done in the designer, but I guess we haven't advanced that far…
As long as tools like Dreamweaver exist, there will be a need for good front-end developers to clean up the mess.
Re: Oh, Adobe... read the copy, then view the source.
#18Please, tell me this is Adobe trying to mock IE. It has to be, right? I mean, they've always sort of not valued source code, but this is beyond torturing it. This is so inspirationally horrible someone spent hours remaking it, like it should've been: http://studentweb.infotech.monash.edu/~wlay/FIT1012/muse-dem... .
The original does have at least one advantage: preloaded hover images. It's nice for them to improve usability a tiny bit, along with all the bloat. I can't imagine a complete newcomer to HTML and CSS hacking together a page and having it come out nearly as bad. Any designer who can learn design can easily learn to code better than Muse, in my opinion.
Re: Oh, Adobe... read the copy, then view the source.
#19I'm willing to bet everybody on this thread writes their HTML by hand. How many of you have a framework for programmatically writing HTML? How many have a framework for writing HTML as broadly as Muse can?
Re: Oh, Adobe... read the copy, then view the source.
#20"You can design and publish original HTML pages to the latest web standards without writing code" - WTF I think compounding all this inefficiency is how they have " " on EVERY SINGLE DIV. Someone should use the Tilt extension to visualise this page in 3D ( http://hacks.mozilla.org/2011/07/tilt-visualize-your-web-pag... ) and screen cap it.