From: Igor <lanthruster@gmail.com>
To: Ciaran McCreesh <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] minimalistic emerge
Date: Fri, 8 Aug 2014 19:23:21 +0400 [thread overview]
Message-ID: <53e4eb6b.0190700a.5f01.2a15@mx.google.com> (raw)
In-Reply-To: <20140808142203.777a1818@googlemail.com>
[-- Attachment #1: Type: text/plain, Size: 3607 bytes --]
Hello Ciaran,
Friday, August 8, 2014, 5:22:03 PM, you wrote:
>> get the result - install the application you need, leaving everything
>> else AS IS untouched and stable?
> cave resolve --lazy :P
A great option name :-) I liked it. Wish it were there.
Updating only the minimum necessary packages required is natural, wide
system update is a wrong math model. There are regulations
in avionics, cybernetics and other life sensitive construction bureaus
prohibiting system wide updates. BTW - directly follows from nature.
Any complex bird is not updated on daily basis, it takes small steps,
small changes targeting only small fixes - natures is adaptive and
doesn't know where to move, it probes carefully, always backups, always
reversible, moves forward but very accurately, if the change
in a bird is deep the chance is that it will stop functioning and die - for
nature that means millions of years of genome programming is wasted. Whew,
a lot of work.
NATURE is VERY lazy, and that's why I liked your option name a lot :-) you
nailed it.
From Cybernetics:
Laziness is a built in algorithm. It controls system resources in case there
is no threat to the system purposes with higher priorities. In other words -
if what you're doing right now is well adopted to fulfill hard-coded in
genome high priority purposes - there IS NO NEED TO CHANGE anything.
GENTOO (and many other systems) in many ways violate the profound nature
laws found out by venerable scientists, therefore what is done in long
perspective is futile, it's more like painting the grass.
You need 100 times more effort and resources to keep grass painted, each
time you paint - a system wide update happens which is then REVERSED by nature.
May be not a good example - but reflecting.
One of the main built-in by nature perceptions of what is RIGHT or WRONG in human Genmoe
is time. After all our lifes are limited and the most precious what we have
is time.
Returning to our programming.
Anything what is designed by a programmer for a user should be first evaluated from
the time users spends. In fact you have no control over it - as a programmer you either
accept it or leave the trade. If user feels he spends time - the project is a failure.
Anything you ever design - should require no time for a user to achieve the
result. And finding and accessing what eats time is the virtue a talented programmer
has.
Those are problems we face with GENTOO design if only the team could clearly state
the problems and shift focus on their solution - GENTOO would be the greatest system
ever.
BUT
From Cybernetics:
As the environment changes - most systems are designed to adopt. Meaning there are many alternative
systems solving differently same tasks, not VERY differently but differently enough to function
in a situation where another system would cease. Many variants of the same system with variations exist
in nature.
That what keeps is pulling in different directions, we're moving somewhere as most of us are not
aware of deep algorithms inside of us which rules us so subtly.
The nature is the greatest system designer, we all have to learn from it.
PS
Jeroen knows an option, but he won't tell - he is from
GENTOO bug tracking service - no one can stand bug tracking for
more than 1 year and he is there for more than 5, so you reckon..
he is probably reading this right now - try to be very quiet...
--
Best regards,
Igor mailto:lanthruster@gmail.com
[-- Attachment #2: Type: text/html, Size: 4756 bytes --]
next prev parent reply other threads:[~2014-08-08 15:23 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-08 13:12 [gentoo-dev] minimalistic emerge Igor
2014-08-08 13:22 ` Ciaran McCreesh
2014-08-08 15:23 ` Igor [this message]
2014-08-08 15:36 ` hasufell
2014-08-08 15:53 ` Igor
2014-08-08 15:45 ` Ian Stakenvicius
2014-08-08 16:27 ` Igor
2014-08-08 16:40 ` Homer Parker
2014-08-08 17:26 ` Igor
2014-08-08 17:32 ` Homer Parker
2014-08-08 17:30 ` Ian Stakenvicius
2014-08-09 9:34 ` "Paweł Hajdan, Jr."
2014-08-09 15:25 ` Igor
2014-08-13 7:54 ` [OT] " Tom Wijsman
2014-08-08 16:31 ` Rich Freeman
2014-08-08 13:23 ` hasufell
2014-08-08 13:32 ` Jeroen Roovers
2014-08-08 15:14 ` Alan McKinnon
2014-08-13 8:13 ` Tom Wijsman
2014-08-08 15:51 ` Kent Fredric
2014-08-08 16:58 ` Igor
2014-08-08 17:29 ` Kent Fredric
2014-08-08 20:52 ` Igor
2014-08-08 21:33 ` Kent Fredric
2014-08-08 21:39 ` Ian Stakenvicius
2014-08-08 21:43 ` Kent Fredric
2014-08-09 14:56 ` Igor
2014-08-09 15:12 ` Chris Reffett
2014-08-09 17:10 ` Ciaran McCreesh
2014-08-13 8:20 ` Tom Wijsman
2014-08-13 13:17 ` hasufell
2014-08-09 19:30 ` Jeroen Roovers
2014-08-09 15:44 ` Chris Reffett
2014-08-09 15:46 ` Chris Reffett
2014-08-09 15:58 ` Chris Reffett
2014-08-08 19:34 ` Peter Stuge
2014-08-08 19:47 ` Ian Stakenvicius
2014-08-08 19:56 ` Kent Fredric
2014-08-08 20:16 ` Ian Stakenvicius
2014-08-09 2:14 ` Rich Freeman
2014-08-09 8:30 ` Peter Stuge
2014-08-08 21:04 ` Johannes Huber
2014-08-13 8:25 ` Tom Wijsman
2014-08-09 3:07 ` [gentoo-dev] " Duncan
2014-08-09 8:34 ` Peter Stuge
2014-08-09 11:03 ` Duncan
2014-08-09 11:06 ` hasufell
2014-08-09 12:16 ` Ambroz Bizjak
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=53e4eb6b.0190700a.5f01.2a15@mx.google.com \
--to=lanthruster@gmail.com \
--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