From: NeilBrown <nfbrown@suse.de>
To: "James Bottomley" <James.Bottomley@HansenPartnership.com>
Cc: "Laurent Pinchart" <laurent.pinchart@ideasonboard.com>,
"Jens Axboe" <axboe@kernel.dk>,
"Christoph Hellwig" <hch@infradead.org>,
"Miguel Ojeda" <miguel.ojeda.sandonis@gmail.com>,
"ksummit" <ksummit-discuss@lists.linuxfoundation.org>,
ksummit@lists.linux.dev
Subject: Re: [MAINTAINER SUMMIT] Are we becoming too fearful? [was Re: [TECH TOPIC] Rust]
Date: Thu, 23 Jun 2022 09:13:22 +1000 [thread overview]
Message-ID: <165593960233.4786.4776751165554098218@noble.neil.brown.name> (raw)
In-Reply-To: <ca6243160b36aa42f4d0ad23853b84e57ca366f1.camel@HansenPartnership.com>
On Mon, 20 Jun 2022, James Bottomley wrote:
>
> I think there's a growing problem in Linux which is exemplified by this
> Rust debate but which goes way beyond it: We're becoming too fearful of
> making big decisions to sustain innovation in some areas. This really
> is a creeping cancer of inertia that has destroyed many projects before
> us and if we're not careful, we'll go the same way.
Is this because Linux is just too big? Are we squeezing too much into
one project, and becoming afraid to push on one piece for fear of
breaking another?
Of course, breaking Linux into separate pieces would mean we would need
to create APIs that were at least a little bit stable. But it might
also mean that individual sub-projects could take risks and either
flourish or die without an undue impact on the rest of the ecosystem.
NeilBrown
next prev parent reply other threads:[~2022-06-22 23:13 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-18 20:33 [TECH TOPIC] Rust Miguel Ojeda
2022-06-18 20:42 ` Laurent Pinchart
2022-06-18 20:42 ` [Ksummit-discuss] " Laurent Pinchart
2022-06-18 20:44 ` Laurent Pinchart
2022-06-18 20:44 ` [Ksummit-discuss] " Laurent Pinchart
2022-06-18 20:49 ` Miguel Ojeda
2022-06-19 6:13 ` Christoph Hellwig
2022-06-19 6:13 ` [Ksummit-discuss] " Christoph Hellwig
2022-06-19 10:04 ` Laurent Pinchart
2022-06-19 10:04 ` [Ksummit-discuss] " Laurent Pinchart
2022-06-19 12:56 ` James Bottomley
2022-06-19 12:56 ` [Ksummit-discuss] " James Bottomley
2022-06-19 13:19 ` Jens Axboe
2022-06-19 13:19 ` [Ksummit-discuss] " Jens Axboe
2022-06-19 13:53 ` Laurent Pinchart
2022-06-19 13:53 ` [Ksummit-discuss] " Laurent Pinchart
2022-06-19 14:27 ` James Bottomley
2022-06-19 14:27 ` [Ksummit-discuss] " James Bottomley
2022-06-19 14:45 ` [MAINTAINER SUMMIT] Are we becoming too fearful? [was Re: [TECH TOPIC] Rust] James Bottomley
2022-06-19 14:45 ` [Ksummit-discuss] " James Bottomley
2022-06-22 9:59 ` Linus Walleij
2022-06-22 10:57 ` Laurent Pinchart
2022-06-22 12:01 ` Linus Walleij
2022-06-22 12:09 ` Laurent Pinchart
2022-06-22 23:13 ` NeilBrown [this message]
2022-06-23 11:37 ` James Bottomley
2022-06-25 12:03 ` [Ksummit-discuss] " Mauro Carvalho Chehab
2022-06-25 11:45 ` [Ksummit-discuss] [TECH TOPIC] Rust Mauro Carvalho Chehab
2022-06-25 14:15 ` James Bottomley
2022-06-25 16:18 ` Mauro Carvalho Chehab
2022-06-25 22:29 ` Linus Walleij
2022-06-26 2:52 ` Theodore Ts'o
2022-06-26 3:18 ` Al Viro
2022-06-19 13:49 ` Laurent Pinchart
2022-06-19 13:49 ` [Ksummit-discuss] " Laurent Pinchart
2022-06-19 19:08 ` Geert Uytterhoeven
2022-06-19 19:08 ` [Ksummit-discuss] " Geert Uytterhoeven
2022-06-19 20:57 ` Matthew Wilcox
2022-06-20 13:53 ` Linus Walleij
2022-06-20 14:08 ` James Bottomley
2022-06-21 15:11 ` Dan Carpenter
2022-06-23 10:58 ` [TECH TOPIC] Why is devm_kzalloc() harmful and what can we do about it Laurent Pinchart
2022-06-23 11:24 ` Dan Carpenter
2022-06-23 11:31 ` Laurent Pinchart
2022-06-21 9:49 ` [TECH TOPIC] Rust David Woodhouse
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=165593960233.4786.4776751165554098218@noble.neil.brown.name \
--to=nfbrown@suse.de \
--cc=James.Bottomley@HansenPartnership.com \
--cc=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=ksummit@lists.linux.dev \
--cc=laurent.pinchart@ideasonboard.com \
--cc=miguel.ojeda.sandonis@gmail.com \
/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