Re: Java > Scala

2011-12-01 Thread Patrick Stewart
> I think one reason for the movement toward Java and JVM style languages is > that hardware is getting cheaper and cheaper, and developers cost the same > or more. With a 'simpler to write' 'quicker to write' language like Java > (where you don't have to learn things like manual memory mana

Re: Java > Scala

2011-12-01 Thread Patrick Stewart
Paulo Pinto Wrote: > Am 01.12.2011 12:59, schrieb Patrick Stewart: > >> I think one reason for the movement toward Java and JVM style languages is > >> that hardware is getting cheaper and cheaper, and developers cost the same > >> or more. With a 'simpler to

Re: Java > Scala

2011-12-02 Thread Patrick Stewart
Walter Bright Wrote: > On 12/1/2011 11:59 PM, Russel Winder wrote: > > (*) RPython is a subset of Python which allows for the creation of > > native code executables of interpreters, compilers, etc. that are > > provably faster than hand written C. http://pypy.org/ > > Provably faster? > > I ca

Re: Java > Scala

2011-12-02 Thread Patrick Stewart
Russel Winder Wrote: | CPython is written in C but PyPy is written in RPython (*). PyPy is | about 5 times faster than CPython on most of the performance benchmarks | CPython has. CPython is the main implementation and first Python that cameo out. It is still bleeding edge. I think that counts

Re: Biggest Issue with D - Definition and Versioning

2012-01-18 Thread Patrick Stewart
How about putting equal effort in keeping existing D users? There is more than one blogs online of ex D users with some pretty solid arguments why they abandoned D. And those args are usually not some missing shiny feature X but feature Y D already has but it is broken. Just saying focusing on

Re: Biggest Issue with D - Definition and Versioning

2012-01-18 Thread Patrick Stewart
Walter Bright Wrote: > On 1/18/2012 1:27 PM, Patrick Stewart wrote: > > How about putting equal effort in keeping existing D users? There is more > > than one blogs online of ex D users with some pretty solid arguments why > > they > > abandoned D. And those args a

Re: Biggest Issue with D - Definition and Versioning

2012-01-19 Thread Patrick Stewart
Walter Bright Wrote: > On 1/18/2012 4:03 PM, Patrick Stewart wrote: > > I am sorry to see many D community projects and libraries dead as they are > > targeted for D1 and not portable to D2, or just locked to specific version > > of > > D and not transferable to

Re: Biggest Issue with D - Definition and Versioning

2012-01-19 Thread Patrick Stewart
Walter Bright Wrote: > On 1/19/2012 2:06 AM, Patrick Stewart wrote: > > Long story short - I find new things added and premature optimizations The > > worst enemy of language at the moment. They might look like selling point to > > you, to me they look like distractions fr

Re: Biggest Issue with D - Definition and Versioning

2012-01-19 Thread Patrick Stewart
I agree 100% with this, must say, beautifully written essay.

Re: D versionning

2012-07-12 Thread Patrick Stewart
Most ridiculous thing about D is that it breaks so much backward compatibility that people just give up using it. Decent versioning like this might help people stick to something. Wake up, guys, it is 10+ years and *still* it haven't reached some form of stable release. Like I sad, engineering

Re: D versionning

2012-07-15 Thread Patrick Stewart
There is one thing missing from developers perspective as far D is concerned: Not all D users want to be beta testers. But they are all treated in such a way. That is reason #1 I migrate away from D all my software. It is long process and tough decision, but after 5 years of tracking D story I a

Re: D versionning

2012-07-15 Thread Patrick Stewart
> OTOH, it may break the community yet again, which we certainly > don't want, probably even less than breaking code. > Also, the example of Python with two main stable branches that > live in parallel is not very encouraging. Are you kidding? Python should be used as example of how software sho

Re: D versionning

2012-07-15 Thread Patrick Stewart
> OTOH, it may break the community yet again, which we certainly > don't want, probably even less than breaking code. > Also, the example of Python with two main stable branches that > live in parallel is not very encouraging. Also, check Python website: they recommend python v2 for all new user

Re: D versionning

2012-07-15 Thread Patrick Stewart
Adam Wilson Wrote: > On Sun, 15 Jul 2012 14:20:14 -0700, SomeDude > wrote: > > > On Sunday, 15 July 2012 at 20:44:01 UTC, Patrick Stewart wrote: > >>> OTOH, it may break the community yet again, which we certainly don't > >>> want, probably e

Re: D versionning

2012-07-15 Thread Patrick Stewart
SomeDude Wrote: > On Sunday, 15 July 2012 at 20:44:01 UTC, Patrick Stewart wrote: > >> OTOH, it may break the community yet again, which we certainly > >> don't want, probably even less than breaking code. > >> Also, the example of Python with two main stable b

Re: D versionning

2012-07-15 Thread Patrick Stewart
bearophile Wrote: > Patrick Stewart: > > > Both languages have programming bugs and bad decisions. Python > > fix them without disrupting schedule and usability. D says > > "suck it up for next X years while we fix it" or "You have some > >

Re: D versionning

2012-07-15 Thread Patrick Stewart
Walter Bright Wrote: > On 7/15/2012 4:08 PM, Patrick Stewart wrote: > > Second biggest flaw with D development is premature optimization opsession > > by > > large number of devs. "We haven't make it work quite yet as specs define, > > but > > lets

Re: D versionning

2012-07-15 Thread Patrick Stewart
bearophile Wrote: > Patrick Stewart: > > > Both languages have programming bugs and bad decisions. Python > > fix them without disrupting schedule and usability. D says > > "suck it up for next X years while we fix it" or "You have some > >