On Wednesday, 11 March 2015 at 16:35:22 UTC, Andrei Alexandrescu
wrote:
I would agree it would be bad if dustmite and dub were
locked-in to only work with dmd. Is that the case?
No, both support all three D compilers.
On Wednesday, 11 March 2015 at 08:00:22 UTC, Vladimir Panteleev
wrote:
On Wednesday, 11 March 2015 at 07:32:48 UTC, Andrei
Alexandrescu wrote:
It doesn't seem so to me. You find easy weaknesses in my
vision and pump on them instead of working on making it
stronger. That's the easy but that
On 2015-03-11 17:27, Anon wrote:
Ignoring that for a moment, where does it stop? Do we include an
editor? [sarcasm] Why not? Every D developer needs to edit their
code! Let's go ahead and call Eclipse+DDT the standard D editor,
and bundle that with dmd. [/sarcasm]
I don't see why not. Both
On Wednesday, 11 March 2015 at 08:57:14 UTC, Rikki Cattermole
wrote:
On 11/03/2015 9:00 p.m., Vladimir Panteleev wrote:
On Wednesday, 11 March 2015 at 07:32:48 UTC, Andrei
Alexandrescu wrote:
It doesn't seem so to me. You find easy weaknesses in my
vision and
pump on them instead of working on
On Wednesday, 11 March 2015 at 07:19:57 UTC, Vladimir Panteleev
wrote:
What is indubitably, actually, very important, and something
I'm surprised you haven't pushed for since long ago, is making
it EASY to get more things. Dub absolutely must be a part of D,
and not today but one or more years
On Thursday, 12 March 2015 at 07:44:01 UTC, Jacob Carlborg wrote:
On 2015-03-11 17:27, Anon wrote:
Ignoring that for a moment, where does it stop? Do we include
an
editor? [sarcasm] Why not? Every D developer needs to edit
their
code! Let's go ahead and call Eclipse+DDT the standard D
On Thursday, 12 March 2015 at 07:44:01 UTC, Jacob Carlborg wrote:
On 2015-03-11 17:27, Anon wrote:
Ignoring that for a moment, where does it stop? Do we include
an
editor? [sarcasm] Why not? Every D developer needs to edit
their
code! Let's go ahead and call Eclipse+DDT the standard D
On 3/11/15 9:27 AM, Anon wrote:
On Wednesday, 11 March 2015 at 07:19:57 UTC, Vladimir Panteleev wrote:
What is indubitably, actually, very important, and something I'm
surprised you haven't pushed for since long ago, is making it EASY to
get more things. Dub absolutely must be a part of D, and
On Wednesday, 11 March 2015 at 05:43:17 UTC, Vladimir Panteleev
wrote:
Furthermore, Vibe is a library, with its own possibly-unstable
API. Some projects may want to use an older version of Vibe
with a newer version of the compiler. This is hypothetical,
correct me if I'm wrong.
I think your
On Wednesday, 11 March 2015 at 08:00:22 UTC, Vladimir Panteleev
wrote:
On Wednesday, 11 March 2015 at 07:32:48 UTC, Andrei
Alexandrescu wrote:
It doesn't seem so to me. You find easy weaknesses in my
vision and pump on them instead of working on making it
stronger. That's the easy but that
On Wednesday, 11 March 2015 at 08:57:14 UTC, Rikki Cattermole
wrote:
On 11/03/2015 9:00 p.m., Vladimir Panteleev wrote:
On Wednesday, 11 March 2015 at 07:32:48 UTC, Andrei
Alexandrescu wrote:
It doesn't seem so to me. You find easy weaknesses in my
vision and
pump on them instead of working on
On Wednesday, 11 March 2015 at 16:35:22 UTC, Andrei Alexandrescu
wrote:
On 3/11/15 9:27 AM, Anon wrote:
Not to mention, putting extra tools like dustmite and dub in
dmd
will only ever benefit dmd users, not those of us who use ldc
or
gdc.
That's entirely reasonable. Each distribution has
On Wednesday, 11 March 2015 at 05:43:17 UTC, Vladimir Panteleev
wrote:
On Wednesday, 11 March 2015 at 05:16:38 UTC, Andrei
Alexandrescu wrote:
That doesn't ensure e.g. version compatibility etc. I repeat:
my vision is to make vibe readily available with the D
distribution, just like druntime
On 3/10/15 11:32 PM, Vladimir Panteleev wrote:
On Wednesday, 11 March 2015 at 06:30:52 UTC, Andrei Alexandrescu wrote:
One command away is too much.
Not when the build tool will fetch dependencies as part of the build
process anyway. A 10-second wait is not worth the disadvantages of
moving
On Wednesday, 11 March 2015 at 06:56:27 UTC, Andrei Alexandrescu
wrote:
On 3/10/15 11:52 PM, Vladimir Panteleev wrote:
I can only urge you to consult with someone deeply involved
with Vibe
(e.g. Sonke), as well as someone who uses Vibe and Dub heavily
in
production, before forcing a decision.
On 2015-03-11 07:45, Andrei Alexandrescu wrote:
Vladimir, please work with me on this. This is clearly subjective so
it's really what you believe is good vs. what I believe is good. I want
to make sure vibe releases are in sync and guaranteed to work with dmd,
thus making for a perfectly smooth
On 2015-03-11 07:56, Andrei Alexandrescu wrote:
Sönke was up for it last time we communicated. This isn't forcing any
decision as much as pushing things in order toward a greater goal. --
Andrei
I agree with Dicebot and Vladimir that including vibe.d without Dub
might cause more harm than
On Wednesday, 11 March 2015 at 06:45:17 UTC, Andrei Alexandrescu
wrote:
I want to make sure vibe releases are in sync and guaranteed to
work with dmd, thus making for a perfectly smooth experience.
How will bundling Vibe with D achieve that goal?
What will ACTUALLY change by bundling Vibe
On 3/11/15 12:19 AM, Vladimir Panteleev wrote:
On Wednesday, 11 March 2015 at 06:45:17 UTC, Andrei Alexandrescu wrote:
I want to make sure vibe releases are in sync and guaranteed to work
with dmd, thus making for a perfectly smooth experience.
How will bundling Vibe with D achieve that goal?
Vladimir Panteleev wrote in message
news:rexuctylycuzskceb...@forum.dlang.org...
Including Dub is MUCH more important than including Vibe.
I am speaking from my limited experience, so please correct me if I'm
wrong, but:
You're completely right.
On 3/10/15 10:43 PM, Vladimir Panteleev wrote:
Including Vibe without Dub is certainly a mistake, because
inter-component versioning relies on Dub.
Fine, let's include dub too.
And if you have Dub, Vibe and
its components (including any older versions of such) are, like I said,
a command
On Wednesday, 11 March 2015 at 06:30:52 UTC, Andrei Alexandrescu
wrote:
One command away is too much.
Not when the build tool will fetch dependencies as part of the
build process anyway. A 10-second wait is not worth the
disadvantages of moving Vibe into D.
On Wednesday, 11 March 2015 at 06:45:17 UTC, Andrei Alexandrescu
wrote:
On 3/10/15 11:32 PM, Vladimir Panteleev wrote:
On Wednesday, 11 March 2015 at 06:30:52 UTC, Andrei
Alexandrescu wrote:
One command away is too much.
Not when the build tool will fetch dependencies as part of the
build
On 3/11/15 12:17 AM, Jacob Carlborg wrote:
How about including both Dub and vibe.d?
That sounds good. -- Andrei
On Wednesday, 11 March 2015 at 07:32:48 UTC, Andrei Alexandrescu
wrote:
On 3/11/15 12:19 AM, Vladimir Panteleev wrote:
What will ACTUALLY change by bundling Vibe with D?
Many people know of D but not of vibe.
Precedent shows that this does not work. Including Dustmite with
D did not solve
On Wednesday, 11 March 2015 at 07:32:48 UTC, Andrei Alexandrescu
wrote:
It doesn't seem so to me. You find easy weaknesses in my vision
and pump on them instead of working on making it stronger.
That's the easy but that business won't work, and here are the
reasons why approach. The harder
On 3/10/15 11:52 PM, Vladimir Panteleev wrote:
I can only urge you to consult with someone deeply involved with Vibe
(e.g. Sonke), as well as someone who uses Vibe and Dub heavily in
production, before forcing a decision.
Sönke was up for it last time we communicated. This isn't forcing any
On Wednesday, 11 March 2015 at 06:30:52 UTC, Andrei Alexandrescu
wrote:
On 3/10/15 10:43 PM, Vladimir Panteleev wrote:
Including Vibe without Dub is certainly a mistake, because
inter-component versioning relies on Dub.
Fine, let's include dub too.
There is 1.0.0 milestone in dub GitHub
On 3/11/15 1:10 AM, Vladimir Panteleev wrote:
On Wednesday, 11 March 2015 at 06:56:27 UTC, Andrei Alexandrescu wrote:
On 3/10/15 11:52 PM, Vladimir Panteleev wrote:
I can only urge you to consult with someone deeply involved with Vibe
(e.g. Sonke), as well as someone who uses Vibe and Dub
On Wednesday, 11 March 2015 at 06:56:27 UTC, Andrei Alexandrescu
wrote:
On 3/10/15 11:52 PM, Vladimir Panteleev wrote:
I can only urge you to consult with someone deeply involved
with Vibe
(e.g. Sonke), as well as someone who uses Vibe and Dub heavily
in
production, before forcing a decision.
On 3/10/15 10:29 PM, Dicebot wrote:
On Wednesday, 11 March 2015 at 05:16:38 UTC, Andrei Alexandrescu wrote:
That doesn't ensure e.g. version compatibility etc. I repeat: my
vision is to make vibe readily available with the D distribution, just
like druntime and phobos. Of course dub is nice to
On Tuesday, 10 March 2015 at 22:41:32 UTC, Andrei Alexandrescu
wrote:
3. As I articulated in the vision document, we aim at making
vibe.d an integral part of the D distribution. That's more than
a packaging issue: (a) vibe.d must follow the same release
process, perhaps even same version
On 11/03/2015 9:00 p.m., Vladimir Panteleev wrote:
On Wednesday, 11 March 2015 at 07:32:48 UTC, Andrei Alexandrescu wrote:
It doesn't seem so to me. You find easy weaknesses in my vision and
pump on them instead of working on making it stronger. That's the easy
but that business won't work, and
On 2015-03-11 08:47, Vladimir Panteleev wrote:
If you want to increase Vibe's visibility, adding a few links to
dlang.org will serve this goal much better.
I agree. Bundle Dub and make vibe.d clearly visible on dlang.org.
--
/Jacob Carlborg
On 11/03/2015 11:04 p.m., Paolo Invernizzi wrote:
On Wednesday, 11 March 2015 at 08:57:14 UTC, Rikki Cattermole wrote:
On 11/03/2015 9:00 p.m., Vladimir Panteleev wrote:
On Wednesday, 11 March 2015 at 07:32:48 UTC, Andrei Alexandrescu wrote:
It doesn't seem so to me. You find easy weaknesses
On 3/11/15 1:00 AM, Vladimir Panteleev wrote:
On Wednesday, 11 March 2015 at 07:32:48 UTC, Andrei Alexandrescu wrote:
It doesn't seem so to me. You find easy weaknesses in my vision and
pump on them instead of working on making it stronger. That's the easy
but that business won't work, and here
On 3/11/15 3:53 AM, John Colvin wrote:
On Tuesday, 10 March 2015 at 22:41:32 UTC, Andrei Alexandrescu wrote:
3. As I articulated in the vision document, we aim at making vibe.d an
integral part of the D distribution. That's more than a packaging
issue: (a) vibe.d must follow the same release
On Wednesday, 11 March 2015 at 07:01:02 UTC, Meta wrote:
On Wednesday, 11 March 2015 at 06:56:27 UTC, Andrei
Alexandrescu wrote:
On 3/10/15 11:52 PM, Vladimir Panteleev wrote:
I can only urge you to consult with someone deeply involved
with Vibe
(e.g. Sonke), as well as someone who uses Vibe
On 2015-03-11 08:47, Vladimir Panteleev wrote:
On Wednesday, 11 March 2015 at 07:32:48 UTC, Andrei Alexandrescu wrote:
On 3/11/15 12:19 AM, Vladimir Panteleev wrote:
What happens if a regression occurs in Vibe just before a D release? Do
we block the release for the sake of Vibe?
Yes.
On Saturday, 7 March 2015 at 04:54:38 UTC, David Soria Parra
wrote:
Hi,
I've been working with Martin Nowak and Andrei in the last few
weeks to get ideas and write up a DIP on D's release process.
With D maturing more and more I believe it is time to formalize
the release process and do a
On Tuesday, 10 March 2015 at 22:41:32 UTC, Andrei Alexandrescu
wrote:
3. As I articulated in the vision document, we aim at making
vibe.d an integral part of the D distribution. That's more than
a packaging issue: (a) vibe.d must follow the same release
process, perhaps even same version
On 3/10/15 8:43 PM, Vladimir Panteleev wrote:
On Tuesday, 10 March 2015 at 22:41:32 UTC, Andrei Alexandrescu wrote:
3. As I articulated in the vision document, we aim at making vibe.d an
integral part of the D distribution. That's more than a packaging
issue: (a) vibe.d must follow the same
On Wednesday, 11 March 2015 at 05:16:38 UTC, Andrei Alexandrescu
wrote:
That doesn't ensure e.g. version compatibility etc. I repeat:
my vision is to make vibe readily available with the D
distribution, just like druntime and phobos. Of course dub is
nice to include as well but not my main
On Wednesday, 11 March 2015 at 05:16:38 UTC, Andrei Alexandrescu
wrote:
That doesn't ensure e.g. version compatibility etc. I repeat:
my vision is to make vibe readily available with the D
distribution, just like druntime and phobos. Of course dub is
nice to include as well but not my main
On Tuesday, 10 March 2015 at 22:41:32 UTC, Andrei Alexandrescu
wrote:
On 3/6/15 8:54 PM, David Soria Parra wrote:
Hi,
I've been working with Martin Nowak and Andrei in the last few
weeks to
get ideas and write up a DIP on D's release process. With D
maturing
more and more I believe it is
On 3/6/15 8:54 PM, David Soria Parra wrote:
Hi,
I've been working with Martin Nowak and Andrei in the last few weeks to
get ideas and write up a DIP on D's release process. With D maturing
more and more I believe it is time to formalize the release process and
do a time based release process in
Nice to see more attention to this topic. On a negative side, it
doesn't seem to be that different from what we already supposed
to have (though it seems to imply getting rid of those annoying
cherry-picks, if yes, that is pretty good)
In my opinion two main problems with proposed scheme are
On 7 Mar 2015 19:05, Dicebot via Digitalmars-d
digitalmars-d@puremagic.com wrote:
Nice to see more attention to this topic. On a negative side, it doesn't
seem to be that different from what we already supposed to have (though it
seems to imply getting rid of those annoying cherry-picks, if
On Sat, Mar 07, 2015 at 07:15:12PM +, Iain Buclaw via Digitalmars-d wrote:
[...]
One wishlist to the dlang website would be to have versioned
documentation. For instance, pydocs let you switch between versions
of a library so you can read the documentation relevant to your
installed D
On Saturday, 7 March 2015 at 21:33:07 UTC, H. S. Teoh wrote:
On Sat, Mar 07, 2015 at 07:15:12PM +, Iain Buclaw via
Digitalmars-d wrote:
[...]
One wishlist to the dlang website would be to have versioned
documentation. For instance, pydocs let you switch between
versions
of a library so
Hi,
I've been working with Martin Nowak and Andrei in the last few
weeks to get ideas and write up a DIP on D's release process.
With D maturing more and more I believe it is time to formalize
the release process and do a time based release process in order
to make release processes more
51 matches
Mail list logo
