public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: heroxbd@gentoo.org
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Portage QOS
Date: Fri, 10 Jan 2014 23:05:12 +0900	[thread overview]
Message-ID: <861u0g7x0n.fsf@moguhome00.in.awa.tohoku.ac.jp> (raw)
In-Reply-To: <52cfeffd.6d2a700a.56f3.ffff9763@mx.google.com> (Igor's message of "Fri, 10 Jan 2014 17:05:00 +0400")

Hi Igor,

Igor <lanthruster@gmail.com> writes:

> I've been using C/C++ since school it's fast, even bad code is working fast.
>
> I WOULD NEVER BELIVE PYTHON IS AS FAST AS C++ with math algorithms
> that do calculate staff and not call functions from pre-complied
> objects written in C/C++.
>
> It's crazy that you're even trying to state it. Take a look at what
> Python is producing in disasm and then look at it in G++.
>
>>> So why do we send Gentoo for food riding on Python? If it were death
>>> we send Gentoo for then I would choose Python but food?
>
>> I'm finding it very hard to stay polite, because ... honestly?
>> You have no idea what you're talking about.
>
> Or vice versa.
>
>> If you want things to change - hire a few of us fulltime to work on
>> things, and you'll get the change you want.
>> Until then there's no need to point out that we are lacking manpower to
>> do large-scale changes, because that's been a constant in most
>> opensource projects since the 1960s.
>
>> Less talking, more doing - provide patches and stop polluting our
>> mailing list with your madness.
>
> See tge subject of this letter. The whole point of this conversation is that
> I offered to design it and program it and offered HARDWARE for it but we
> can't get to the point because it's not clear for everyone if we need it.
>
> If high command not needing it it will find means to kill it and I'm
> very busy, really very busy - can't afford to spend that much time on
> something not useful.

I appreciate your intension to make Gentoo better, at the same time I
could not share the view with you.

Here is the checklist for you:

1. I got a brilliant idea! goto 2
2. Can I realize it by myself?
   Y, goto 6; N goto 3
3. Can I convince someone to do it for me?
   Y, goto 6; N goto 4
4. Can I hire someone to do it for me?
   Y, goto 6; N goto 5
5. Nothing could be achieved :(
6. After rounds of hard work, it comes true :D

Seems that you got stuck at 5. Sorry if you are not willing to adjust
your attitude, your subsequent will be ignored.

Some of the details of your proposal do interest me, such as an
automatic build.log / emerge --info uploader. Supporting mail reply to
bugzilla will even be cooler (which can be used to upload build.log and
emerge --info of course).

Cheers,
Benda


  parent reply	other threads:[~2014-01-10 14:05 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-09  7:24 [gentoo-dev] Portage QOS LTHR
2014-01-09  8:12 ` Alec Warner
2014-01-09 12:44   ` Igor
2014-01-09 14:12     ` Christopher Schwan
2014-01-09 15:26       ` Igor
2014-01-09 15:55         ` Jeroen Roovers
2014-01-09 16:37           ` Igor
2014-01-10  0:27             ` heroxbd
2014-01-10 12:41               ` Igor
2014-01-10 13:51                 ` Rich Freeman
2014-01-10  0:16         ` heroxbd
2014-01-10  0:31           ` Patrick Lauer
2014-01-10  1:19             ` Tom Wijsman
2014-01-10  1:52               ` Patrick McLean
2014-01-10  2:40                 ` Tom Wijsman
2014-01-10  6:17                 ` Brian Dolbec
2014-01-10 18:14                 ` Ciaran McCreesh
2014-01-10  7:54             ` heroxbd
2014-01-10 18:11             ` Ciaran McCreesh
2014-01-11  3:57               ` Patrick Lauer
2014-01-10  1:02           ` Tom Wijsman
2014-01-10  9:10             ` heroxbd
2014-01-10 14:54               ` Tom Wijsman
2014-01-10 12:23           ` Igor
2014-01-10 12:30             ` René Neumann
2014-01-10 12:30           ` Igor
2014-01-10 12:39             ` Patrick Lauer
2014-01-10 13:05               ` Igor
2014-01-10 13:18                 ` René Neumann
2014-01-10 18:19                   ` Ciaran McCreesh
2014-01-10 19:06                     ` René Neumann
2014-01-10 14:05                 ` heroxbd [this message]
2014-01-12 10:47                 ` [gentoo-dev] " Steven J. Long
2014-01-10 13:10               ` [gentoo-dev] " Igor
2014-01-10 14:02                 ` Rich Freeman
2014-01-10 15:16                   ` Tom Wijsman
2014-01-10 18:12           ` Ciaran McCreesh
2014-01-09 15:49     ` Ben Kohler
2014-01-09 16:11       ` Igor
2014-01-09 17:59     ` [gentoo-dev] " Duncan
2014-01-09 20:42       ` Igor
2014-01-09 21:08         ` Chris Reffett
2014-01-10 12:10           ` Igor
2014-01-10 12:26             ` René Neumann
2014-01-10 12:52               ` Igor
2014-01-10 12:57                 ` René Neumann
2014-01-10 15:39                 ` Tom Wijsman
2014-01-10 16:36             ` Mike Frysinger
2014-01-10 18:17             ` Greg KH
2014-01-10 19:38           ` Duncan
2014-01-10 22:36             ` heroxbd
2014-01-11  1:28               ` Duncan
2014-01-09 19:35 ` [gentoo-dev] " yac
2014-01-11 15:00 ` Naohiro Aota
2014-01-12 10:28   ` Igor
2014-01-12 19:31   ` Igor
2014-01-12 19:31   ` Igor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=861u0g7x0n.fsf@moguhome00.in.awa.tohoku.ac.jp \
    --to=heroxbd@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox