Live data from Hacker News

Oh, Adobe... read the copy, then view the source.

muse.adobe.com

41–50 of 151 posts

Re: Oh, Adobe... read the copy, then view the source.

#41
post #17

Earlier quoted context omitted.

What a shameful waste of a good front-end developer's time.

"What a [lucrative] waste of a good front-end developer's time."

You couldn't pay me enough to _maintain_ that mess. Not even a unit test in sight if something breaks.

Re: Oh, Adobe... read the copy, then view the source.

#42

Earlier quoted context omitted.

WYSIWYG for HTML is just never a good thing. You spend more time learning the idiosyncrasies of a crippled GUI when you could just get busy in a text file.

I agree! I also think compilers are ridiculous. You spend much more time tuning their output and learning their arcane options and switches and pragmas than you would need just writing ASM by hand.

Reductio ad absurdum? :(

Re: Oh, Adobe... read the copy, then view the source.

#43

Earlier 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…

How about we've progressed to the state where HTML is the bytecode you don't want to see anyway, and designers can use modern tools to manipulate it? If the generated markup works, cross-browser and cross-platform (I don't know to what extent it does, but let's assume so), then what's the problem? For many purposes, optimizing the HTML nerd out of the process is a much bigger win than a 20k download (don't forget gzi…

It's not a matter of clinging to the past.

I definitely want and wish for tools that can allow me to design websites without having to know what IE developers were thinking the day they decided to have some fun.

The reason vim, emacs and the likes are still used a lot isn't because of nostalgia but because it works great for the user.

The issue with all the WYSIWYG editors is they take the "a web site can be anything and everyone can be a designer"-approach which is completely make believe. Till they make some form of WYSIWYM editor aimed at the web designer to use, all other approaches are worthless because they are basically just Word that's fancied up.

Most graphic designer classes have a field trip to see how typographers worked for newspapers 60 years go, and learn why their job was important - and such a day will come for designers some day too when it comes to writing code in hand.

But till then, design and code still matters.

Re: Oh, Adobe... read the copy, then view the source.

#44
post #18

Earlier quoted context omitted.

Sprite sheets?

I can't tell whether you're suggesting a solution or taking a guess as to what Muse did. I think it's the latter. Sorry if I interpreted your question incorrectly. :) They're using a hidden div full of elements to load the hover images before they're requested by an actual hover. It's all the way at the bottom of their code code: [Removed for brevity] Sprite sheets are another option (using the sliding doors techniqu…

The windowing technique isn't ungainly when its done automatically for you a la SpriteMapper :)

http://yostudios.github.com/Spritemapper/

Re: Oh, Adobe... read the copy, then view the source.

#46

People on HN love ripping on Adobe. I agree that the code is gross, but can we get some constructive criticism? What's a better way to programmatically write good HTML? I'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?

WYSIWYG for HTML is just never a good thing. You spend more time learning the idiosyncrasies of a crippled GUI when you could just get busy in a text file.

Yes, I also write all my programs in assembly for the same reason...

Re: Oh, Adobe... read the copy, then view the source.

#47
I recommend reading this post by Zeldman from last year: http://www.zeldman.com/2010/07/05/an-indesign-for-html-and-c...

    Says Nack:

    As I noted the other day, “Almost no one would look
    inside, say, an EPS file and harrumph, ‘Well, that’s not
    how I’d write PostScript’–but they absolutely do that    
    with HTML.”

Re: Oh, Adobe... read the copy, then view the source.

#49
post #38

Earlier quoted context omitted.

How about we've progressed to the state where HTML is the bytecode you don't want to see anyway, and designers can use modern tools to manipulate it? If the generated markup works, cross-browser and cross-platform (I don't know to what extent it does, but let's assume so), then what's the problem? For many purposes, optimizing the HTML nerd out of the process is a much bigger win than a 20k download (don't forget gzi…

You're forgetting that when several thousand people access a site per second, even a 1kb difference means thousands of dollars of bandwidth cost and fractions of a second of download speed.... let alone 70KB of difference which would bankrupt your company and turn all of your users away. We don't write HTML/JS/CSS by hand because it's fun, that's for sure. We focus on code-reuse and delayed loading plus AJAX (plus gz…

This.

And, not to mention no business owner want to get locked into a solution, they want their "data" transferable and standardized to at least some extend.

The code this produces is so horrible you've lost all the time spent with it. Muse dies out, and your time spent in it dies with it.

Re: Oh, Adobe... read the copy, then view the source.

#50
post #24

Earlier quoted context omitted.

But first tell me why designers need html page generator? Is learning HTML and css that much hard in google era?

Do you really think everyone has 100+ hours to spend learning the idiosyncrasies of HTML and CSS? That's asking a lot for someone that just wants to put up a landing page for an idea, or to design their portfolio. Everytime my artist friend wants to put their portfolio online, I suggest they start by writing some simple markup and half an hour later I'm explaining the finer points of the box model while they whinge a…

That's why we have WordPress, Tumblr, etc., even things like launchrock, about.me, shopify, the list goes on.
Post reply on HN