Postscript #1: The Bush tax cut
The Wall Street Journal asks about the Bush Administration's new tax initiatives: "Is [Bush] too eager to cut taxes for the rich? Or are his critics so eager to soak the rich that they'd settle for a smaller economy with less for all?" (1/2/03). Elsewhere, the issue has been framed as a choice between growth and jobs and--class warfare. But one may argue that the most stimulative tax break is one that mainly benefits working class and middle class people--because these groups would spend most if not all of the money gained through a tax cut, while the rich would primarily increase their savings. What do you think?
96% of income taxes are paid by the top half of the income distribution, and over a third are paid by the top 1% of the income distribution. The left has created somewhat of a Catch-22 in this country. The income tax structure is so progressive that only the rich pay any significant income taxes, and then the left opposes any income tax cuts because they benefit only the rich; taking their argument seriously would eliminate tax cuts as a potential policy instrument, even if they would significantly increase economic growth.
Examples of centres: a centre to represent those unfairly excluded from the main advogato centre, for whatever reason.
First answer, to question #3: mglazer rated all of their diary entries at 1; incidentally he also rated the diary entries of ladypine, moshez, shlomif, nixnut, and ChrisMcDonough at 10. Congratulations to bgeiger who got it. I think it is reasonable to assume that mglazer is not interested in reading any criticism of his anti-arab hate campaign.
FORTRAN, LISP, Algol 60, CPL, GPM, PROLOG, the UNIX shell, APL, Forth, Janus, Smalltalk, Scheme, ML, FP, Occam, Elephant 2k.
Does anyone think these are not right, or have other suggestions for this list?
Postscript This diary entry:
#dialect C gnu-cpp linux-style
dialect python lexical-scope indent-4-spaces
case-sensitive-ids scheme48-package multiline-comments)
* @dialect java sun-codeconv gcj-code
I think having a reasonably coherent, cross-language, machine readable set of conventions for indicating the dialect of a source text is useful, particularly for allowing syntax-directed editors to reliably determine how to format program text, and to figure what identifiers are introduced and how they are used.
An issue is: should dialect directives extend the language? My opinion is they should, since they could be used to influence the semantics of the program, but they should be permitted to occur in comments, so ensuring backwards compatibility.
Another issue concerns UNIX #! directives; see SRFI 22: Running Scheme Scripts on Unix for some discussion of important issues here.
I'd like to write an advogato article about this, probably in a couple of weeks time, but I have to hammer down a few ideas first. In the meantime I am interested in any comments or references to similar ideas.
Web based proof exchange systems:
I am still very enthusiastic about raph's work here, although I am disappointed he has used python for the implementation. Apart from that, I think raph's writings show excellent taste and insight. What I think he has got right:
There have been lots of interesting comments appearing on recentlog, but I've not had a chance to write any responses. I'll try to do this in the next few weeks.
Nice series of articles on windows and its free rivals. Just a little point: just because POSIX specifies a file system that doesn't support interesting permissions models doesn't mean that linux and FreeBSD can't: both of the have VFS layers that allow them to do just this sort of thing.
Wishing all advogatans a Happy New Year!
Can you put a price on heroism?
Yes! And you can manage it sensibly or wastefully too! I've been growing irritated with the Economist over recent years (since the departure of Rupert Pennant-Rea, I think...), and I hardly buy it anymore, but the occasional article like this one keeps me checking the website...
There's an article by Thierry Coquand, A new paradox in type theory that gives a good explanation of Reynold's argument that polymorphism is not set-theoretic. I think this goes some way towards making important ideas about the nature of the polymorphic lambda-calculus accessible purely through online references, though a lot of important references are from the 70s and 80s and would benefit from good online summaries. I'd be grateful to hear of more references. BTW mail sent to firstname.lastname@example.org will get to me, I'm quite happy that my main email address has been lost from the internet, since I don't have to spend so much time deleting spam...
jameson: Were you in Thomas Streicher's group when you were at Darmstadt? Who are you working with at Boulder? Despite my reservations, Girard's book is already something of a classic: I don't think you would have any problems convincing the librarian to try to get a copy.
Postscript: The last `Communications of the ACM' issue has as it main focus an event that I think will prove to be of great importance to computer science: The ACM has rejected licensing of software engineers essentially because code construction is not a normal engineering task. Interesting also in this light is Phil Greenspun's article reflecting on management at Ars Digita. Conclusions? I don't think software will *ever* be a `normal' engineering discipline, the way that civil engineering is today. I do think that the `Wild West' nature of the disipline will not last, however, because I think that in the next <n> decades it will become feasible to construct large systems that are proven to satisfy a formal specification.
New HTML Parser: The long-awaited libxml2 based HTML parser code is live. It needs further work but already handles most markup better than the original parser.
Keep up with the latest Advogato features by reading the Advogato status blog.
If you're a C programmer with some spare time, take a look at the mod_virgule project page and help us with one of the tasks on the ToDo list!