Slashdot Mirror

After 7 years, I suspect this covers the entire Perl6 development team too.

I can't tell if your comment here is supposed to be approving perserverence or chiding stubborness, but in any case, the perl 6 development effort has achieved some notable successes over the years (and few, if any, members of the team have been working soley on perl 6...).

Off the top of my head:

• Many Perl 6 concepts were implemented as perl 5 modules, and some have become core features in perl 5.10
• Pugs: reference implementation of perl 6 implemented in haskell
• Perl 6 on Parrot (now called Rakudo continues to progress...
• Simon Cozens is impressed with the state of the Parrot Compiler Toolkit: "Parrot lets you implement your own languages using Perl 6 rules for the grammar and Perl 6 for the compiler."

legal purchase of guns is far from anonymous. but regardless the real problem of the 2nd amendment as a failsafe is no government is going to wake up one day and say "thats it, all rights are now null and void". they will (yes i'm aware present tense would be more appropriate) use 'salami tactics'http://blog.simon-cozens.org/post/view/111 5to erode rights bit by bit so theres no real time when there's a consensus to rise up. well, at least by then it'll be far too late. the people who would pose a major threat will be long gone.

I worked for Pacific Press Service in Tokyo developing photo copyright and library tech until 94. I first saw a photograph search engine developed by Fujitsu around 92-93 I believe. It required the user to draw the type of image composition very roughly with a mouse and paintbox. So you would draw a horizon line, fill the bottom with blue and draw a yellow circle above if you wanted photos of the sea and sun. No wavelets at that time.

I then corresponded briefly with Ingrid Daubechies of AT&T who brought wavelets to the U.S., and was kind enough to send some of her papers. Wavelets are neat because it is like getting a paintbox full of different waveforms, localized as another poster mentions not just a fourier of the entire image. Anyway they are much better known now, so you can find it on the net.

This is not really the same as Barnsley's fractal compression one startup worked on around that time IIRC. They basically had a library of fractals which would be matched to image features, and once you had covered the entire image with them you would be able to zoom into it infinitely, since fractals are self-similar. You wouldn't necessarily get new detail but it would fool you into thinking you were. (I wonder if they liscensed it to anyone). They claimed 400:1 compression, etc. I don't know if they were the basis of LivePicture or if that was wavelet based.

These technologies all have two things in common, which is selecting an algorithmic strategy for talking about images, and storing it so efficiently that the data can be found quickly. The old Fujitsu system ran on a NEWS workstation IIRC, and it was blisteringly fast compared to any system I have ever seen. Only problem is doodles all look pretty much the same unless you are talented and patient.

It seems PNI (Picture Network Interactive)'s natural language recognition text searching for photos was the best, it was just text but used software supposedly developed for the White House. Only thing was they wanted to take over the entire industry with online contracts (this was around 1993) so everyone hated them. Nice tech though.

Anyway, wavelets may not be the entire solution but certainly they are a very useful way to describe data (not just a photo) and undoubtedly have lots of potential applications that just haven't materialized yet. Here's some tidbits Lancaster's links ImgSeek
  Perl Haar decomposition and seeking
  Blitzwave lib
  wvlt
  wvlt #2
  Wavelet.org
  WSQ used for FBI fingerprinting

Thanks. There used to be a funny translation of part of the Pillow Book into blog-speak at http://blog.simon-cozens.org/shonagon/ but it isn't working now. I don't know why. I left a note on the blog of the guy who made it. It's kind of a joke, but kind of accurate. Is there a difference between listing your favorite seasons and saying, "I'm listening to Radiohead now"? I haven't gotten into any other version enough to recommend one.

I'm of mixed feelings on that. I have the obligatory bookshelf dedicated to books with woodcuts on the cover, but I'm not happy with some of the ones I've gotten recently (I won't say "recent ones" since I think the Postfix book, at least, isn't all that recent). The New Riders books I have (both Paul duBois, I believe) I'm pretty happy with.

I'd not trust Apress until I hear the whole story on this issue and see how it settles out, though. Probably fine, but...

I'm of mixed feelings on that. I have the obligatory bookshelf dedicated to books with woodcuts on the cover, but I'm not happy with some of the ones I've gotten recently (I won't say "recent ones" since I think the Postfix book, at least, isn't all that recent). The New Riders books I have (both Paul duBois, I believe) I'm pretty happy with.

I'd not trust Apress until I hear the whole story on this issue and see how it settles out, though. Probably fine, but...

This first version of the book was written by Simon Cozens.

When it came to writing the second edition, Simon didn't get the job owing to his reluctance to carry it forward to future revisions, due to work restraints. So, someone else was hired, but Simon was promised 50% royalties, since it was going to be based largely on his work.

Based on Simons latest blog post, the publishers have conveniently forgotten this agreement. He's now not goint to get any royalties for the book, despite having written much of the material!

So, rather than buying the new edition (and supporting a publisher who rips off their authors), you should go read the Creative Commons licensed version of the first edition that Simon has posted here.

This first version of the book was written by Simon Cozens.

When it came to writing the second edition, Simon didn't get the job owing to his reluctance to carry it forward to future revisions, due to work restraints. So, someone else was hired, but Simon was promised 50% royalties, since it was going to be based largely on his work.

Based on Simons latest blog post, the publishers have conveniently forgotten this agreement. He's now not goint to get any royalties for the book, despite having written much of the material!

So, rather than buying the new edition (and supporting a publisher who rips off their authors), you should go read the Creative Commons licensed version of the first edition that Simon has posted here.

James Loo with Simon Cozens and Peter Wainwright

Though it appears that Simon Cozen's involvement was limited to having his text from the first edition used and the publisher backtracking on the agreement to pay him royalties for it.

His first edition is freely downloadable and he has a PayPal tip jar if you like it.

James Loo with Simon Cozens and Peter Wainwright

Though it appears that Simon Cozen's involvement was limited to having his text from the first edition used and the publisher backtracking on the agreement to pay him royalties for it.

His first edition is freely downloadable and he has a PayPal tip jar if you like it.

Anyone know how Struts compares to Maypole, a Perl-based MVC? I just started reading up on MVCs, and Maypole claims decent functionality can be achieved with as little as 10-20 lines of coding.

Also, while I'm thinking of it, does anyone know of a decent Python-based MVC?

While the idea of a 3 year old book on web development appeals to the poetry in my soul, I think it is misleading. In the last few years the Perl dev community has been making really significant progress in enabling rapid development methodologies, in particularly using tools like Class::DBI

A book which claims to detail how to do web development with Perl and MySQL and doesn't address the following issues is painfully out of date:

* Class::DBI
* SPOPS
* Kake's How to avoid writing code

With the Perl Foundation funded work on Maypole being the most recent efforts in this direction.

Simon Cozens has written one of these. It's called Flox, is written in perl using Apache::MVC (also known as Maypole), and is only 300 lines of code!

Simon Cozens has written one of these. It's called Flox, is written in perl using Apache::MVC (also known as Maypole), and is only 300 lines of code!

Simon Cozens has written one of these. It's called Flox, is written in perl using Apache::MVC (also known as Maypole), and is only 300 lines of code!

UK programmer, maintainer of perl.com, and Anglican missionary Simon Cozens has re-rendered the 10th-century Japanese classic Pillow Book of Sei Shonagon as a blog. It works waaay too well.

[The Truste seal] will signal that the e-mail is from a company that has agreed to guidelines based on fair information practice principles, Schiavone said.

This is great! Now all I have to do is put a line in my Mail::Audit filter to look for that seal and automatically ditch any mail that contains it. Or better yet, send a reject notice to the "trusted" sender saying that I didn't ask for it, I don't want it, and if they don't want to be sued for wasting my bandwidth, they'd better not send it to me any more.

OpenBSD forked off of FreeBSD a few versions back [...]