Re: Strong typing and Type Safety.A multilanguage approach

Replies are listed 'Best First'.
Re^2: Strong typing and Type Safety.A multilanguage approach by ww (Archbishop) on Nov 19, 2010 at 21:56 UTC
OT: but there is a lot of research supporting the proposition that lines of 60 chars or fewer are easier to read (comprehend) than lines approximating the kind of max lengths those newfangled browser-things can render. ;-:)	[reply]
Re^3: Strong typing and Type Safety.A multilanguage approach by mr_mischief (Monsignor) on Nov 21, 2010 at 09:52 UTC
There is indeed lots of research showing what makes something easier to read. Then there's also recent research showing that making text more difficult to read can make the content of the text easier to remember. That's not definitive work yet and it had to do with the fonts used rather than page layout in general, but it's worth consideration. Maybe in page layout as in Perl TIMTOWTDI. Of course, there are myriad wrong ways, too.	[reply]
Re^3: Strong typing and Type Safety.A multilanguage approach by Anonymous Monk on Nov 20, 2010 at 02:14 UTC
FWIW, I doubt in that research the 60 chars of content were squeezed by 50/100 chars of advertising from each side respectively (squeezed, because there is hardly any whitespace around the content)	[reply]
Re^2: Variable browser width (not: Strong typing ...) by tye (Sage) on Nov 20, 2010 at 03:47 UTC
that can render text on screens wider [...] and you don't even have to know how many pixels when you write the text! Oh, you are so stuck in the pre-CSS web... I bet you also think that text should never overlap confusingly or be cut off at the edge of the browser with no scrollbar to let you see the rest of it. That's so last decade! I mean, who needs to be able to read all of the text on every page when the display elements can have... gasp round corners!!! squeal - tye	[reply]