Well, I didn't mean to pan it by the YAPL tag. But we are getting a
lot of them. D was supposed to be the savior for a while, and
probably will eventually displace C++. D can call C/C++ now, I believe.
I'm surprised you like GO, isn't garbage collection a bad idea? I
seem to remember long conversations about how the last cpu cycle had
to be wrung out of any large system, and GC foils that.
I'm really impressed Rob Pike is on the design team. ATT really owned
the computing world for quite a while. Hopefully Rob will integrate
the best ideas into GO.
But YA does apply. I'm getting language fatigue. I was hoping
there'd be a rational core set of languages:
- Systems language: C/C++ level. Used for kernel/OS/drivers.
- Shell languages: Basically an easy way to pipe code written in
System Language
- Scripting: Python, Ruby, JavaScript level. Rapid prototyping
where performance
less important.
- Domain Specific: modeling (NetLogo etc), web (PHP, Javascript) ..
etc
So where does GO fit in? Probably at the systems level. The shells
and scripting languages may be able to use GO commands, that would be
sweet. So if we're just jacking up the programming platforms,
inserting GO as a C/C++ replacement, and dropping it back down, that
could work.
And yes, I miss the idea of a VM underneath it all. But if they come
up with a MS Common Language Runtime, that would be just as good.
Hey, maybe a wedtech on GO?
-- Owen
On Nov 10, 2009, at 9:52 PM, Douglas Roberts wrote:
What are you talking about, Owen? That's one good looking
language. I think I'm in love.
Seriously.
I'm not too wild about it's mascot Gordon the Gopher, however.
--
Doug Roberts
============================================================
FRIAM Applied Complexity Group listserv
Meets Fridays 9a-11:30 at cafe at St. John's College
lectures, archives, unsubscribe, maps at http://www.friam.org