Breaking compatibilyt hurts

2009-12-02 Thread Jesse Phillips
This has come up as one issue for adoption to D. D2.x is on its way, unstable, and D1.x is getting the ax. While Walter has said that the compiler will continue to get support, no one in the community knows what the library support will be like. I came across an article where even Python wasn't

Re: Breaking compatibilyt hurts

2009-12-02 Thread Walter Bright
Jesse Phillips wrote: This has come up as one issue for adoption to D. D2.x is on its way, unstable, and D1.x is getting the ax. While Walter has said that the compiler will continue to get support, no one in the community knows what the library support will be like. I came across an article wher

Re: Breaking compatibilyt hurts

2009-12-02 Thread Jesse Phillips
Walter Bright wrote: > One of the comments in there: > > "One of the greatest problems I found when trying Common Lisp was the > large number of implementations and the disorganization of the library > space. It is hard for a newcomer to decide which libraries are > available, which are maintai

Re: Breaking compatibilyt hurts

2009-12-02 Thread torhu
On 03.12.2009 1:13, Jesse Phillips wrote: This has come up as one issue for adoption to D. D2.x is on its way, unstable, and D1.x is getting the ax. While Walter has said that the compiler will continue to get support, no one in the community knows what the library support will be like. I came

Re: Breaking compatibilyt hurts

2009-12-02 Thread Walter Bright
Jesse Phillips wrote: Well, part of the problem is that you can use all of those arguments against D (That includes the complaint about Lisp). Maybe not if you just look at D1 or just D2, and many times the complaints aren't as big an issue as they are made out to be once you start using the lang

Re: Breaking compatibilyt hurts

2009-12-03 Thread Don
torhu wrote: On 03.12.2009 1:13, Jesse Phillips wrote: This has come up as one issue for adoption to D. D2.x is on its way, unstable, and D1.x is getting the ax. While Walter has said that the compiler will continue to get support, no one in the community knows what the library support will be

Re: Breaking compatibilyt hurts

2009-12-03 Thread Trass3r
Jesse Phillips schrieb: I'm not claiming D is in the wrong in its chosen path. This shows that other languages deal with similar issues, but is one thing for someone familiar with a language to not choose it for a project than it is to get someone to look into a new language. From time to ti

Re: Breaking compatibilyt hurts

2009-12-03 Thread naryl
Walter Bright Wrote: > Jesse Phillips wrote: > > Well, part of the problem is that you can use all of those arguments > > against D (That includes the complaint about Lisp). Maybe not if you > > just look at D1 or just D2, and many times the complaints aren't as > > big an issue as they are made o

Re: Breaking compatibilyt hurts

2009-12-04 Thread Daniel de Kok
On 2009-12-03 01:13:13 +0100, Jesse Phillips said: This has come up as one issue for adoption to D. D2.x is on its way, unstable, and D1.x is getting the ax. While Walter has said that the compiler will continue to get support, no one in the community knows what the library support will be lik

Re: Breaking compatibilyt hurts

2009-12-04 Thread Leandro Lucarella
Daniel de Kok, el 4 de diciembre a las 09:38 me escribiste: > On 2009-12-03 01:13:13 +0100, Jesse Phillips > said: > >This has come up as one issue for adoption to D. D2.x is on its > >way, unstable, and D1.x is getting the ax. While Walter has said > >that the compiler will continue to get supp

Re: Breaking compatibilyt hurts

2009-12-04 Thread Nick Sabalausky
"Leandro Lucarella" wrote in message news:20091204133103.gb27...@llucax.com.ar... > Daniel de Kok, el 4 de diciembre a las 09:38 me escribiste: >> On 2009-12-03 01:13:13 +0100, Jesse Phillips >> said: >> >This has come up as one issue for adoption to D. D2.x is on its >> >way, unstable, and D1

Re: Breaking compatibilyt hurts

2009-12-04 Thread Leandro Lucarella
Nick Sabalausky, el 4 de diciembre a las 10:03 me escribiste: > > The second release with the change has the new/removed feature. That gives > > people time to fix their programs and try the new feature without breaking > > anything for several months (a minor Python version is released each ~9 >