From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Idea: use menu hook to implement the savedefault command
Date: Wed, 13 Aug 2008 14:38:15 +0200 [thread overview]
Message-ID: <20080813123815.GA26618@thorin> (raw)
In-Reply-To: <1218629514.8757.27.camel@localhost>
On Wed, Aug 13, 2008 at 02:11:54PM +0200, Javier Martín wrote:
> El mié, 13-08-2008 a las 13:48 +0200, Robert Millan escribió:
> > On Wed, Aug 13, 2008 at 01:36:44PM +0200, Javier Martín wrote:
> > > It might be unnecessarily complex, yes. What about a C#-delegate-like
> > > approach? e.g.:
> > >
> > > function myhook() {
> > > save_env
> > > }
> >
> > While in the process of designing interfaces, finding inspiration in patent
> > encumbered technologies is one of the last things I would recommend.
> While parts of the .NET class library most certainly contain patented
> code, the C# language itself is part of an ECMA specification, and thus
> the delegate _syntax_ (not the actual implementation) would be safe to
> use... Or so I think - patents make my mind spin T_T
Being part of ECMA isn't any garantee of not being patent encumbered. ECMA
will happily bless any specification you give them, even if it contains
technical flaws, provided it's accompanied by enough money (OOXML is a good
example of this).
Last I checked, Microsoft had different patent policies for parts inside
the spec than for parts outside of it, but they're both written in complex
wording with lots of requisites that makes it very difficult to be sure the
code will be free for every user.
Since there isn't any real benefit for us in using their technology as a
reference, I believe it's much better to avoid the problem altogether by
not doing so.
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
next prev parent reply other threads:[~2008-08-13 12:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-11 21:03 Idea: use menu hook to implement the savedefault command Bean
2008-08-11 21:32 ` Robert Millan
2008-08-12 1:27 ` Bean
2008-08-12 8:52 ` Robert Millan
2008-08-12 9:38 ` Bean
2008-08-12 10:15 ` Robert Millan
2008-08-12 10:38 ` Bean
2008-08-12 10:44 ` Robert Millan
2008-08-12 10:52 ` Bean
2008-08-13 10:31 ` Marco Gerards
2008-08-13 11:36 ` Javier Martín
2008-08-13 11:48 ` Robert Millan
2008-08-13 12:11 ` Javier Martín
2008-08-13 12:38 ` Robert Millan [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-08-11 21:02 Bean
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=20080813123815.GA26618@thorin \
--to=rmh@aybabtu.com \
--cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.