161–170 of 209 posts
This is great. The large scrolling format (similar to pinterest) is a good idea as the last thing that was needed was something that looked like reddit or HN. Sites like the Daily Mail have been very successful with this style. Good luck to the new Digg team!
Earlier quoted context omitted.
A tag would suffice.
This is what I do. Most of my stuff degrades gracefully, but for the few things which can't (JS demos/game things), I generally do something like this: example.com is a HTML5/ES5/CSS3 3D graphics demo. Unfortunately, your user-agent doesn't seem to support ES5, sorry about that.
Earlier quoted context omitted.
I'm tired of having this argument over and over again, so let's approach this Javascript issue from a different angle: It is bad practice to couple content (the "what") with functionality (the "how"). The content itself should not depend on how it is displayed. From an engineering standpoint, this makes your code unmanageable and unmaintainable in the long run. These stupid shortcuts of forcing users to have Javascri…
There are certain design elements that translate into a single line of JS, but require a couple of pages worth of CSS voodoo. Guess what's more maintainable.
Earlier quoted context omitted.
I'm tired of having this argument over and over again, so let's approach this Javascript issue from a different angle: It is bad practice to couple content (the "what") with functionality (the "how"). The content itself should not depend on how it is displayed. From an engineering standpoint, this makes your code unmanageable and unmaintainable in the long run. These stupid shortcuts of forcing users to have Javascri…
There are certain design elements that translate into a single line of JS, but require a couple of pages worth of CSS voodoo. Guess what's more maintainable.
Earlier quoted context omitted.
You are free to believe that. But let us say I want to cater both to you and to another user that browses the web with NoScript (assume it is my goal to cater to as many users as possible). I have two options: A) make the layout accessible without JavaScript B) break the layout without JavaScript. Only with option A do I cater to both of you -- Regardless of deliberate breaking or bandied opinions ("Thou shalt never…
>assume it is my goal to cater to as many users as possible The thing is, it's not your goal to cater to as many users as possible. It's your goal to optimize your ROI on development time. The reason we have to have laws about accessibility is that your average fast food place knows that wheelchair-bound hamburger sales will never make back the cost of constructing a wheelchair ramp. The economics of the situation wo…
Earlier quoted context omitted.
Criticisms about not including microformats and schema.org is super nitpicky.
I was listing stuff that made me a bit scared, as I browsed the source, not stuff to criticize the website with. As for criticism: I think the design and social integration is fresh and well executed. I make websites that contain more errors and look worse than that. It is more of a web application, than a web site. I listed MicroFormats, because: As a foundation for a modern website, it is a great idea. Digg has the…
Earlier quoted context omitted.
Apart from all the old pages being 404 (which is a huge mishap). Nitpicking on html is a fun and amusing pastime, but unless the page is deformed in some way, it falls into the "shit nobody cares about" category.
It falls into the "shit that will bite you in the ass one day" category. It's about engineering quality, and it goes all the way down to the stuff we don't see. Given Digg's history, it's a bit of a red flag. However, it all depends on how this technical debt is managed. If this is an alpha release under the heading "release early, release often" and the tech debt is known, there's nothing alarming about it. But if t…
In fact, I think these nitpicks are an excellent sign for digg. They discarded anything which was useless for their launch. Very well done - an excellent MVP.
Earlier quoted context omitted.
There are certain design elements that translate into a single line of JS, but require a couple of pages worth of CSS voodoo. Guess what's more maintainable.
So we compensate for a lack of CSS libraries by mixing presentation layer with content layer. Nice.
Abstarting things for the sake of abstracting is a rather naive approach. It's a good starting point, but some abstractions complicate things way beyond what's needed.