April 12, 2012

Look at the great stuff Adobe’s putting into WebKit

Seriously, look at it: Blending modes, better typography, Web inspector improvements, lots of CSS Regions improvements, a WebKit HUD in Dreamweaver, and more–and that’s all in the course of three days.  (Boy, Adobe sure is stuck in a Flash-only mindset…)

Posted by John Nack at 11:21 AM on April 12, 2012

Comments

  • Toby — 12:23 PM on April 12, 2012

    Yep, it’s almost as if they haven’t completely 180’d on Flash in the past 18 months..

    Seriously though, Adobe is definitely stepping up their web game with these contributions.

  • Jeremy Chone — 1:50 PM on April 12, 2012

    +1, very cool stuff. Then, we just need photoshop to HTML/CSS code snippets, and we will be all set ;)

    [Yeah? How would you go about using that, and how would you rate the capability relative to other things you’d like to see PS do? I think CSS generation could be cool, but I’d like to know more about exactly what people want, and how badly they want it. –J.]

    • Michael Corn — 11:54 AM on April 13, 2012

      I don’t think that photoshop to HTML/CSS snippets will work the same every time, I feel like you’d be exporting a lot of images. I would like to see the opposite. I want a layer where I can control text or color with HTML/CSS. Especially since you’re so into webkit these days; you could use it to render the layer. That way i can make mockups with elements I’ve already built in my website. It feels like the CS6 type controls are headed that with style control, I just always want more!

  • Coleran — 6:26 PM on April 12, 2012

    Actually, would argue that it is stuck in the flash (but without the ‘only’) mindset. Adding proprietary features outside the standards systems was exactly what flash was all about ;)

    [Well yeah: Put another way, that means “Delivering cool stuff years & years before the whole design-by-committee thing can do its thing.” I mean, all this stuff they’re adding to HTML is wonderful–but it’s been available in Flash for years. –J.]

    • Pedro Estarque — 8:38 PM on April 12, 2012

      Adding proprietary features outside the standards systems was exactly what flash was all about ;)
      Except WebKit is open source, which makes all the difference.

      • Carbon43 — 10:25 PM on April 12, 2012

        Pedro, actually not exactly. Open source is good and cool and shiny and spiffy (I like open source stuff!), but that does not “make all the difference”. There is nothing inherently wrong with privately owned and maintained code. There is plenty of good, well written code the rights to which are owned by a private entity who uses and licenses that in a fair and reasonable manner.

        Here’s what happened with Flash. (before I go further I should note that I’m a staunch flash hater, so I find it odd to be defending it in this case… but I digress) The state of web interaction and usability when flash was first developed, and throughout much of Flash’s existence was very poor. As John so eloquently pointed out, “design by committee” can really, really suck in some aspects. It can move at a positively glacial pace. Flash provided a powerful tool to enhance user experiences on the web long before such a thing would have been possible with *standards*. Thats awesome, and a win for everyone. Where Adobe failed is they became overly reliant on Flash being their own little bit of leverage on the market, and attempted to exert unreasonable influence to force continued use of Flash in areas where it’s usefulness was diminishing as a result of natural market forces and standards catching up, in order to maintain their advantageous status quo, rather than evolving with the market. I’m happy to say it looks like over the past year + it looks like they’ve realized that they can’t hold onto the past, and need to innovate and drive forward the future. *That* is what John’s post ^^^^ way up there is all about.

  • Timothy — 6:17 AM on April 13, 2012

    Isn’t this mostly for the benefit of Adobe’s own authoring tools though? I mean this doesn’t really feel like the Amish drove down the road and fixed the neighbor’s barn after the storm so much as the politician went to Washington to change the law for their own benefit.

    • Glenn — 11:34 AM on April 13, 2012

      These additions are going through the web-standards process. Yes, it’ in Adobe’s interest to push and help create these improvements, and that would help sell authoring tools. But if these additions were useless, pointless, and nobody wanted them, they wouldn’t help sell more authoring tools.

      I’m looking forward to using CSS Regions — and am fine with Adobe creating an authoring tool that would help create the proper CSS. If the Adobe authoring tool is sub-par, the standard is out there and anyone can create a tool that does the same thing. If they wanted, they could make it free. This should be a win for everyone.

  • Scarbom — 5:48 AM on April 16, 2012

    can’t wait to see how css regions are only used by print designers afraid of the web.

  • haleonearth — 5:25 PM on May 07, 2012

    Welcome to the party! I’m glad to see Adobe getting their head in the game :)

    [Thanks for the condescension. Just because you never read about stuff like this on Daring Fireball et al. doesn’t mean is doesn’t happen (or that it hasn’t been happening for a long time). –J.]

Copyright © 2014 Adobe Systems Incorporated. All rights reserved.
Terms of Use | Privacy Policy and Cookies (Updated)