Comments on: The E Programming Language http://agoln.net/archives/39 Development and personal site Wed, 12 May 2010 16:55:16 -0700 hourly 1 http://wordpress.org/?v=3.0.1 By: Luke Hoersten http://agoln.net/archives/39/comment-page-1#comment-38 Luke Hoersten Fri, 27 Jul 2007 02:43:50 +0000 http://agoln.net/archives/39#comment-38 Erlang goes way above and beyond E. Erlang not only concentrates on local concurrency (which they did 20 years ago!), but multi-node concurrency! <em>That</em> is why it is so popular lately. So yes, a new language with only deadlock-bucking is nothing significant. Erlang's had it for 20 years along with many other breakthroughs. Erlang goes way above and beyond E. Erlang not only concentrates on local concurrency (which they did 20 years ago!), but multi-node concurrency! That is why it is so popular lately.

So yes, a new language with only deadlock-bucking is nothing significant. Erlang’s had it for 20 years along with many other breakthroughs.

]]> By: Bennett http://agoln.net/archives/39/comment-page-1#comment-36 Bennett Tue, 17 Jul 2007 15:18:04 +0000 http://agoln.net/archives/39#comment-36 Slightly insignificant? No way. For mission critical applications it is a must have. I've not really heard of E before but Erlang has been in the news a lot lately. It is praised for that same reasons, and that is why it is being used in systems that need to be highly fault tolerant. Erlang as well as many others use message passing and actor model for concurrency. It's pretty interesting also. Slightly insignificant? No way. For mission critical applications it is a must have. I’ve not really heard of E before but Erlang has been in the news a lot lately. It is praised for that same reasons, and that is why it is being used in systems that need to be highly fault tolerant. Erlang as well as many others
use message passing and actor model for concurrency. It’s pretty interesting also.

]]> By: Logan http://agoln.net/archives/39/comment-page-1#comment-33 Logan Tue, 17 Jul 2007 04:41:26 +0000 http://agoln.net/archives/39#comment-33 I think that it's not only deadlock-bucking, but allowing it to go seemlessly over a connection is what makes it neat. It takes about 4 lines of code to run a remote function, although I'm not sure of any benchmarking. I think that it’s not only deadlock-bucking, but allowing it to go seemlessly over a connection is what makes it neat. It takes about 4 lines of code to run a remote function, although I’m not sure of any benchmarking.

]]> By: Luke Hoersten http://agoln.net/archives/39/comment-page-1#comment-32 Luke Hoersten Tue, 17 Jul 2007 01:19:04 +0000 http://agoln.net/archives/39#comment-32 Hey that is pretty nifty. Deadlock-bucking promises seems like a slightly insignificant feature to base a language around though. Most languages boast new paradigms or a whole set of new features such as this. In fact, they are working on adding stuff like this into C++ IIRC. Regardless, it's an interesting idea and makes a lot of sense. Have some code watch over your threads and make them play nice and share =) Hey that is pretty nifty. Deadlock-bucking promises seems like a slightly insignificant feature to base a language around though. Most languages boast new paradigms or a whole set of new features such as this. In fact, they are working on adding stuff like this into C++ IIRC.

Regardless, it’s an interesting idea and makes a lot of sense. Have some code watch over your threads and make them play nice and share =)

]]>