[dylan] The Future of Dylan: Why are we here?

--===============1756542264==
Content-Type: multipart/alternative; boundary=047d7b5d30be225f610501fbdfd0

--047d7b5d30be225f610501fbdfd0
Content-Type: text/plain; charset=UTF-8

I'm going to break this up over a couple of days as I'd like to see
(hopefully) some discussion of the early points before we move into the
later points.

I will also try not to answer the questions with my own answers within the
initial posts, but use a follow up to do so so that my opinions are at
least somewhat separate from the questions.

If you haven't used Dylan in a long time, your answers are welcome as well!

Even if you just think that you agree with what others have posted or some
of the points below, please respond anyway. The more feedback that we get,
the more we can understand which positions are strongly held and by how
much of the community.

------

    The very least you can do in your life is figure out what you hope for.
    And the most you can do is live inside that hope.
    Not admire it from a distance but live right in it, under its roof.

      -- Barbara Kingsolver

It is time for everyone with an interest in Dylan to think about the future
of Dylan.

But let's take a step backwards. Why are we here? Why are we reading this?

What Makes Dylan Special?
------

What makes Dylan special? What makes it great? What makes some of us want
to keep working on it, well past any hope of entering the mainstream?

Some like the macros. Some like the condition system. Others appreciate the
sliding scale between static and dynamic behaviors. Some appreciate that it
can generate efficient, native executables and shared libraries. Still
others find the syntax to be nice while, admittedly, others hate the
syntax. Yet others appreciate the coherent and consistent design behind
Dylan, where a set of core features mesh well to provide a clean and clear
language. Perhaps some value that we have an actual language specification
via the DRM.

What brings you here?

To move on and think further about the future of Dylan, we must understand
why we've chosen to be here in the first place.

What are the core values of Dylan? What must, above all else, be preserved?

Thanks!

 - Bruce

--047d7b5d30be225f610501fbdfd0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I&#39;m going to break this up over a couple of days as I&=
#39;d like to see (hopefully) some discussion of the early points before we=
 move into the later points.<div><br></div><div>I will also try not to answ=
er the questions with my own answers within the initial posts, but use a fo=
llow up to do so so that my opinions are at least somewhat separate from th=
e questions.</div>
<div><br></div><div><div>If you haven&#39;t used Dylan in a long time, your=
 answers are welcome as well!</div><div><br></div></div><div><div>Even if y=
ou just think that you agree with what others have posted or some of the po=
ints below, please respond anyway. The more feedback that we get, the more =
we can understand which positions are strongly held and by how much of the =
community.</div>
<div><br></div></div><div>------</div><div><br></div><div><div>=C2=A0 =C2=
=A0 The very least you can do in your life is figure out what you hope for.=
</div><div>=C2=A0 =C2=A0 And the most you can do is live inside that hope.<=
/div><div>=C2=A0 =C2=A0 Not admire it from a distance but live right in it,=
 under its roof.</div>
<div><br></div><div>=C2=A0 =C2=A0 =C2=A0 -- Barbara Kingsolver</div><div><b=
r></div><div>It is time for everyone with an interest in Dylan to think abo=
ut the future of Dylan.</div><div><br></div><div>But let&#39;s take a step =
backwards. Why are we here? Why are we reading this?</div>
<div><br></div><div>What Makes Dylan Special?</div><div>------</div><div><b=
r></div><div>What makes Dylan special? What makes it great? What makes some=
 of us want to keep working on it, well past any hope of entering the mains=
tream?</div>
<div><br></div><div>Some like the macros. Some like the condition system. O=
thers appreciate the sliding scale between static and dynamic behaviors. So=
me appreciate that it can generate efficient, native executables and shared=
 libraries. Still others find the syntax to be nice while, admittedly, othe=
rs hate the syntax. Yet others appreciate the coherent and consistent desig=
n behind Dylan, where a set of core features mesh well to provide a clean a=
nd clear language. Perhaps some value that we have an actual language speci=
fication via the DRM.</div>
<div><br></div><div>What brings you here?<br></div><div><br></div><div>To m=
ove on and think further about the future of Dylan, we must understand why =
we&#39;ve chosen to be here in the first place.</div><div><br></div><div>
What are the core values of Dylan? What must, above all else, be preserved?=
</div><div><br></div></div><div>Thanks!<br></div><div><br></div><div>=C2=A0=
- Bruce</div><div><br></div></div>

--047d7b5d30be225f610501fbdfd0--

--===============1756542264==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
hackers mailing list
[email protected]
https://lists.opendylan.org/mailman/listinfo/hackers

--===============1756542264==--