From: Tomasz Rola <email@example.com>
To: Computer Old Farts Forum <firstname.lastname@example.org>
Subject: [COFF] Re: Systemd Creator Lands At Microsoft
Date: Sat, 9 Jul 2022 02:29:07 +0200 [thread overview]
Message-ID: <20220709002907.GB28363@tau1.ceti.pl> (raw)
On Fri, Jul 08, 2022 at 12:26:23PM +0200, Michael Cardell Widerkrantz wrote:
> Tomasz Rola <email@example.com>, 2022-07-08 09:40 (+0200):
> > Well, what the title says. Some folks here wandered what the future
> > may be. I suppose destroying Linux, or making it irrelevant.
> Microsoft of today is really not the Microsoft of the 1990s. There are a
> lot of people at MSFT working on Linux in different forms.
If you know this first hand, then great. I admit, after 1995 I have
only used anything MS about few times a year or so. The experience was
always a bit miserable - my index finger got stiff from constant
clicking, my mouse-arm got tired from precision moves etc. You may
thing I am exagerrating, in such case try moving your finger up and
down for an hour - I was just trying to port my Linux workflow under
Windows, and I am sure if I really had to work under Windows, I would
have invented some shortcuts to save my finger. But I digress.
You wrote, MS is not the same as in 1990. I think, sure, thirty years
later, they would not be the same. But you seem to imply that "so
old-thinking guys are out of the doors already". This might
be. However, I am more likely to believe that "old thinking guys" made
sure to hire new guys who would be able to get the torch from their
cold hands and carry on. On the surface, a business is all new ("hey
we hire new people every day"). Under the surface, a business is
almost the same ("why change something that works so well").
> > What would happened, if systemd development went in two ways, one
> > gnu-licenced and the other commercial?
> I suppose more distributions would look at the alternatives like OpenRC
> or S6.
Maybe. I am still trying to evaluate various alternatives to Debian
and I am not so sure. Debian was so bloody good (for me) that finding
alternative is hard (especially that I expect to do something with
computer at the same time).
** A C programmer asked whether computer had Buddha's nature. **
** As the answer, master did "rm -rif" on the programmer's home **
** directory. And then the C programmer became enlightened... **
** Tomasz Rola mailto:firstname.lastname@example.org **
next prev parent reply other threads:[~2022-07-09 0:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 7:40 [COFF] " Tomasz Rola
2022-07-08 10:26 ` [COFF] " Michael Cardell Widerkrantz
2022-07-09 0:29 ` Tomasz Rola [this message]
2022-07-09 1:52 ` Angel M Alganza
2022-07-09 8:35 ` Tomasz Rola
2022-07-09 8:59 ` Angel M Alganza
2022-07-10 21:39 ` Chris Hanson
2022-07-11 14:11 ` Steffen Nurpmeso
2022-07-11 21:04 ` Michael Cardell Widerkrantz
2022-07-11 23:01 ` Dave Horsfall
2022-07-12 7:58 ` [COFF] Re: Alpine, was: " Michael Kjörling
2022-07-12 15:34 ` Adam Thornton
2022-07-12 22:02 ` Steffen Nurpmeso
2022-07-12 23:34 ` Dave Horsfall
2022-07-13 7:36 ` [COFF] Re: Alpine Michael Kjörling
2022-07-12 15:56 ` [COFF] Re: Systemd Creator Lands At Microsoft Michael Cardell Widerkrantz
2022-07-12 19:48 ` Lars Brinkhoff
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).