delorie.com/archives/browse.cgi | search |
X-Authentication-Warning: | delorie.com: mail set sender to geda-user-bounces using -f |
X-Recipient: | geda-user AT delorie DOT com |
X-Original-DKIM-Signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; |
d=gmail.com; s=20120113; | |
h=mime-version:in-reply-to:references:date:message-id:subject:from:to | |
:content-type; | |
bh=elhVmm2gznZbhKkver3vAi33cbKF43+cOV0aqpepWRk=; | |
b=afmtsvvkNRYvkBmJ0XG58cs676YzLL3Pl/ynmmVYXeUuWhk8ulpAqo6YrLtVXUofI6 | |
RQnyFQGMJ2j7NxR218N9lTT0tlwTmA9qooToNuruNxy43MJalb/KBUzgY24BvdJGVj4w | |
Yk59mePG7ZskEpbx+7i+V43eKzwozJnNOYXSs0yuatNsgntV7uWjTmvINuDppAMWHsHw | |
vXVjhQgJIev0d04Wubap7hxh+A6YW0JZitB57ZFdNErQg3jLc2cE07CnM95HgPDC2a/1 | |
avKb3PAqMOacC5ahC501UGav8APAyZOyzyjtaZGPcwx7fl4UttCmqveb+X2F8uIOx7NA | |
8Q4g== | |
MIME-Version: | 1.0 |
X-Received: | by 10.107.159.66 with SMTP id i63mr9941174ioe.68.1436298805076; |
Tue, 07 Jul 2015 12:53:25 -0700 (PDT) | |
In-Reply-To: | <20150707193304.GA14821@recycle.lbl.gov> |
References: | <1436006726 DOT 677 DOT 13 DOT camel AT ssalewski DOT de> |
<20150706200609 DOT GD24178 AT localhost DOT localdomain> | |
<CAC4O8c9f0pLsLu_dyuO5ggh7RmHY1vAA=UUhk9AE0JYZb4mhBQ AT mail DOT gmail DOT com> | |
<CAM2RGhQfPO31-1Uyc3kC7w286r0VD7c41UZEZcyYquzknCxbsQ AT mail DOT gmail DOT com> | |
<20150707060409 DOT GB14357 AT localhost DOT localdomain> | |
<CAOP4iL2C_LU=RQy5FWYF-7RrHW6tqhqqyFJGjkwLQ2AD7FiYJA AT mail DOT gmail DOT com> | |
<1436287952 DOT 678 DOT 26 DOT camel AT ssalewski DOT de> | |
<559C0F7E DOT 7010009 AT neurotica DOT com> | |
<1436293439 DOT 678 DOT 71 DOT camel AT ssalewski DOT de> | |
<559C24B4 DOT 3040007 AT neurotica DOT com> | |
<20150707193304 DOT GA14821 AT recycle DOT lbl DOT gov> | |
Date: | Tue, 7 Jul 2015 15:53:24 -0400 |
Message-ID: | <CAOuGh891VtcHtAfVD9NHwZB9A0OX-h1bBdL72FuDm1Tr94XhWQ@mail.gmail.com> |
Subject: | Re: [geda-user] gEDA/gschem still alive? |
From: | "Bob Paddock (graceindustries AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com> |
To: | geda-user AT delorie DOT com |
Reply-To: | geda-user AT delorie DOT com |
Errors-To: | nobody AT delorie DOT com |
X-Mailing-List: | geda-user AT delorie DOT com |
X-Unsubscribes-To: | listserv AT delorie DOT com |
On Tue, Jul 7, 2015 at 3:33 PM, Larry Doolittle <ldoolitt AT recycle DOT lbl DOT gov> wrote: > is somewhat impractical, given the goals of grabbing python modules > from wherever And having them all work together. :-( > I'd like to see at least one of Python, Lua, Nim, Julia, ... reach > the level of maturity and stability that we have in C today. Yes. There is also Pony: http://ponylang.org/ " Why Pony? Programming languages have been developed for over five decades and there are many of them. So, why Pony? Developing high performance and scalable software systems has always been a very difficult task. With the introduction of multi-core processors, productivity using low-level languages such as C or C++ dramatically decreased. Substantial time had to be invested in debugging memory management related issues or data-race bugs. Manually synchronising concurrent memory accesses was an additional dimension programmers had to worry about, which ultimately distracted from the actual problem to be solved. Most importantly, the increase in performance, scalability and efficiency (if any) gained by programming for multiple cores was outweighed by the effort that had to be put in. We believe that a programming language should be a high-level tool to express a problem to be solved by the computer. The runtime system should, with a little help and as unintrusively as possible, figure out how to map the program to the underlying hardware as efficiently as possible. The key is to have strong compile-time guarantees. Every single feature of Pony is designed to guarantee correctness and to improve speed as well as simplicity. The result is an actor-based language where programs cannot crash, where garbage collection is fully concurrent and non-blocking, and where programs are guaranteed to be data-race free. Applications can run on a virtually infinite processor count and on arbitrarily large clusters, without changing the source code. It's type safe! Pony is type safe. Really type safe. There's a mathematical proof and everything. It's memory safe! There are no dangling pointers and no buffer overruns. The language doesn't even have the concept of null! It's exception safe! There are no runtime exceptions. All exceptions have defined semantics, and they are alwayscaught. It's data-race free! Pony doesn't have locks or atomic operations or anything like that. Instead, the type system ensures at compile time that your concurrent program can never have data races. So you can write highly concurrent code and never get it wrong. It's deadlock free! This one is easy, because Pony has no locks at all! So they definitely don't deadlock, because they don't exist! It's compiled! Pony is a ahead-of-time (AOT) compiled language. There is no interpreter or virtual machine. It's compatible with C! Pony programs can natively call C libraries. Our compiler is able to generate a C-header file for Pony libraries. Consequently, C/C++ programs can natively call Pony programs!"
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |