Why break an existing product while you build another? The features that set Reader apart from other feed readers are gone. Proper social features have been removed and replaced with +1 and share. When you look at the core users of Reader, what they actually do in Reader and what they want, this "update" is damaging.
I was waiting patiently for the ability to quickly and easily share to G+ from Reader. This addition works, although not very intuitively, but I'm glad to see it. However, I don't understand why the decision was made to remove all other social features.
Reader is about quickly consuming large amounts of data from feeds and (what set it apart from other feed readers IMO) other users can share an article with an optional comment inside that rapid data consumption environment. I no longer have a way to share and consume only articles without using a 3rd party product. I use G+ for social, not rapid consumption, there's waayy too much noise for that. Simply put, I don't have conversations in the middle of reading, I have that conversation after I finish reading. Unless a public stream can be split into its own circles, tags, wtf-ever, noone can have a public stream of only articles while using G+, unless that's all they use it for.
I suppose I could find a (non-standard) way to get a feed of someone's +1's, but this only gives me public shares with no comments. I most certainly can't get a feed of a private circle. There are no good options, aside from a 3rd party product. Feeds of private circles, tagging or circles for the public stream, or something far better, that you or I haven't even thought of, will probably happen one day, but as I already said, why break a working product while you work on another?
You can always use Twitter thanks to a cool web app by @benguild that finds the Twitter account associated with your favorite feeds.
While this probably isn't a proper replacement anyone looking for a new reader will use, it is a nice tool for finding your favorite authors and sites "official" accounts.
For certain cases, I rely heavily on data-* attributes in span elements that will possibly be reassigned and definitely reformatted several different ways. This feels like the wrong way of doing things, specifically when you have several of these elements wrapped in a parent span to provide styling, etc. There's plenty of good arguments for (or against) data, but that's how it immediately applies to me. The data element feels better, it's more semantically correct and all that, good stuff from my perspective.
However, removing time is horrible for anyone looking for a standard representation of interpretable time data without having access to the microdata schema used by the developers. Unless there are standard datatypes in the HTML5 spec via a type style attribute, data will only encourage non-standard, "wrong" implementations and general misery. Expecting developers to automatically use schema.org, or relying on them to document their interpretation of time for anyone tasked with maintenance (let alone making that documentation public), seems rather naive.
I like the creation of the data element, but removing time without coming up with a suitable replacement seems counter-productive to the direction HTML5 is supposed to be heading.
- Main Light IndustriesWeb Designer/Developer, 2010 - present
- Atlantic Water Products2004 - 2010
- Lake Forest High School
- Greenwood Mennonite School
- Acorn Christian Academy
Feedly. A fast and stylish way to read and share the content of your fav...
Introducing the New Feedly. Browsing, reading and sharing your favorite sites has never been this easy, fast and rewarding. Feed your mind a
A List Apart: Articles: Responsive Images: How they Almost Worked and Wh...
It's our job, as designers and developers, to pick apart even the seemingly most simple tasks to find ways to improve them. When Ethan M
Google+ Gives the Gift of Unlimited Picasa Storage
Picasa is limited to 1GB of storage (unless you pay up for more Google bytes) but now there's a free workaround. You can upload unlimited ph
andyMatthews.net - ThemeRoller! Styling jQuery Mobile apps has never bee...
Andy Matthews is a talented web and application developer living in Nashville TN. He has over 12 years of experience in graphic design, prog