'An anonymous reader shares a report:
A somewhat obscure guideline for developers of U.S. government
websites may be about to accelerate the long, sad decline of Mozilla's
Firefox browser. There already are plenty of large entities, both
public and private, whose websites lack proper support for Firefox;
and that will get only worse in the near future, because the 'fox's
auburn paws are perilously close to the lip of the proverbial slippery
slope. The U.S. Web Design System (USWDS) provides a comprehensive set
of standards which guide those who build the U.S. government's many
websites. Its documentation for developers borrows a "2% rule" from
its British counterpart: "... we officially support any browser above
2% usage as observed by analytics.usa.gov." (Firefox's market share
was 2.2%, per the traffic for the previous ninety days.)
[...] "So what?" you may wonder. "That's just for web developers in
the U.S. government. It doesn't affect any other web devs." Actually,
it very well could. Here's how I envision the dominoes falling:
1. Once Firefox slips below the 2% threshold in the government's
visitor analytics, USWDS tells government web devs they don't have to
support Firefox anymore.
2. When that word gets out, it spreads quickly to not only the
front-end dev community but also the corporate IT departments for whom
some web devs work. Many corporations do a lot of business with the
government and, thus, whatever the government does from an IT
standpoint is going to influence what corporations do.
3. Corporations see this change as an opportunity to lower dev costs
and delivery times, in that it provides an excuse to remove some
testing (and, in rare cases, specific coding) from their development
workflow.'
-- source: https://news.slashdot.org/story/23/12/05/0745251
Cheers, Peter
--
Peter Reutemann
Dept. of Computer Science
University of Waikato, Hamilton, NZ
Mobile +64 22 190 2375
https://www.cs.waikato.ac.nz/~fracpete/http://www.data-mining.co.nz/
'A pull request has been merged to fix a data corruption issue in
OpenZFS (the open-source implementation of the ZFS file system and
volume manager). "OpenZFS 2.2.2 and 2.1.14 released with fix in
place," reports a Thursday comment on GitHub.
Earlier this week, jd (Slashdot reader #1,658) wrote: All versions of
OpenZFS 2.2 suffer from a defect that can corrupt the data. Attempts
to mitigate the bug have reduced the likelihood of it occurring, but
so far nobody has been able to pinpoint what is going wrong or why.
Phoronix reported on Monday: Over the US holiday weekend it became
more clear that this OpenZFS data corruption bug isn't isolated to
just the v2.2 release — older versions are also susceptible — and that
v2.2.1 is still prone to possible data corruption. The good news at
least is that data corruption in real-world scenarios is believed to
be limited but with some scripting help the corruption can be
reproduced. It's also now believed that the OpenZFS 2.2 block cloning
feature just makes encountering the problem more likely. '
-- source: https://news.slashdot.org/story/23/12/03/0134224
Cheers, Peter
--
Peter Reutemann
Dept. of Computer Science
University of Waikato, Hamilton, NZ
Mobile +64 22 190 2375
https://www.cs.waikato.ac.nz/~fracpete/http://www.data-mining.co.nz/
'"Red Hat is going to do away with the X.Org server and support
Wayland and XWayland for apps that currently (or only) run on X11,"
writes Slashdot reader motang. Red Hat's Carlos Soriano Sanchez
confirmed on the Red Hat blog:
"The result of this evaluation is that, while there are still some
gaps and applications that need some level of adaptation, we believe
the Wayland infrastructure and ecosystem are in good shape, and that
we're on a good path for the identified blockers to be resolved by the
time RHEL 10 is out, planned to be released on the first half of 2025.
With this, we've decided to remove Xorg server and other X servers
(except Xwayland) from RHEL 10 and the following releases. Xwayland
should be able to handle most X11 clients that won't immediately be
ported to Wayland, and if needed, our customers will be able to stay
on RHEL 9 for its full life cycle while resolving the specifics needed
for transitioning to a Wayland ecosystem. It's important to note that
"Xorg Server" and "X11" are not synonymous, X11 is a protocol that
will continue to be supported through Xwayland, while the Xorg Server
is one of the implementations of the X11 protocol.
[...]
This decision will allow us to focus our efforts starting from RHEL 10
solely on a modern stack and ecosystem. This means we will be able to
tackle problems such as HDR, increased security, setups with mixed low
and high density displays or very high density displays, better
GPU/Display hot-plugging, better gestures and scrolling, and so on. We
are confident that Wayland will provide a solid platform and we're
excited to work with the community and all of our partners and
customers on building the future for Linux." '
-- source: https://linux.slashdot.org/story/23/11/29/0559207
Cheers, Peter
--
Peter Reutemann
Dept. of Computer Science
University of Waikato, Hamilton, NZ
Mobile +64 22 190 2375
https://www.cs.waikato.ac.nz/~fracpete/http://www.data-mining.co.nz/
