January 24, 2012
On 24 January 2012 02:37, Bernard Helyer <b.helyer@gmail.com> wrote:
> On Tuesday, 24 January 2012 at 02:17:09 UTC, Trass3r wrote:
>>
>> Adapt the bot or configure your client to ignore the bot. Plain simple.
>
>
> You know who else configured their client to ignore bots?
>
> Bin Laden.
>
> You thought I was going to say Hitler, didn't you? Well that's silly, Hitler was long dead before the invention of ARPANET, let alone the IRC protocol. I don't know how I can take technical advice from someone so confused about the timeline of history.

Godwin's Law.


-- 
Iain Buclaw

*(p < e ? p++ : p) = (c & 0x0f) + '0';
January 24, 2012
On Tue, 2012-01-24 at 08:40 +0000, Iain Buclaw wrote:
[...]
> 
> Godwin's Law.

Perhaps this could be turned into a variant of the game "Mornington Crescent"

http://en.wikipedia.org/wiki/Mornington_Crescent_(game)

:-)

-- 
Russel. ============================================================================= Dr Russel Winder      t: +44 20 7585 2200   voip: sip:russel.winder@ekiga.net 41 Buckmaster Road    m: +44 7770 465 077   xmpp: russel@russel.org.uk London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder


January 24, 2012
Brad Anderson Wrote:

> Recently there has been explosion in bug closures.  This has had the unfortunate side effect of making it difficult to have a conversation in #d IRC with the bot constantly announcing these changes.  I humbly request that those responsible slow down this behavior to a more tolerable level so we can talk uninterrupted in the #d IRC channel.  I hate to call out someone by name but Walter in particular has been completely out of line with the volume of notifications he's been generating recently.
> 
> I understand some people like bug closures and who am I to judge but there is a limit to what some of us can tolerate and it has been surpassed.
> 

Couldn't agree more. I've even been forced to increase the scrollback buffer of my IRC client in order to not miss conversation pieces while just fetching coffee, which of course uses up more RAM, not to say the extra tear on my scroll wheel isn't concerning too. I'm very tempted to file a bug that D has a technical memory leak, indirectly, but still, it's a very real problem. I see no other way of fixing this except write-locking the git repos, right? Could anyone fix this? I guess a temporary workaround could be if poeple used shorter names for the bugs. Like instead of "(ice) glue.c (67) :  assert failed with exit code 78" perhaps just "assrt fail lol". Or hey, perhaps even insert some conversation starters, like "assrt fail, btw, a developer walked into a foo *eelface*", that would be really great for those awkward silent moments on the IRC. Let's work together on this people! okthxbye!

January 24, 2012
24.01.2012 5:57, Brad Anderson пишет:
> Recently there has been explosion in bug closures.  This has had the
> unfortunate side effect of making it difficult to have a conversation in
> #d IRC with the bot constantly announcing these changes.  I humbly
> request that those responsible slow down this behavior to a more
> tolerable level so we can talk uninterrupted in the #d IRC channel.  I
> hate to call out someone by name but Walter in particular has been
> completely out of line with the volume of notifications he's been
> generating recently.
>
> I understand some people like bug closures and who am I to judge but
> there is a limit to what some of us can tolerate and it has been surpassed.
>
> I'm sorry it had to come to this.
>
> Regards,
> Brad Anderson

If people have a problem with #d IRC they should just disable technical messages they don't need. If they can't do that, it's their own problem. They are supposed to be programmers.

Have no idea why isn't such post the one and only reply.

Didn't want to hurt one's feelings but this will be the reply I would expect if I would ask such question.
January 24, 2012
On 1/24/12 4:16 PM, Denis Shelomovskij wrote:
> If people have a problem with #d IRC they should just disable technical
> messages they don't need. If they can't do that, it's their own problem.
> They are supposed to be programmers.
>
> Have no idea why isn't such post the one and only reply.

And I in turn am amazed by the number of people who didn't notice that Brad's post was … uhm, how do I put that … not entirely serious. For a clue, you might want to look up »A modest proposal«.

David,
thinking of all the poor babies
January 24, 2012
On 1/24/2012 2:17 AM, k wrote:
> Couldn't agree more. I've even been forced to increase the scrollback buffer
> of my IRC client in order to not miss conversation pieces while just fetching
> coffee, which of course uses up more RAM, not to say the extra tear on my
> scroll wheel isn't concerning too. I'm very tempted to file a bug that D has
> a technical memory leak, indirectly, but still, it's a very real problem. I
> see no other way of fixing this except write-locking the git repos, right?
> Could anyone fix this? I guess a temporary workaround could be if poeple used
> shorter names for the bugs. Like instead of "(ice) glue.c (67) :  assert
> failed with exit code 78" perhaps just "assrt fail lol". Or hey, perhaps even
> insert some conversation starters, like "assrt fail, btw, a developer walked
> into a foo *eelface*", that would be really great for those awkward silent
> moments on the IRC. Let's work together on this people! okthxbye!

A friend of mine, Hal Finney, once wrote a Basic interpreter for an embedded system. He was incredibly short on ROM, and used every trick to stuff that Basic interpreter in. One way to reduce size was to use one error message for every error; he chose:

   EH?

Only 3 bytes! We all thought it was awesome. His customer hated it, though.


January 24, 2012
On 1/24/2012 7:28 AM, David Nadlinger wrote:
> On 1/24/12 4:16 PM, Denis Shelomovskij wrote:
> And I in turn am amazed by the number of people who didn't notice that Brad's
> post was … uhm, how do I put that … not entirely serious. For a clue, you might
> want to look up »A modest proposal«.

These days, I always get downvoted for referring to "steenkin' badges". Apparently, nobody watches Bogart movies anymore. I guess I don't really blame them, his style of cool is obsolete.
January 24, 2012
On Tue, Jan 24, 2012 at 11:34 AM, Walter Bright <newshound2@digitalmars.com>wrote:

> On 1/24/2012 7:28 AM, David Nadlinger wrote:
>
>> On 1/24/12 4:16 PM, Denis Shelomovskij wrote:
>> And I in turn am amazed by the number of people who didn't notice that
>> Brad's
>> post was … uhm, how do I put that … not entirely serious. For a clue, you
>> might
>> want to look up »A modest proposal«.
>>
>
> These days, I always get downvoted for referring to "steenkin' badges". Apparently, nobody watches Bogart movies anymore. I guess I don't really blame them, his style of cool is obsolete.
>

Bogart?  I'm pretty sure that comes from a Weird Al Yankovic movie.

My age is showing,
Brad Anderson


January 24, 2012
On 01/24/12 05:21, bcs wrote:
> On 01/23/2012 06:10 PM, Walter Bright wrote:
>> On 1/23/2012 5:57 PM, Brad Anderson wrote:
>>> I understand some people like bug closures and who am I to judge but
>>> there is a
>>> limit to what some of us can tolerate and it has been surpassed.
>>
>> I live to make IRC users suffer. It's dessert after eating babies.
> 
> How appropriate, considering the title.

ThatsTheJoke.

January 24, 2012
On 1/24/12 1:34 PM, Walter Bright wrote:
> On 1/24/2012 7:28 AM, David Nadlinger wrote:
>> On 1/24/12 4:16 PM, Denis Shelomovskij wrote:
>> And I in turn am amazed by the number of people who didn't notice that
>> Brad's
>> post was … uhm, how do I put that … not entirely serious. For a clue,
>> you might
>> want to look up »A modest proposal«.
>
> These days, I always get downvoted for referring to "steenkin' badges".
> Apparently, nobody watches Bogart movies anymore. I guess I don't really
> blame them, his style of cool is obsolete.

I don't think it is. My prediction: when CGI actors pass the uncanny valley, people will love new movies with Bogart.

Andrei