This Larry guy is phenomenal. He has single handely managed to produce an immense amount of bad will in the only community that had any motivation to support and push his product in places that actually buy licenses.
Let me guess, the next time a large corporation is going to choose its VCS for a project the LinuxHeads (and there is always one or two) are really going to vote this product down from the choice list.
Prediction 1: Out of business in a year... at most two.
Prediction 2: Most other VCS will improve to fill the void. From what I've seen so far as soon as Arch gets to clean up its command line interface it will wipe out all the others.
Sorry guys, I love HP calcs and I really like RPN but for most things a Palm PDA and EasyCalc is a better solution.
The thing is if you only have a 2/4 line input screen RPN is unbeatable but on a 320x320 screen there is no point. The thing to beat there is a symbolic calculator, somethng like a micro Mathematica for a handheld.
And, the entry cost is close to $100 bucks for a low level Palm PDA whose battery live is measured in weeks if not months per charge for a B/W screen.
I had many HP calculators. Lved them all. Loved RPN. Power48 is an impressive emulator... BUT:
1.- Start time is too long. Screen is too crowded and plain complicated for a PDA LCD.
2.- If you need a very good calculator use EasyCalc and you'll be happier at any resolution. http://easycalc.sourceforge.net/. Fast startup and decent interface. Clearly not as programable nor a large library of tools, still very usable.
Now, here is the irony: HP should have been a king of the PDA arena using their experience in the calculator group... but somehow they become WinCE clone makers. Very sad. What happened?
XMingWin makes for a very nice tool to use from the Linux side. But the big question is: How well does it work in the area of dynamically loading libraries (.so and.dll stuff) and all the headaches associated with all those #ifdefs in portable libraries!
As a particular minimal case try: Hello World app using wxWindows for both environments. It would be nice to see if this is a more vialble approach than using the same sources using gcc under Linux and Dev-C++ inder Win* to compile a portable app.
Just curious...
Sergio
Re:Concurrent/Distributed tasks
on
Ask Larry Wall
·
· Score: 1
I was thinking more on hte lines of the Jabber protocol myself.
Re:Concurrent/Distributed tasks
on
Ask Larry Wall
·
· Score: 1
It seems form your comments that you haven't done any large scale enterprise programming. Perl is used very much there.
Look, you said it, 5.8.0 -- THERE IS A.0 AT THE END!!! How well tested it it?
Pixie: What does a persistent data storage layer have to do with concurren/distributed programming?
Core: Installed by default. I would like to see some of these capabilities avaiable as default in Perl 6.
Many places don't allow for modules to be added in such a loose way. Think about this when you update twhenty servers and you install the wrong/incompatible version of a module next time.
Concurrent/Distributed tasks
on
Ask Larry Wall
·
· Score: 2, Interesting
Larry,
One of the limitations that I have found on Perl is its lack of modern concurrent processing support in the form of a standard stable threads package (yes, there is ithreads) or some way to make Perl modules execute and comunicate remotely (nope, rsh* won't do, neither is SOAP the solution)
More and more other languages are providing mechanisms or libraries of modules that are standard in their distribututions.
I would like to know what kind of ideas you would have in this area. Do you think that Perl needs to have this capability as a standard component?
Unfortunately everyone is missing the point. The problem with SashXB is that it should be deployed as a stand-alone package without a dependency to certain particular versions of libraries! As soon as some of these change the whole thing would break!
At least the diretibuition should be one single binary or it should load its own set of libraries.
Personally it should have been built using wxWindows.
Hey, I can do magic with Perl but I would like to see a stable and uniform threads support in the
langage. It doen't neet to be native threads, just
standard.
Someone mentioned that the total prpduction cost
was approx 20M. I timed the commericals and the
program segments (9min show + 4min commercial) and
it seems that there where only approx 4.15 hours
of show. If the commercials cost 10K per second I
think it was a very good return on investment.
Does anybody know with more accuracy the return
numbers?
Nice work, but if there are no ISO images downloadable I doubt that the product is used
very much... therefore it has not been reviewed
a lot
... so then...
appart from a bit of self inflicted
damage (or need for cash) why is is it that you
insist on copyrighting those ISO image distributions? Just to keep BSD to a few select
users (as usual:-)
It seems that the only shift that is needed is not that the publisher must be eliminated but that the media on which the articles are published must evolve.
The Los Alamos e-print project shows that the electornic distribution and searching of the knowledge works. And it works very well.
The next stage (which is already happening) is the elimination of the printed publication. But not all publications need to disapear... only those that have specialized to the point of being just a container of papers (Have you ever seen Physics Review A or B or C or D, etc). Opinion and field reviews need to have support for the lateral effect that the electronic media hasn't yet perfected (Think of 'I saw this article next to another one I was looking for in the same issue). Portals are OK but still limited.
Printed paper has had one advantage to the electronic format... it can be read after many many years. Try to read a 5 1/4 floppy today. And worse, only those texts written in TeX or SGML or PosScript are really readable today after ten years. So a careless jump into the e-print business could really be a disaster if some sort of standards are not carefully thought out.
Regarding the peer review mechanism... it will be with us for a long time because even though it may be a bit biased it is the only way to filter out the noise. It hopefully will be coexisting with a repository of freely submitted material (like Los Alamos) so that those that want to do their filtering process by themselves may have the choice to look for themselves and build their own filters.
Slashdot Mirror
Still a dream in many places in Brooklyn NY....
Try Scratch using this guide:
Super Scratch Programming Adventure!: Learn to Program By Making Cool Games by the LEAD project.
It looks like a well organized way to build projects that explain the different features. Later you can try python or processing.
And if he is interested then C and C++ for the real thing :-)
From the book "Life with Unix" in the secion on games it gors sort of like this: There is a game called 'cc'. It seems we never finish it.
Don't eat the green cookies!
Woa... what a way to crash and burn!
This Larry guy is phenomenal. He has single handely managed to produce an immense amount of bad will in
the only community that had any motivation to support and push his product in places that actually buy licenses.
Let me guess, the next time a large corporation is going to choose its VCS for a project the LinuxHeads (and there is always one or two) are really going to vote this product down from the choice list.
Prediction 1: Out of business in a year... at most two.
Prediction 2: Most other VCS will improve to fill the void. From what I've seen so far as soon as Arch gets to clean up its command line interface it will wipe out all the others.
Recently someone mentioned to me that it is possible to put hunderds of books in a CD using DjVu. It looks like DjVu is the MP3 of books!
Take a look at http://www.djvuzone.org/
The curious thing is that there is great support for it under Linux and KDE in particular.
Sorry guys, I love HP calcs and I really like RPN but for most things a Palm PDA and EasyCalc is a better solution.
The thing is if you only have a 2/4 line input screen RPN is unbeatable but on a 320x320 screen there is no point. The thing to beat there is a symbolic calculator, somethng like a micro Mathematica for a handheld.
And, the entry cost is close to $100 bucks for a low level Palm PDA whose battery live is measured in weeks if not months per charge for a B/W screen.
I had many HP calculators. Lved them all. Loved RPN.
Power48 is an impressive emulator... BUT:
1.- Start time is too long. Screen is too crowded and plain complicated for a PDA LCD.
2.- If you need a very good calculator use EasyCalc and you'll be happier at any resolution. http://easycalc.sourceforge.net/. Fast startup and
decent interface. Clearly not as programable nor a large library of tools, still very usable.
Now, here is the irony: HP should have been a king of the PDA arena using their experience in the calculator group... but somehow they become WinCE clone makers. Very sad. What happened?
Interesting...
This is the real thing in terms of what a practical developer of apps targeted to run both on Linux and Win32 needs.
Thanks!
XMingWin makes for a very nice tool to use from the Linux side. But the big question is: How well does it work in the area of dynamically loading libraries (.so and .dll stuff) and all the headaches associated with all those #ifdefs in portable libraries!
As a particular minimal case try: Hello World app using wxWindows for both environments. It would be nice to see if this is a more vialble approach than using the same sources using gcc under Linux and Dev-C++ inder Win* to compile a portable app.
Just curious...
Sergio
I was thinking more on hte lines of the Jabber protocol myself.
It seems form your comments that you haven't
.0 AT
done any large scale enterprise programming.
Perl is used very much there.
Look, you said it, 5.8.0 -- THERE IS A
THE END!!! How well tested it it?
Pixie: What does a persistent data storage layer have to do with concurren/distributed programming?
Core: Installed by default. I would like to see some of these capabilities avaiable as default
in Perl 6.
Many places don't allow for modules to be added
in such a loose way. Think about this when you update twhenty servers and you install the wrong/incompatible version of a module next time.
Larry,
One of the limitations that I have found on Perl is
its lack of modern concurrent processing support in
the form of a standard stable threads package (yes, there is ithreads) or some way to make Perl modules execute and comunicate remotely (nope, rsh* won't do, neither is SOAP the solution)
More and more other languages are providing mechanisms or libraries of modules that are standard in their distribututions.
I would like to know what kind of ideas you would have in this area. Do you think that Perl needs to
have this capability as a standard component?
Thanks for all the fun!
Someone once said:
"It is possible to write spagetti code in any language "
Remember that when you are using your favorite programming tool.
You can write very readable and clean code in Perl...
it just takes some dicipline.
Unfortunately everyone is missing the point. The problem
with SashXB is that it should be deployed as a stand-alone package
without a dependency to certain particular versions of
libraries! As soon as some of these change the whole thing would break!
At least the diretibuition should be one single binary or it should load its own set of libraries.
Personally it should have been built using wxWindows.
Hey, I can do magic with Perl but I would like to see a stable and uniform threads support in the
langage. It doen't neet to be native threads, just
standard.
Someone mentioned that the total prpduction cost
was approx 20M. I timed the commericals and the
program segments (9min show + 4min commercial) and
it seems that there where only approx 4.15 hours
of show. If the commercials cost 10K per second I
think it was a very good return on investment.
Does anybody know with more accuracy the return
numbers?
Theo,
:-)
Nice work, but if there are no ISO images downloadable I doubt that the product is used
very much... therefore it has not been reviewed
a lot
... so then...
appart from a bit of self inflicted
damage (or need for cash) why is is it that you
insist on copyrighting those ISO image distributions? Just to keep BSD to a few select
users (as usual
It seems that the only shift that is needed is not
that the publisher must be eliminated but that the media on which the articles are published must evolve.
The Los Alamos e-print project shows that the electornic distribution and searching of the knowledge works. And it works very well.
The next stage (which is already happening) is the elimination of the printed publication. But not all publications need to disapear... only those that have specialized to the point of being just a container of papers (Have you ever seen Physics Review A or B or C or D, etc). Opinion and field reviews need to have support for the lateral effect that the electronic media hasn't yet perfected (Think of 'I saw this article next to another one I was looking for in the same issue). Portals are OK but still limited.
Printed paper has had one advantage to the electronic format... it can be read after many many years. Try to read a 5 1/4 floppy today. And worse, only those texts written in TeX or SGML or PosScript are really readable today after ten years. So a careless jump into the e-print business could really be a disaster if some sort of standards
are not carefully thought out.
Regarding the peer review mechanism... it will be with us for a long time because even though it may be a bit biased it is the only way to filter out the noise. It hopefully will be coexisting with a repository of freely submitted material (like Los Alamos) so that those that want to do their filtering process by themselves may have the choice to look for themselves and build their own
filters.