Slashdot Mirror
Perl Features of the Future - Part 2
Kevin writes "This story is a follow up to yesterday's part 1 (hence the name) on the changes in Perl 6. Damian Conway (design team member): "There will be some learning involved, but it isn't like learning an entirely new language," he said. "It's more like adding a few new words to your vocabulary." It seems the perl intrepreter is getting overhauled as well."
The part 2 was there when the first story appeared on /., so anyone who was interested already read the whole thing. Further, both parts are mostly fluff and stuff that we already know from following these developments.
Does anyone else think it's sad that we've got a Perl story on Slashdot and the souce is a Yahoo! page?
The parrot interpreter reminds me so much of the CLR. I know mono has a C# compiler, but do they also have the equivalent of the MS CLR? If not then parrrot could fill that hole (well if it were going to come into existence in the next few years).
Photos.
While parrot sounds interesting, I'd like to it compared to other bytecode interpreters like the JVM and .NET's CLR. How similar/different are they? Is parrot more suited to scripting tasks? Does it have a robust security model like Java/.NET? Does it have any neat features that the others are missing?
These guys are just begging for handouts instead of cranking out code. They say they have no jobs - great! More time to code Perl6, right? Here's a clue, guys: simplify your language and VM designs. Right now it's all just a hodge-podge of shit. Looks like they're afraid to say 'no' to any useless fucking feature.
Also we should be able to vote on who gets the Perl Foundation money. The votes should be weighted by value of monetary contribution. At least one member of the team is a bigtime underachiever. How do you get your money back from the foundation if you're not happy with the results?
I wonder if it would be possible for Larry Wall/The Perl Foundation/someone to apply for grant money to work on Perl 6, like a university professor might.
Perl 6 files will end with .c .cc or .cpp, possibly .h and .hpp (.hh is right out, the number of files ending in .hh shall be zero and zero shall be the number of files ending in .hh).
The compiler will be renamed gcc. Oh yeah, there will be a compiler.
The syntax will look just like C/C++ except some of work of the past winners of the Obfuscated C contest will be incorporated as standard idiom (cool, ascii art that IS a program! cool)
- brought to you by the C++ Troll.
This quote surprised me a little bit.
"Like so many others in the IT industry, all three of us [Conway, Sugalski and Wall] have been looking for work," he noted.
In fact, this bothers me a lot. The company I work for, along with an extremely huge number of other corporations, have benefitted imensely from Perl. Oracle and many other products have custom Perl builds integrated with their products. Why is it that Larry Wall should have to be looking for work? Shouldn't he and the others be quite well off from the enormous benefit that he has provided the technology industry?
This is the biggest thing that scares me about open source. I don't want to sound anti-capitalistic here, but how many companies are reaping the benefits of the hard work Larry and other open source developers put into their excellent projects, but don't give a dime to those developers? How many members of the contributing Perl Foundation were corporate sponsors?
I advocate open source languages and products all the time, but I can see a danger. That danger comes from folks like those at Lindows. They take stuff that others have freely contributed, sell it, retire early in the Bahamas, and the developers who made it possible wind up serving lattes in a second job to support their families.
I can see open sourcing and donating useful utilities (I'm in the process of doing so this week), but I can't see myself putting in the time and energy into designing something as complex as an operating system kernel or programming language for free. Yes, the potential for peer recognition and hero status among geeks is tremendous, but the frustration of seeing someone else profit from my selfless contribution would take away the sweetness. Sorry, I'd rather devote those free hours to my kids or to a worthwhile charity. The rewards from those activities are even more valuable than alpha geek status.
Just to add to the other two posts. Parrot also seems to be much easier to develop for, people have been able to knock out protype test languages in no time. Speedwise it seems to be better. As for the security model it runs purely as a VM (if desired) so yeah it has the same level of security; if you can trust your OS not to let VMs escape the box then programs on the VM are secure.
GPL to some extent helps. Another important area would be "in house development projects", most software isn't written by software companies. If corporations open sourced their internal systems they could use each other's stuff. How different is the software used to test steel quality from company to company? Why can't insurance companies open source their membership systems (though not the data)? Government & academic programming are also promising since both can work on systems directly for the public benefit. Finally the examples of Oracle, etc... you mentioned are important. As the Linux kernel, and the open source browsers have shown for profit companies will help open source efforts where the open source software does some but not everything they need. Oracle might very well be willing to help Perl.
Wall aside, they weren't pulling their weight. Where is this imaginary trust fund of goodness that you propose that these people be paid out of? People are losing their jobs every single day - why are these guys any different? Furthermore - they were actually paid for Perl6 development by donations to the Perl Foundation. The jury is still out if that money was spent wisely.