Amazing video. I want one!

This morning I watched Kevin Kelly’s "The next 50 years of science".

The scientific method which provides us with so many … all technological goodies does not resemble the science of 1600. Ever since Bacon, science has undergone a slow evolution.

Landmarks in the history of the scientific method are the invention of libraries, indexes, citations, controlled experiments, peer review, placebos, double blind experiments, randomization, and search among others. At the core of the scientific method is the structuring of information.

In the next 50 years, as the technologies of information and knowledge accelerate, the nature of the scientific process will change even more than it has in the last 400 years. We can’t predict what specific inventions will arise in the next 50 years, but based on long-term trends in epistemic tools, I believe we can speculate on how the scientific method itself — that is, how we know — will change in the next five decades

 Joachim Tuchel wrote:
 > >> ... Why on earth does it seem everybody believes that JBOSS or any EJB
 > >> environment will scale with no limits? After all, it's a bunch of Java
 > >> classes running in a JVM, just like seaside is a bunch of SMalltalk
 > >> classes runnung in a Smalltalk-VM....

 Andre Schnoor answered
 Marketing. The right buzz words and false promises within a perfect
 > opportunity window in history - and there you are. If something is new (I
 > mean so new that nobody can actually grasp it), hype and buzz sometimes
 > work like religion: You believe what you want to believe. You find
 > yourself spreading the word before you actually had a look at it. Suddenly
 > there are 5 million people chiming in, while only a mere 0,05% of them
 > really know what they are talking about. The big bang of myths.
 >
 > I ran rather large sites with 8 million+ monthly visitors and 7-8
 > Terrabytes of bandwith on a single 4 CPU Sun. Others required 16 Suns for
 > less traffic. It mostly depends on your database model and how frequently
 > users interact with content that is compiled "live" (not cached). The
 > basic application scripting doesn't account much to it.
 >
 >  From the perspective of a classic software engineer (and with an extra
 > bias towards German "Gruendlichkeit"), web technology in general is a huge
 > pile of complicated, heterogenous, incredibly expensive and annoying crap.
 > All that in-band signalling, all those stone age protocols and character
 > sets, quick & dirty hacks, spaghetti scripting,
 >   what-happens-next-machines ... think about how incredibly *ugly* this
 > network actually is  ;-)
 >
 > Seaside looks like a very beautiful and innovative thing. You should give
 > it a try.
 >
 >

.. Largo Argentino ..

.. and here are the top ten lies of venture capitalists.

Marcus Denker’s Seaside talk from 22C3 is available as video now: events.ccc.de/2006/04/21/gentlemen-fire-up-your-clients/

The file is called 22C3-599-en-seaside_squeak.mp4 (almost an hour, 346 MB).

The image used (This contains all slides as Squeak Projects): www.iam.unibe.ch/~denker/talks/22c3.zip "Slides" as pdf (e.g. for printing): www.iam.unibe.ch/~denker/talks/22c3.pdf

 gem rdoc --all

Then start the gem server

 gem_server

When will I next be in Italy? :-).

On debian:

  apt-get install puf

puf is one of these great commandline tools that one simply loves!

www.dezwozhere.com/links.html

www.meyerweb.com/eric/writing.html

www.mezzoblue.com/zengarden/resources/

www.meyerweb.com/eric/css/edge/

# convertEnronEmail

 #!/usr/bin/perl -0p
 s/^M//gsm;
 ($date) = /^(Date: [^\n]+)/sm;
 ($from) = /^From:\s*([^\n]+)/sm;
 print "From $from @{[scalar localtime]}\n";
 s/\Z/\n/;

#enronEmailsForKeyword

 #! /bin/sh
 mdfind "kMDItemTextContent == '${1+"$@"}'" | grep /enron/

#enronGrep

 #! /bin/sh
 enronEmailsForKeyword ${1+"$@"} | xargs grep ${1+"$@"}

#enronMailBoxForKeyword

 #! /bin/sh
 enronEmailsForKeyword ${1+"$@"} | xargs -n+1 convertEnronEmail

#enronThreadForKeyword

 #! /bin/sh
 enronEmailsForKeyword ${1+"$@"} | xargs cat

A big thanks to Andreas for the new logo.

The logo reminds me of the "Blub Blub Spinat advertisement by Verona Feldbusch", but you probably do not understand that joke if you are not German :-).

New features:

• Simple Excel export
• Simple adding of historic data
• Simple editing of existing data

The focus right now is on bug fixing and improving the design before we continue to add more features.

As usual enjoy it and make sure you send me any feedback, esp. bugs and wishes.

Getting started:

• Get a free account.
• You book your time on accounts. So setup tasks (accounts)

The general structure is client.project.task. The client might be IBM, the project might be XRT and the task might be design. Then you can add t asks like IBM.XRT.testing, which would mean a testing task.

This client.project.task structure has the advantage that it makes it easier to run more complex reports on the data. How much data we do for client X? How much did we do on project Y?

Here we create the client BMW with project RoR and task design. If the client already exists, only the project and the task are created. If the client and the project exist, only the task gets created.

You can add tasks only to existing client.project.task combinations, but by entering IBM.XRT.testing, you automatically create the client IBM, the project XRT and the task testing if they did not exist before.

Starting/Stopping task

Enough! Some people got work todo! OK, it’s as simple as a cd-player. Press the start and stop button.

Task not running

Task running

This client.project.task structure has the advantage that it makes it easier to run more complex reports on the data. How much data we do for client X? How much did we do on project Y?

Enjoy timesummer, and please use the forms on the site to send us feedback.

 Changes for RoR
 ---------------
 * Works with rjs templates.
 * Add methods to change the error message dialog(?) title/explanation.
 * Bugfixes.
 * Added GetText.Nn_().

rubyforge.org/projects/gettext/

• Creates a Colorful Chart of a Webpage’s Rendered Source Code
• Displays Source in its Altered State After the DOM has been Manipulated by JavaScript

Source charting …

• Clearly Defines Nested Containers
• Easy Way to Identify Structure and Hierarchy
• Great Visual Aid Tool for Learning Environments
• Intuitive and Efficient Way to Analize Source
• Dramatically Enhances Your Debugging Capability