Conditional Statements ... is the field in which PPL really scores over all other programming languages. Whereas other languages only offer a generalised IF-THEN-ELSE or a CASE statement, PPL has a whole class of utterly novel wish-fulfilment statements. For example...
IF x WAS_EVER 100 THEN
DON'T print(x)
IF j IS_NEARLY right
DELETE ALL INCORRECT
REFERENCES TO j
UNLESS a IS "My Name" THEN
crash_unix
WHENEVER errors THEN
run_in_circles_scream_and_shout
ON_SUSPICION_OF x < 100
CORRECT ANY OTHER
REFERENCES TO x
IN_CASE y NEARLY x THEN y
REALLY x
onLine weblog archive
Saturday, January 19, 2002
Friday, January 18, 2002
My take on it? CSS does not benefit from this limitation issue because the limitations do not deal primarily with the medium (the CSS 'vocabulary' itself, although in the case of CSS1 and to a lesser degree CSS2, that is the case), but we're talking about bugs. Annoying, annoying bugs.
Thursday, January 17, 2002
Two pairs of researchers try to discover the ideal number of links per page. They learn that sites perform better when visitors don't have to dig too deep.
W3C Recommendations Reduce "World Wide Wait"
SCS - Life on the Bleeding Edge
and of course, the seminal David Siegel piece, The Balkanization of the Web (complete with page titles buried in image files).
Newspaper writing is full of "indirection," and may be one of the primary reasons readers struggle with or turn away from newspaper stories. An awareness of the damage indirection can do in a story should be part of every writer's and editor's set of language skills.My wife, married to me for these last seven years, would probably enjoy this article, but she does not read glish.com :(
After browser vendors have stepped it up and given us much of the control we've been asking for, I can't seem to find web designers that are exploiting these new found powers. Everyday I see a tremendous amount of visual experimentation using web technologies other than CSS ... What I long to see is a move to embrace standards based web technologies in similar efforts...Now, while I do think these are valid questions, I think Chris might be looking at CSS design a little askew. I quote again:
What will it take to get people to seriously consider CSS based designs as viable outlet for their creative endeavors?
"structural integrity is only one benefit [of CSS] ... can we do something more then make our content sites more readable?"See, I think those two things (structural integrity, increased accessibility) are at this point in the game the only real reasons to switch to CSS. Frankly, browser implementations are still too disparate, too broken, to allow for the creative explosion Chris is asking for. And in large part because of these limitations, the people that have chosen to eschew tables and embrace CSS and standards-based web design are not the crazy-ass designers, who are elsewhere, doing other things, while only the geeks like you and me spend time listening to arcane arguments about markup and indirection and style sheets and trying to change the web in fundamental, but not primarily visual ways. We tend to be sympathetic to concerns about usability, interested more in making our content accessible than in exploring the design options CSS offers.
But then, on the other hand, I remember some comments from Zeldman on the 5k contest: "Limitations are the soil from which creativity grows." And from Stewart: "Since the space we have to explore is so small, we have to look harder, get more creative; and that's what makes it all interesting.". You'd think what was true about the 5k contest would be true about CSS design too, that people would find interesting little crannies in the tight design confines that CSS imposes. But that doesn't appear to be the case.
So yeah: what he said.
Wednesday, January 16, 2002
This is a web site for commentary, essays, etc., from David P. Reed, Bob Frankston, and some of their friends. It was initially set up and maintained by Dan Bricklin.Thanks Ev.
What does HTML mean to you? You've probably never thought about it... Maybe you've seen it affixed to the tail-end of a Web address. Maybe you've heard it mentioned in a tech column. Well, what does it sound like? That's right, HTML is the abbreviation for Hotmail, Microsoft's Web-based email system.
Perhaps not directly related to css, but this is the one that made me see the light:
RFC 1958
B. Carpenter, Editor
June 1996
Architectural Principles of the Internet
Especially this bit: "3.6 Modularity is good. If you can keep things separate, do so."
{ makes for a good mantra }
{ close your eyes & repeat as needed}
-- see also --
Tim Berners-Lee
Principles of Design
-- for something less tech see --
Packet/Simson Garfinkel
Deliver Us from Tables
-- For an early counter argument try --
Jukka Korpela
Why style sheets are harmful
I work as part of a federally-funded Webteam for a prestigious laboratory in the states. It has recently come to my attention that our government has placed a burden on us. Congress passed the Rehabilitation Act back in '98 which instantiated a committee to ensure that all federal technologies do not treat those with disabilities unfairly. This board released a set of standards that they created to ensure that the government doesn't violate the Rehab Act. This, although wonderful for the disabled, leaves many of us media lackeys at these federal facilities with a bit of a conundrum. How do we fix all this stuff within 6 months? Our site has thousands of pages that would need to be sorted through by hand and even with us abandoning all projects for 6 months, we would not be able to guarantee all pages to be fixed. I know our team isn't the only one with this problem, so I was wondering if you guys have any good ideas on how to go about changing our site, our videos, our presentations, and pretty much anything else that relies on one sense over another. We would prefer to avoid using the 'Undue Burden' clause as much as possible.Now there's a case for ridding your site of tables and font tags.
When I see any Web site claim to be only readable using particular hardware or software, I cringe - they are pining for the bad old days when each piece of information need a different program to access it.And por favor, if you have not read Owen's own Design Rant, please do so now for a great case for device independent markup with CSS style and layout.
On the 13th of each month we'll be profiling a leading member from the web design community, releasing a range of useful tutorials and much more. We aim to provide a learning resource that will inspire you to produce good looking, intuitive, dynamic and powerful websites that degrade gracefully whilst supporting w3c specified recommendations.Check out the Beziér Curves & DHTML tutorial.
Tuesday, January 15, 2002
Monday, January 14, 2002
The bottom line is: DHTML is dead for serious application development; browsers, as application delivery platforms, are past their peak; and the future of distributed, interactive applications--at least on Windows--belongs to .NET. If you're developing these types of applications and you're not learning .NET, you may want to rethink your career plans.after the Microsoft poll rigging BS of last week?
...the method of authoring DHTML is changing. Or will soon. We used to ignore structure, accesibility, and degradability in favor of functionality. But that is going to change. In the future our DHTML will live on top of structure the same way that CSS style does. This will allow it to remain accessible while providing enhanced functionality.I say: right on. Coming is the day when we won't talk about degradeable code anymore, but instead we'll be writing "augmentable code": structurally sound markup with functionality added via EcmaScript and the DOM.