Earlier generations have weathered recessions, of course; this stall we’re in has the look of something nastier. Social Security and Medicare are going to be diminished, at best. Hours worked are up even as hiring staggers along: Blood from a stone looks to be the normal order of things “going…
Was actually relieved that this just a park fire. Started wondering if something blew up.
Myles at a birthday party. (Taken with instagram)
Such a great a shot with @misscrash by Tommy Boy
Cool pic of Dave Navarro and suspension artist MissCrash at a recent Jane’s Addiction show.
Found this on Reddit. Enjoy the comments.
HTML5 and CSS3 present some exciting possibilities when it comes to web development. However, both are merely recommendations to the W3C and have not been officially adopted as a standard. In actuality, it could be years before they are officially adopted.
This presents a bigger problem for HTML5 than CSS3 when it comes to actually using them in a professional sense. While some of the better modern browsers do support HTML5, there is no guarantee that what gets built now will still render the same years from now, next month, or even tomorrow. Until it is adopted, the specs can change along the way.
However, there are elements of HTML 5 that can be used now, as they will degrade gracefully no matter what happens to the specs, and I do plan incorporating some of it in our sites moving forward. Apple, Google, Microsoft and others encourage developers to start using as much HTML as we can. It is especially useful when it comes to using their mobile devices. But on the other hand, the W3C is encouraging developers to NOT use HTML5 until there is a final version of the specification.
While in the same boat, CSS3 offers a bit more to play with. There are some very useful and nifty things that can be done with CSS3 now, and I do plan on implementing some into the sites that we build.
There has been a mentality shift in the web world about going from the graceful degradation approach to a progressive enhancement approach. Graceful degradation is building for the most advanced browsers and accepting the shortfalls of the lesser browsers as long as the content was “presentable”. Progressive enhancement is taking the “content is king” approach.
As defined by Wikipedia:
“Progressive enhancement uses web technologies in a layered fashion that allows everyone to access the basic content and functionality of a web page, using any browser or Internet connection, while also providing those with better bandwidth or more advanced browser software an enhanced version of the page.”
So in the spirit of progressive enhancement, I plan on implementing many features of HTML5 and CSS3 when and where they make the most sense.
Some HTML5 I plan using:
Some CSS3 that I plan on using:
Now is a great time to get used to some of these features. While it is not practical to go all out and implement full-on HTML5/CSS3 sites for our clients, it is a great idea to start implementing as much as can be supported. Our goal is to make our client’s content available to as many people as possible. That means making sure that it is readable no matter what device or browser a person may be using. HTML5 and CSS3 can both hinder and aid in that goal. It’s up to us to make sure we understand where that line is and to balance it to our best ability. Plus, we do not want to find ourselves playing catch-up when it is all finalized and fully supported, even if it will be 2022. ;)