LinuxTag program

Homepage: battery.rubyforge.org/

Download: rubyforge.org/frs/?group_id=268&release_id=531

 The Ruby Production Archive (RPA) will provide packages of Ruby
 libraries and programs in a form that allows production use, engineered
 through a stringent process resembling FreeBSD's or Debian's.

 rpa-base is a port/package manager designed to support RPA. Its scope and
 purposes are different to those of other systems like RubyGems.

 rpa-base 0.1.0 is now available on http://rpa-base.rubyforge.org .
 Please keep in mind that this is *not* a RPA release (that is, a release
 of the repository) but just a release of the rpa-base tool itself. We
 have provided several sample ports/packages for testing purposes, but
 they don't formally belong to RPA. Read below for information on the
 libs/apps packaged so far.

 rpa-base requires Ruby 1.8.1 (certainly 1.8 at least, it might work on
 1.8.0); it has been tested on several Linux distributions, FreeBSD and
 win32. We would appreciate feedback (both positive and negative) under
 those or any other architecture.

 It takes but a couple minutes to install and will allow you to do

 rpa install instiki ruvi

 ;-)
 (NOTE: ruvi, the cool pure-Ruby vim clone, won't work on win32)

 Features
 ========

 rpa-base is a port/package manager designed to support RPA's client-side
 package management. You can think of it as RPA's apt-get + dpkg. It
 features the following (working right now):

  * sane dependency management: rpa-base installs dependencies as needed,
    keeps track of reverse dependencies on uninstall, and will remove no
    longer needed dependencies
  * atomic (de)installs: operations on the local RPA installation are atomic
    transactions; the system has been designed to survive ruby crashes (OS
    crashes too on POSIX systems)
  * modular, extensible design: the 2-phase install is similar to FreeBSD and
    Debian's package creation; rpa-base packages need not be restricted
    to installing everything under a single directory ("1 package, 1 dir"
    paradigm)
  * rdoc integration: RDoc documentation for libraries is generated at install
    time (currently disabled on win32)
  * ri integration: ri data files are generated for all the libraries managed
    by RPA; you can access this information with ri-rpa (currently disabled on
    win32)
  * handling C extensions: if you have the required C toolchain, rpa-base can
    compile extensions as needed
  * unit testing: when a library is installed, its unit tests are run; the
    installation is canceled if they don't pass

(by Robert C. Martin; on <a href="www.artima.com">artima.com</a>) For many years we've been using statically typed languages for the safety they offer. But now, as we all gradually adopt Test Driven Development, are we going to find that safety redundant? Will we therefore decide that the flexibility of dynamically typed languages is desirable? http://www.artima.com/weblogs/viewpost.jsp?thread=4639

From the README:

Major features:

• Cholesky decomposition
• LU decomposition
• QR decomposition
• Schur decomposition
• Singular value decomposition
• Eigenvalues and eigenvectors of a general matrix
• Minimization by least squares
• Linear equation solving
• Stand-alone LAPACK bindings: call any LAPACK routine from directly from ruby.

Changes: Several bugfixes were made for the JIT compiler. A working Java-to-Smalltalk bytecode translator (which does not support networking and reflection yet) was added.

homepage download

German English

The last 20 years of the PC have been boring. PC vendors aim at businesses, who aren’t creative in their tool-use. They’re adults: they learn a system and stick to it. We should think about children. The printing revoltuion didn’t happen in Gutenberg’s day, it happened 150 years later, long after Gutenberg was dead, when all the pople alive had grown up with the press.

A small minority of Gutenberg’s contemporaries got the printing press, but it wasn’t until they were dead that the children who grew up with the press were able to put the ideas into practice.

James Licklieder: in a couple of years, human brains and computers will be coupled. It hasn’t happened yet. Except in science, where scientists and computers are indeed thinking as no human brain has ever thought before. .. craphound.com/kayetcon2003

 GM> Are there any accepted or already practiced ways for
 GM> companies to prevent Ruby source code from being read by potential
 GM> competitors? I can vaguely imagine redefining Ruby's
 GM> "require"-type methods so they can include zipped and passworded
 GM> ".rbz" files, say. Or using exerb (except for UNIX and without the
 GM> potential license issues).

 GM> I want to use Ruby at work but this is one of those "steps to
 GM> convincing your boss to use Ruby" I need to go through.

Just look at the "eval.c" file, i think the require is defined there and then write your hook. Or write a dll/so and add embedd your rb files as large c strings there (using maybe the "wrap" tool from the Fox Toolkit) and then do rb_eval_string("my c file"). After this protect the dll with something like "armadillo" (use google to find the URL). This works perfectly for me.

Original by Ronald Jeffries, translation by Aleksi Niemela and Dave Thomas. www.rubycentral.com/articles/pink/index.html

(Source: Avi Bryant) I came across Avi Bryant's blog. Tons of interesting stuff, especially about Seaside. http://www.cincomsmalltalk.com/userblogs/avi/blogView

 Ich habe mal ein erstes deutsches 3.7g zusammengestellt:

 http://www.iam.unibe.ch/~denker/Squeak3.7gDeutsch.zip

 Das ist einfach das letzte 3.7g Full Image + deutsche uebersetzungen.
 Die englischen Fenster habe ich geloescht, die engl. Demo-Projekte sind
 aber noch drin.

 Was wir brauchen ist

 -> Eine deutscher Willkommen-text
 -> ein paar deutsche Demo Projekte
 -> am besten ein deutsches tutorial...

 Bi den Einfuehrungs-texten sollten wir uns nicht an den englischen orientieren,
 die sind naemlich eher sinnlos, denke ich.

Smalltalk is very well thought out, extremely well engineered, very flexible, and generally gives quite good performance in a multitude of situations. It’s very adaptable to many different situations, and has lots of tricks up it’s sleeve. Driving it is a bit of a paradigm shift from driving your average plane, it has some new fancy controls, but once you get the hang of it, it can be totally amazing and really fun. Even if you don’t totally know what you’re doing you can still get yourself out of a jam. Given that you’ve got a good pilot you can launch off to a quick start and really do some very heavy and impressive damage in a very short time. It also tends to perform quite impressively if you’ve got a few of them around, and easier to coordinate an army of them.

Java is pretty difficult to drive, and once you get it going in a certain direction it’s pretty hard to get it going somewhere else. It has a few turbo buttons on it so that if you really know when and where to use it, it can fly pretty well. You can surely get it going really fast if you fly it high enough and then point it straight into the ground. It’s generally not very flexible and often a real pain to deal with, but overall once you’ve got a flightplan fixed in stone you can fly it reasonably well and run it reasonably efficiently. If you are meticulous in your planning and implementation, it can really deliver the goods. If you make some mistakes, things can go very wrong that may become almost impossible to correct. Don’t count on any big changes, quick maneuvers, or any sort of fancy tricks that just might save the day, and leave yourself a good bit of time for planning and implementation before you expect to be able to deliver the goods. If you come accross any surprise attacks or come up against an Apache hellicopter, you could be doomed.

This situation provides much of the motivation for our architecture, ERP5, which offers several advantages for business. All ERP5 tools are open source, so are free and have openly available source code that a business can change to suit its processes. ERP5 incorporates, from scratch, advanced concepts such as object-oriented databases, a content management system, synchronization, variations, workflows, and a method to model and implement business processes. ERP5 is also a Web site where researchers can share innovation on management techniques and their implementation through software.

In 2001, two companies initiated the ERP5 project: Nexedi, a Zope service provider in France (Zope is a well-known open-source application server), and Coramy, a European apparel manufacturer. They aimed to develop a set of ERP software components for small and medium-sized companies. In addition to source code, the project also produced educational material and a clearly defined theoretical model. To fit the needs of smaller companies, they also designed ERP5 for distribution across distant sites with slow and unreliable Internet connections.

link

Source: _why, yaml.freepan.org) YAML is extremely simple to learn. The basics are extraordinarily simple. You may even find that you have unintentionally used YAML syntax when building lists or simple file formats.

It also helps if you have experience with any agile language (such as Ruby, Python, Perl or PHP). YAML was designed to suit these languages well and borrows a few basic ideas from them.

And look at the clock before you start. Jot the time down and we'll see how fast you are. [http://yaml.freepan.org/index.cgi?YamlInFiveMinutes]