Live data from Hacker News

Old TechCrunch + really fast, clean, customizable layouts

tcfast.com

41–50 of 72 posts

Re: Old TechCrunch + really fast, clean, customizable layouts

#42

Earlier quoted context omitted.

It'd be a sort of interesting legal issue if they got sued. Using the name 'tcfast' might be problematic. But what if it was a more general web-based RSS reader that reformatted any RSS feed into pages like this? If that's illegal, where's the line between that and Google Reader?

Google Reader is used for the private consumption of public RSS feeds but this republishes content.

OK, what about popurls[1], alltop[2] and the like?

1. http://popurls.com/ 2. http://alltop.com

Re: Old TechCrunch + really fast, clean, customizable layouts

#44
post #42

Earlier quoted context omitted.

Google Reader is used for the private consumption of public RSS feeds but this republishes content.

OK, what about popurls[1], alltop[2] and the like? 1. http://popurls.com/ 2. http://alltop.com

Those don't republish content, they post headlines and links to the original sources.

Re: Old TechCrunch + really fast, clean, customizable layouts

#46

Earlier quoted context omitted.

>That way, when users hit Ctrl-+ to override a site's smaller-than-the-browser's-default font size, the site will show about the same amount of text on each line, rather than producing narrower lines as the font grows. That is stale 2008 advice. Every browser but ie6 uses zoom to resize pages. Text is resized on ctrl-+ regardless of px vs em. The days of sizing things with em's is long over, and these days it is coun…

Text is resized, but not necessarily content. Also note that that behavior is configurable in several browsers, including Firefox, for people who don't want to have to choose between reasonably sized text and crisp non-fuzzy images. Also, many browsers that support zooming don't necessarily let that zooming override a size specified in px. In any case, why would specifying the width of a column of text in em be "coun…

In addition to jcampbell1's remarks, which are completely correct, the zooming override issue you mention is, in my experience, nonexistent. I may be wrong, but I have not recently* encountered it on FF, IE, Opera, nor Chrome.

Em sizing is counterproductive because 1. That's not how most designers think, (We use Points, Pica, and Pixels.), 2. It's unnecessary for scaling with normally configured browsers, and 3. If someone changes their default type size, I am NOT going to support them: they have full knowledge of how to change the setting to fix a suboptimal page, and they have chosen to have suboptimal pages in the majority of their browsing (You think leading and optimal line width don't matter just as much as text size?) To anyone who actually forces their typeface choice: please do so on a site-by-site basis--or at least typeface-by-typeface for those you find illegible. Please do not try to override the informed choices of typographically-aware designers.

Sorry if that sounded like a rant. :) I'm a designer, and I'm passionate about my work being displayed and read the way I designed it to. Otherwise, I'd give every user a typeface selection screen when they visit my websites. The fact is, average users don't make informed choices.

*Within the past three years.

Re: Old TechCrunch + really fast, clean, customizable layouts

#48

Earlier quoted context omitted.

Text is resized, but not necessarily content. Also note that that behavior is configurable in several browsers, including Firefox, for people who don't want to have to choose between reasonably sized text and crisp non-fuzzy images. Also, many browsers that support zooming don't necessarily let that zooming override a size specified in px. In any case, why would specifying the width of a column of text in em be "coun…

In addition to jcampbell1's remarks, which are completely correct, the zooming override issue you mention is, in my experience, nonexistent. I may be wrong, but I have not recently* encountered it on FF, IE, Opera, nor Chrome. Em sizing is counterproductive because 1. That's not how most designers think, (We use Points, Pica, and Pixels.), 2. It's unnecessary for scaling with normally configured browsers, and 3. If s…

The web isn't print, it was never meant to be. The content you publish online is going to be displayed on any number of devices at various resolutions, scales, window sizes, colours, etc.

If you're a web designer, keep in mind that you're displaying content that's useful beyond the artistic merit of the typeface and other decorative elements. If you want to show off a design, make a PDF or an image. If you are making content useful to the widest audience you can reach, there are compromises that have to be made.

Re: Old TechCrunch + really fast, clean, customizable layouts

#49
post #48

Earlier quoted context omitted.

In addition to jcampbell1's remarks, which are completely correct, the zooming override issue you mention is, in my experience, nonexistent. I may be wrong, but I have not recently* encountered it on FF, IE, Opera, nor Chrome. Em sizing is counterproductive because 1. That's not how most designers think, (We use Points, Pica, and Pixels.), 2. It's unnecessary for scaling with normally configured browsers, and 3. If s…

The web isn't print, it was never meant to be. The content you publish online is going to be displayed on any number of devices at various resolutions, scales, window sizes, colours, etc. If you're a web designer, keep in mind that you're displaying content that's useful beyond the artistic merit of the typeface and other decorative elements. If you want to show off a design, make a PDF or an image. If you are making…

The thing is, type isn't decorative. It's integral to the presentation of content. [Good] designers know how to make type legible and readable, as well as appealing, to the greatest number of people. I'm not talking about preserving type in syndicated content, just in the original format. Good designers also know how to present content in a way that is effective on a variety of platforms.

Re: Old TechCrunch + really fast, clean, customizable layouts

#50

Earlier quoted context omitted.

Text is resized, but not necessarily content. Also note that that behavior is configurable in several browsers, including Firefox, for people who don't want to have to choose between reasonably sized text and crisp non-fuzzy images. Also, many browsers that support zooming don't necessarily let that zooming override a size specified in px. In any case, why would specifying the width of a column of text in em be "coun…

In addition to jcampbell1's remarks, which are completely correct, the zooming override issue you mention is, in my experience, nonexistent. I may be wrong, but I have not recently* encountered it on FF, IE, Opera, nor Chrome. Em sizing is counterproductive because 1. That's not how most designers think, (We use Points, Pica, and Pixels.), 2. It's unnecessary for scaling with normally configured browsers, and 3. If s…

I have enormous respect for designers, and I know full well that I, a programmer, can't do what you do and that anything I might produce that puts pixels on a screen benefits immensely from a qualified designer's input. That said, those are poor arguments.

1. Tough? Learn to think better. What would we tell a programmer who doesn't want to use recursion because they "think in loops"? What would you tell a carpenter who didn't want use screws to put your new furniture together because he "thinks in glue"? Units of measure are a tool, and your facility (or lack thereof) with a tool doesn't affect how good it is.

2. I actually admit to some ignorance about browser scaling algorithms, so you may be entirely right here. In any case, I think it's the least important of the issues at play.

3. I submit that it's more important to make sure that your users can use your websites in a way that's comfortable to them, rather than that they should be able to bask in the glow of your unsullied brilliance. I don't mean that I should be able to randomly change fonts around because today I like Georgia and tomorrow I'm going to like Chicago. I'm wondering what happens when your site suddenly starts getting traffic from Israel, and all your new users are using Google Translate to turn it into Hebrew. Not only do your font choices go out the window, but all your ragged right just became ragged left, and some page elements may have have spontaneously rearranged themselves. (See http://translate.google.com/translate?js=n&prev=_t&h..., for example.) Or what if some of your users are colorblind or elderly or dyslexic, or just have trouble reading your type selection for any of a myriad of reasons? Is it more important that your design should remain just how you like it, or that they should be allowed to read it? Before you answer, read this: http://tigerbeatdown.com/2011/07/14/harry-potter-and-the-oh-... It's not about web accessibility, but the major themes are still there.

One of the incredible things about the web is that not only do we have the power to make the content we're producing available to an extraordinarily diverse population, we have the power to make it so that they can all read it in a format that works for them, as individuals. When you have to design a poster that's going to get sent to a printer and plastered over bus stops, everyone waiting all over town is going to see the same poster. When you design a web page, everyone who sees it gets a separate stream of bytes and a separate display to see it on. Why not let each user find the best web page for them, instead of forcing them all to see the best web page for you?

Post reply on HN