I don't think they've screwed up Typekit at all.

Is that a joke? For me, it's now intrusive: I can't turn off Typekit notifications and suggestions, even though I use Suitcase Fusion.

An ugly website is one thing, there are millions, but an ugly website that has found an entirely new way to be ugly is impressive.

This is a really impressive effect, but I'd hesitate to use it as part of a generic cms backed site since the auto-sizing could inadvertently editorialize the meaning of a headline at different page widths.

"Roddick SURVIVES, Staving Off Retirement" vs "Roddick Survives, Staving Off RETIREMENT"

This is what the preset word combinations mentioned in the post are for.

Ahh, right, i missed that. I was distracted from the sub-headings by the big bold responsive headings.

I do not like language {X}, but I do like language {Y}. Everyone should agree to write in language {Y}, so that we can all pretend that language {X} does not exist, and maybe then browsers will just start using {Y} natively.

There are some fairly clear indicators from Adobe itself about the future of dreamweaver.

Note what they say in the 'Code' section here: http://html.adobe.com/toolsandservices/ "We think there’s a need for a different type of code editor – we’re working on something and will have more to share soon."

... which is plainly referring to this project: https://github.com/adobe/brackets

I don't know what their definition of "soon" is but if they are talking about Brackets then they better get crackin'. Brackets has a long way to go.