Posted by: Anonymous
[ip: 88.76.58.41]
on January 19, 2008 01:43 AM
> Ordinary malloc()/free() leaks you can always fix, but GC leaks don't.
in D you can do both. write programs that only use GC, only new/delete, some GC, some new/delete, GC supported pooling, new/delete based pooling - you name it. and all that is easily accessible and non-confusingly designed.
> Yea, D might be cool to implement for that simple 4-6 week back-office project, but let's see you sell it for an, important, high-visibility corporate-wide or government organization project.
there's a huge space between 4-6 week projects and that high-profile corporate/gov. projects you're talking about. and D is surely ready to do bigger things than 4-6 week projects, as can be seen by looking at existing D projects.
Learn about Linux
Download Linux
Get Linux help
New D language pumps up programmer productivity
Posted by: Anonymous [ip: 88.76.58.41] on January 19, 2008 01:43 AMin D you can do both. write programs that only use GC, only new/delete, some GC, some new/delete, GC supported pooling, new/delete based pooling - you name it. and all that is easily accessible and non-confusingly designed.
> Yea, D might be cool to implement for that simple 4-6 week back-office project, but let's see you sell it for an, important, high-visibility corporate-wide or government organization project.
there's a huge space between 4-6 week projects and that high-profile corporate/gov. projects you're talking about. and D is surely ready to do bigger things than 4-6 week projects, as can be seen by looking at existing D projects.
#