some interesting stuff from the /. discussion on browsers:

  • #605 – running mozilla on old systems
  • #598 – why js sucks in practice
  • #407 – adhering to standards vs user agent enforcement
  • #16 – more platforms w/o browsers
  • #235 – some common sense
  • #42 – cute
  • #319 – interesting, if inflammatory and simplistic ;P
  • #84 – rudeness of redirects
  • #130 – web design in the real world
  • #183 – another reason to leave js off?

i just wanted to mention that my columnar css-only design preceded the browser upgrade campaign by about 3 months. waaay ahead of the zeitgeist. (but, as you will notice, with my friday night post, i am also without a life). for those just starting on css design, the css.nu pointers page is a good start.

the ala article has some neat workarounds for non-compliant browsers (the @import and css2 selectors are nice hacks – wait, didn’t they say they were gonna stop doing that?), but those looking for a better explanation of using floats to create columns, there’s a webreference tutorial on it.

while on the issue, i guess i’ve sorta figured out my apprehension at the whole upgrade campaign dealio. yes it’s a good thing, but the javascript forewarding is moronic. 1) 20%+ people have javascript disabled, 2)many of the people you’re targeting won’t have javascript anyway. the top of the page css-hidden warning is much better. i use a server-side one. oh, and for people who get stupid user-agent redirects, try proxomitron, a great tool.

um yeah, summarizing:
   separating presentation from content == good
   javascript auto-forwarding == really really moronic.

noticed that the latest issue of the la weekly has a cover story on the ca power problem (that took a bit a searching to find the permanent location… grr, bad design). it’s a better look than cnn’s rather superficial “in-depth special” (this took a while to find too. i saw it before but it didn’t show up in the searches…)

the online version of the la weekly is much less messy on the fingers (smudgy newsprint and all that).

wasp’s new browser upgrade campaign has a laudable goal. they don’t mention mozilla (not the same as ns6) or lynx (html 4.0 compatible), which is a huge disservice. the former because ns6 sucks, and the second because disregarding lynx rendering means disregarding accessibility. if it renders in lynx, it means it should display in html2/3 browsers, and it’ll work for disabled (blind, etc) people.

but you know, this is the kinda thing content/display separation and server-side template generation was supposed to solve.

if knownow makes it big, i can just see it bringing down apache 1.x servers to their knees (so many child processes, the horror, the horror). um 2.x would do better. and aolserver would do better too. actually, i’m sure that that’s the least of knownow’s worries once you take the riaa, the mpaa, and gov’t goons into account.

apologies for anyone who reads this blog for insight on internet trends and commentary: i believe i am out of the loop now. i don’t go through my daily net reading list regularly anymore (no time), and i’m not going to any of those swanky events (no money). not like the good old days ;P