aboutsummaryrefslogtreecommitdiff
path: root/content/posts/2003-11-22-expos-eacute-amp-retooling-slashdot.html
blob: f373baf787a06117e3a851c60bb443e2d5e29e74 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
---
date: "2003-11-22T17:58:49Z"
title: Exposé & Retooling Slashdot
---

<p>
I played with <a href='http://www.apple.com/macosx/'>Panther</a> a little earlier today at <a href='http://www.microcenter.com/'>Microcenter</a>.   <a href='http://www.apple.com/macosx/features/expose/'>Expos&eacute;</a> is pretty damn cool, although it's of negligible value to me, since I already <a href='/screenshots/'>avoid overlapping windows like the plague</a>.  There's something really gratifying about having MacOS, bash, and <a href='http://www.ruby-lang.org/'>Ruby</a> all on the same machine.
</p>

<p>
Oh yeah, <a href='http://people.debian.org/~ljlane/'>Laurence (ljlane)</a> pointed me at this page: <a href='http://www.alistapart.com/articles/slashdot/'>Retooling Slashdot with Web Standards</a>.  Making this change would save <a href='http://www.osdn.com/'><acronym title='Open Source Developers Network'>OSDN</acronym></a> a lot of money on bandwidth, but <a href='http://www.richlowe.net/'>Richard (richlowe)</a> pointed out this will render <a href='http://www.slashdot.org/'>Slashdot</a> essentially unviewable in <a href='http://lynx.isc.org/release/'>Lynx</a> and <a href='http://artax.karlin.mff.cuni.cz/~mikulas/links/'>Links</a>.  Personally, I'd say that's the price of progress.  <a href='http://lynx.isc.org/release/'>Lynx</a> is crap anyway.  <a href='http://artax.karlin.mff.cuni.cz/~mikulas/links/'>Links</a> , on the other hand, already supports tables and frames (some forks also support JavaScript), so there's no reason they couldn't add rudimentary <acronym title='Cascading Style Sheets'>CSS</acronym> support as well.
</p>