From: Marek Behun <marek.behun@nic.cz>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-leds@vger.kernel.org, dmurphy@ti.com
Subject: Re: [PATCH] leds: Add documentation about possible subsystem improvements
Date: Mon, 28 Sep 2020 01:15:20 +0200 [thread overview]
Message-ID: <20200928011520.6e13e9aa@nic.cz> (raw)
In-Reply-To: <20200928011039.09260cff@nic.cz>
On Mon, 28 Sep 2020 01:10:39 +0200
Marek Behun <marek.behun@nic.cz> wrote:
> On Sun, 27 Sep 2020 22:33:09 +0200
> Pavel Machek <pavel@ucw.cz> wrote:
>
> >
> > Actually.. I started something. How do you like Rust?
> >
>
> I've never written anything in Rust. I am not opposed to the language,
> since I don't know much about it (although I've heart praise for Rust
> from some people), but am not much enthuiastic about this program in
> particular to be written in it.
>
> For embedded systems, for example, gcc was for a long time the only
> needed compiler. Now embedded system often need at least
> Python/Lua/Perl. If I wanted to embed this ledtool and it is written in
> Rust, I will need one more compiler and its environment.
>
> So if you insist on Rust for ledtool, I will most probably pass, but I
> am still interested in working on the kernel part of the LED subsystem.
>
> Marek
>
In fact until recently I managed to avoid Rust on my system (Gentoo),
and was annoyed when suddenly one library needed Rust as a dependency
(librsvg) and Rust had to be installed.
Not because of dislike of Rust, but because of dislike of the idea of
having compilers for 50 different languages on the system...
Marek
prev parent reply other threads:[~2020-09-27 23:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 9:33 [PATCH] leds: Add documentation about possible subsystem improvements Pavel Machek
2020-09-25 14:46 ` Marek Behun
2020-09-27 20:33 ` Pavel Machek
2020-09-27 23:10 ` Marek Behun
2020-09-27 23:15 ` Marek Behun [this message]
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=20200928011520.6e13e9aa@nic.cz \
--to=marek.behun@nic.cz \
--cc=dmurphy@ti.com \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
/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;
as well as URLs for NNTP newsgroup(s).