On Monday, 15 December 2014 at 10:11:37 UTC, ketmar via Digitalmars-d wrote:
> ... i'm accepting the fact that D is doomed to be a toy, which
> ocasionally used here and there. i tried to fight with this, but this fight is lost before it's started. and now i surrender.

Well I don't post too much but I'm in this Forum almost every day. And you contributes a lot answering many questions, so please don't give up. :)

Matheus.

PS: Sorry my english!

On Mon, 15 Dec 2014 14:00:34 +0000
MattCoder via Digitalmars-d <digitalmars-d@puremagic.com> wrote:

> On Monday, 15 December 2014 at 10:11:37 UTC, ketmar via Digitalmars-d wrote:
> > ... i'm accepting the fact that D is doomed to be a toy, which ocasionally used here and there. i tried to fight with this, but this fight is lost before it's started. and now i surrender.
> 
> Well I don't post too much but I'm in this Forum almost every day. And you contributes a lot answering many questions, so please don't give up. :)
thank you. i'm not dropping D (i'm still using it, and i like it), i
just don't want to try to contribute source code patches anymore. ;-)

On Monday, 15 December 2014 at 11:27:30 UTC, Mengu wrote:
> p.s. i know i have your sympathy because of my all lower-case writing despite the hate we get. :-)

Ah! That's why I can never parse ketmar's posts at a glance and keep getting lost. Full stops followed by capital letters make great visual anchors. The whole I v.s. i thing is trivial in comparison.

On Monday, 15 December 2014 at 14:44:03 UTC, John Colvin wrote:
> On Monday, 15 December 2014 at 11:27:30 UTC, Mengu wrote:
>> p.s. i know i have your sympathy because of my all lower-case writing despite the hate we get. :-)
>
> Ah! That's why I can never parse ketmar's posts at a glance and keep getting lost. Full stops followed by capital letters make great visual anchors. The whole I v.s. i thing is trivial in comparison.

actually with correct punctuation, writings with all lower-case letters are a lot easier to read. it just flows.

On Monday, 15 December 2014 at 15:26:57 UTC, Mengu wrote:
> On Monday, 15 December 2014 at 14:44:03 UTC, John Colvin wrote:
>> On Monday, 15 December 2014 at 11:27:30 UTC, Mengu wrote:
>>> p.s. i know i have your sympathy because of my all lower-case writing despite the hate we get. :-)
>>
>> Ah! That's why I can never parse ketmar's posts at a glance and keep getting lost. Full stops followed by capital letters make great visual anchors. The whole I v.s. i thing is trivial in comparison.
>
> actually with correct punctuation, writings with all lower-case letters are a lot easier to read. it just flows.

I personally find a strong effect in the opposite direction. Are you saying that you personally find it easier or are you referring to a body of decent research that has demonstrated this?

Eh, possibly if you're used to a language - like english - that's mostly only lowercase letters in the first place.

I don't see what your problem with comprehending "GH is what everyone is using for contributions, therefore if you're planning on making a contribution you should probable do it there" is. Your entire argument seems to be based on "I don't like it, therefore I should not have to use it" - even if that's where the project development is taking place. I'm not entirely sure how that makes sense to you.

On Monday, 15 December 2014 at 15:26:57 UTC, Mengu wrote:
> On Monday, 15 December 2014 at 14:44:03 UTC, John Colvin wrote:
>> On Monday, 15 December 2014 at 11:27:30 UTC, Mengu wrote:
>>> p.s. i know i have your sympathy because of my all lower-case writing despite the hate we get. :-)
>>
>> Ah! That's why I can never parse ketmar's posts at a glance and keep getting lost. Full stops followed by capital letters make great visual anchors. The whole I v.s. i thing is trivial in comparison.
>
> actually with correct punctuation, writings with all lower-case letters are a lot easier to read. it just flows.

On 12/14/14 4:41 AM, ketmar via Digitalmars-d wrote:
> there is preapproved bounty ER in bugzilla:
> https://issues.dlang.org/show_bug.cgi?id=11070
>
> i did that, where is my bounty?!
>
> but talking seriously, i don't need any bounty, i just want somebody to
> take a look at that and either tell me what to fix or integrate it in
> mainline. along with this one: https://issues.dlang.org/show_bug.cgi?id=13526
>
> they are small, but nice additions. i'm using that patches on dayly
> basis and didn't found any troubles with them. please, take those, so i
> can throw away two .patch files from my build directory! ;-)

It's already been said, and by me before this, use github. If you don't you have relegated yourself to this existence you so despise.

As a practical matter, I see emails for every message posted on github. I may not respond to all of them due to my limited time, but I do look at ones that pertain to my area in the runtime/phobos. I can see the patch online, without having to download it, apply it and test it. I can add comments to specific lines. The auto tester tests it. Only github PRs will be accepted into mainline, not patches on bugzilla, because of the auto tester. This means that your patch must be turned into a PR, and then whoever turns it in must support it if it needs fixing. A previous incarnation of this "development process" did not go well, as your response was "what, peasant? I don't care, that's my patch take it or leave it." It doesn't surprise me that your patch was "missed" or ignored.

I can tell you from experience before we used github, development on D was so freaking slow, you would be complaining to no end if it were still that way. The PR system is orders of magnitude better and faster.

If you want patches included quickly (or at least quicker), add them as PRs to github, and be prepared to fix them if necessary. If you think D ecosystem will crash and burn because of your intransigence, you are free to have that opinion, but most of us here do not share it (and you aren't the first to express it). I don't think your contributions are low-value, just high overhead. Most of us don't have time for that.

-Steve

On Mon, 15 Dec 2014 11:50:32 -0500
Steven Schveighoffer via Digitalmars-d <digitalmars-d@puremagic.com>
wrote:

> your response was "what, peasant? I don't care, that's my patch take it or leave it." It doesn't surprise me that your patch was "missed" or ignored.
this is the equal answer to "github or GTFO".

and this is not only about this particular patch, it's about the things i already mentioned in this discussion. such as having tools that says that they are for patches and then blaming the people who used that tools per disclaimer as "don't do what we wrote here!" see the picture?

that's one of the reasons for D to always be toy hobbyst project: inconsistency and treating "cosmetic issues" as "noops". no C++ interop will cure that. and this makes me sad panda.

On 12/15/14 12:47 PM, ketmar via Digitalmars-d wrote:
> On Mon, 15 Dec 2014 11:50:32 -0500
> Steven Schveighoffer via Digitalmars-d <digitalmars-d@puremagic.com>
> wrote:
>
>> your response was "what, peasant? I don't care, that's my patch take it
>> or leave it." It doesn't surprise me that your patch was "missed" or
>> ignored.
> this is the equal answer to "github or GTFO".
>
> and this is not only about this particular patch, it's about the things
> i already mentioned in this discussion. such as having tools that says
> that they are for patches and then blaming the people who used that
> tools per disclaimer as "don't do what we wrote here!" see the picture?

Let's say, we remove the "proposed patch" text from the "Add an attachment" field. All good? You will use github then?

-Steve

On Mon, 15 Dec 2014 12:51:47 -0500
Steven Schveighoffer via Digitalmars-d <digitalmars-d@puremagic.com>
wrote:

> > and this is not only about this particular patch, it's about the things i already mentioned in this discussion. such as having tools that says that they are for patches and then blaming the people who used that tools per disclaimer as "don't do what we wrote here!" see the picture?
> 
> Let's say, we remove the "proposed patch" text from the "Add an attachment" field. All good? You will use github then?

i will not use github under any circumstances, but this will be one little step along the long "consistency road". at least nobody will be blamed for using bugzilla according to it's disclaimer. and surely i will stop ranting about that, 'cause i deliberately chose GTFO instead of github, according to rules.