From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [Package Request] SeaMonkey
Date: Mon, 06 Jan 2020 18:48:07 +0100 [thread overview]
Message-ID: <20200106174807.F8-HuEYACa0sHwY8xn8etj4QNawKQGbAcnleMzJ3N1o@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-17772@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 746 bytes --]
New comment by silvernode on void-packages repository
https://github.com/void-linux/void-packages/issues/17772#issuecomment-571238075
Comment:
Not to take this discussion off track too much but, in my opinion Mozilla has appeared to start caring a little more in the last year. I think the way they are treating Firefox and the web is honorable when you consider what they could be doing to counteract competitors. As for the code, it's my understanding that they are slowly switching the C++ code base with Rust which is at least a good step in the right direction I think. Maybe my view is completely naive but I like to think Mozilla is beginning to clean up their act and proving they want to continue to serve the web as an open standard.
next prev parent reply other threads:[~2020-01-06 17:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-25 17:36 [ISSUE] Seamonkey voidlinux-github
2019-12-28 1:35 ` [Package Request] SeaMonkey voidlinux-github
2019-12-29 11:29 ` voidlinux-github
2020-01-06 17:48 ` voidlinux-github [this message]
2020-01-29 14:28 ` voidlinux-github
2020-01-29 14:29 ` voidlinux-github
2020-01-29 16:46 ` voidlinux-github
2020-02-01 17:20 ` voidlinux-github
2020-02-01 20:50 ` voidlinux-github
2020-02-29 22:23 ` userabc123xyz
2020-05-06 22:56 ` userabc123xyz
2020-05-06 23:00 ` userabc123xyz
2020-05-06 23:00 ` userabc123xyz
2020-05-06 23:00 ` userabc123xyz
2020-05-06 23:03 ` userabc123xyz
2020-07-19 16:57 ` xianwenchen
2021-03-03 6:01 ` rogerxxxx
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=20200106174807.F8-HuEYACa0sHwY8xn8etj4QNawKQGbAcnleMzJ3N1o@z \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).