[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On March 25, 2010, Elias Pschernig wrote:
> On Thu, Mar 25, 2010 at 2:20 PM, Thomas Fjellstrom
<tfjellstrom@xxxxxxxxxx>wrote:
> > > Thats what the proposal is supposed to prevent. Not sitting on
> > > changes.
> >
> > Theres going to be no new talent (no new generation) if the development
> > dies
> > to such an extent again.
> >
> > I would like to see that not happen.
>
> It's really nothing I care much about... *if* someone will want to pick
> up development for whatever reason it will be up to them to decide on
> how to do the versioning then. Or even just start a new library instead
> of naming it Allegro. So no need for us to plan ahead that long.
People aren't going to want to "pick up development" in general, in fact,
its more likely that people just won't know about the project at all.
Usually when a project dies, its dead. It rarely comes back. And I think
thats a waste. If we can pull off what other projects have done to
revitalize their development and community, seemingly just by making regular
releases regardless of the changes, we probably should.
"If you build it, they will come" basically.
I didn't think you (elias and peter) would be so apathetic towards it given
the work you've put into the project so far.
>
> Myself I'm somewhat wondering how long things like libraries and so on
> will even be needed, once we have mind control and stuff I'd want to
> just think of the game, how it should work and how it should look and
> computers would do the lower levels tasks of translating those thoughts
> into some kind of machine language or whatever... :)
>
--
Thomas Fjellstrom
tfjellstrom@xxxxxxxxxx