Re^3: Parrot, the future of dynamic languages ?

[zentara]

It'll be a real seller! No more regexes! No more hashes! No IO-library! No devices! Just pushing data thru registers! I can hear SUN and Microsoft weep, soon noone will be using Java, C# or .NET. Everyone will just be pushing data thru registers.

Well the Parrot libs will still have to handle the drivers, etc, but it should become invisible to the programmer, and there will of course be alot of high-level libraries to do alot of the repetitive stuff, like regexes and hashes. And I DO see the end of Java and C#, and NET except for the corporate fools who will hang on to it, because they "invested their life's training" into it.

I admit I havn't been "schooled" by the mainstream college ideas since the 70's and I missed out on the all the Java stuff, but I'm glad I didn't waste my time with it. So yes, maybe a quantuum leap for me, isn't the same as for you. But at least I'm not "trapped in one of the quantuum energy-state-holes" called Java,C#,or NET.

For what it's worth, I've been seeing a parallel push in C++. As I read the newsgroups now, it seems they are developing a CPAN sort of library collection to make the simple things, easy and invisible to the programmer. Check out Boost It seems that there is this cone we are all in, all heading towards the "cone's vertex". That vertex, is a set of libs, that run cross platform, and allow you to handle data intuitively as humans understand it. We see data as "numbers,text,and binary bits". Dosn't it make sense to make a cpu that handles data in that form? Sure it has ultimately to be done at a binary level, but should programmers have to deal with that? I think all programming languages are going to "merge" into 1 "quasi-launguage" when that cone-vertex is reached. We are still quite a distance away, but Parrot seems to be taking those first steps, and that is what I like about it.

Maybe the world needs a "global conference" on "what would the "ideal cpu" should be, and go about creating it as a "virtual cpu" with a "virtual assembly language". Then when a new cpu is released, the low-level enginners use the real assembly for the cpu, to make libs for compatibility with the "standard virtual cpu". Then all programmers have to do is learn 1 cpu, and the associated ways of doing different tasks.

To me, that is what Parrot is all about. It's not about Perl. Perl is just going to be implemented using Parrot.

My only prayer is that they have some good assembly programmers to do the basic libs, so it's fast.