found drama

get oblique

Linkdump for September 3rd

by Rob Friesel
  • Philip Walton:

    Almost every type of coupling between HTML, CSS, and JavaScript can be lessened with an appropriate use of classes and a predictable class naming convention.

    Long read, but he has lots of good points. And as he points out, a lot of these are easy (and tempting) mistakes to make.

  • Tom Dale:

    What we’re doing wasn’t even possible in the browser a few years ago. It’s time to revisit our received wisdom.

    Possibly a bit deliberately inflammatory? Contrast this with something like the Jake Archibald post that made the rounds about two months ago. Both sides of this argument have merit, and both of them have nuanced discussions of the subject. Meditate it on come to your own conclusions.

    For what it's worth: "Progressive enhancement everywhere except where it doesn't make sense."

    UPDATE: And then along comes the Brad Frost “Fuck You” post which I can’t help but read as a direct response to Tom Dale’s post. And I get it — both sides of this discussion — which are different flavors of the same side, really — and how everyone’s passions are getting in the way of listening to each other.

  • Tim Kadlec:

    The point is not that we all need to be testing on Google Glass—time will tell how well that device does. The point is that here is a brand new device and form factor and they didn’t have to do a single thing to have get their site working on it.

    He's speaking more broadly than just "do responsive design"; he's talking about progressive enhancement and some other foundational principles that should guide you as a front-end engineer. It's not always easy to work this way, but you should fight for it; remember: the rewards are rich.

    (tagged: design )
  • If you write JavaScript: you want this.
  • Ryan Singer (37signals):

    It’s important to understand that a feature is not a situation. You can dig into a situation to learn what is valuable and what is not according to the goal. Digging into a feature definition doesn’t do that. It has no origin and no goal. Analyzing a feature definition leads you to play out all the things a person might value from the feature instead of learning what they actually value.

  • Oh hey! Check out this fascinating blog my friend found: "…dedicated to Vermont's curiosities, esoterica and forgotten places."
    (tagged: Vermont )
  • Joel Hooks has been tearing it up lately and this deep-dive into AngularJS services is no exception.

About Rob Friesel

Software engineer by day, science fiction writer by night. Author of The PhantomJS Cookbook and a short story in Please Do Not Remove. View all posts by Rob Friesel →

Leave a Reply

Your email address will not be published. Required fields are marked *

*

*