|
|
Subscribe / Log in / New account

Looking back at 2023

By Jonathan Corbet
December 20, 2023
Yet another year has come to an end. Much to our dismay, 2023 did not, in fact, happen exactly as we predicted back in January. So it seems that, once again, we will have to go through the process of looking at the predictions that we made and mocking each in turn, before getting into what was missed altogether. A lot happened in 2023, not all of which was predictable.

Our first prediction was that the community would see a spike in AI-generated material submitted as contributions. If that has indeed happened, the quality has been high enough that those submissions have not been identified as coming from machine-learning applications. That is perhaps surprising, given the common reports that large numbers of developers are working with machine-learning assistance at this point. Be that as it may, it seems fair to say that the flood we predicted has not, as yet, arrived.

The same cannot be said for submissions to LWN. We have, for many years, gotten offers of "articles" to publish, many of which come with promise of payment for publication (an offer we have never accepted in all of LWN's history, incidentally). Often it has been clear that not much human attention has gone into the creation of these offers. Over the last year, though, it seems that some of these people have figured out how to ask a language model to generate their emails, with the result that their solicitations are simultaneously more formulaic and less intelligible than ever. The flood has arrived, but it is going for the (seemingly) easier money first.

The prediction that new kernel functionality would be written in Rust and proposed for inclusion was reasonably obvious a year ago. Much of what has actually been proposed to go upstream is a reimplementation of existing functionality (the Rust Binder implementation, for example), which doesn't quite satisfy the prediction. Other work, though, such as PuzzleFS and the Apple M1 graphics driver, definitely does. As of this writing, a network PHY driver written in Rust, along with some supporting abstractions, is staged to be merged into 6.8, presumably shortly after the new year. As was predicted, no user-visible functionality written in Rust was actually merged in 2023.

The prediction of a "make-or-break year for distributed social networking" is somewhat hard to verify. Certainly, the distributed network often called (not entirely accurately) "Mastodon", has grown significantly over the last year and is the focus of a great deal of conversation. This network, it seems, will be around for the long term. Meanwhile, though, sites like the one formerly known as Twitter continue to exist, despite what appears to be a determined effort to kill it. How this story will play out overall is yet to be seen, but there is hope that centralized services may be giving way to federated alternatives based on free software.

Was it "the year of the immutable distribution" as predicted? The effort being put into the development of such distributions appears to have only increased over the last year (see our recent review of Project Bluefin for an example) , but it is fair to say that this approach to distributions has not yet taken over in general. Distributions built on SUSE's "ALP" platform are not yet shipping (though openSUSE MicroOS Desktop did make its debut). Instead, one could be forgiven for thinking that the commercial distributors out there have given up on innovation and decided to just make RHEL clones instead.

What was missed

While erroneous predictions are easy to point out, predictions that were not made at all can be a bit harder to identify. Nonetheless, one can certainly pick out some events that, in retrospect, we should have perhaps seen coming.

Red Hat's escalation of the enterprise-distribution wars is arguably one of those. The company has never made a secret of its intent to protect the Red Hat Enterprise Linux cash cow to the extent that it can, perhaps bending (though generally not breaking) the free-software licensing rules in the process. The company's decision in 2023 to stop making its patches generally available — and to reserve the right to cut off customers who distribute those patches — fits the pattern well.

Perhaps Red Hat's decision to drop LibreOffice was a bit more of a legitimate surprise; there was once a time when the availability of that sort of "productivity" software was deemed crucial for the future of Linux. In 2023, to the extent that office suites are still considered important, some distributors seem to feel that they can let others deal with packaging and shipping them — or just expect people to use centralized, online services instead.

LWN did not predict the end of six-year long-term-support kernels; once somebody starts providing a service, it is easy to imagine that this service will continue indefinitely. But if it seems that there are few users of that service, and even fewer who are willing to help keep that service going, it will eventually go away. The kernels that receive commercial long-term support are generally far removed from the mainline, so they benefit relatively little from many years of mainline support. Those of us using something close to mainline kernels are, as a general rule, better served by running relatively recent releases. In that world, there is not much call for six years of support for a mainline kernel.

After years of seeing BPF pushed into all corners of the kernel, it was only a matter of time until an attempt was made to put it into the CPU scheduler. That doesn't make it any easier to predict where BPF will end up next year, though.

While it would have been difficult to predict HashiCorp's license change specifically, it would not have been that hard to guess that some company, somewhere, would decide that this whole "open-source software" thing wasn't actually for them. As long as there are companies working with our software, there will be companies trying to figure out how to get the benefits of open source without actually having to free their code. We can't predict who will try this next year, but some company almost certainly will.

Another event that might have been foreseen was disruptions in the community resulting from the ongoing Russian invasion of Ukraine. Indeed, the surprising thing may be that the impact from such a major war has, thus far, been so small. Our community is good at staying above the political and economic fray, but there are limits. Depending on how events proceed in the more troubled parts of our world, we may see more turbulence in the coming year.

Surprises can come closer to home as well — and can also be more welcome. We first wrote about our desire to escape from proprietary accounting software in 2007. After 15 years (at the beginning of this year), it would have been hard to predict that this goal would be achieved in 2023, but it did indeed happen. We are now approaching the end of our first full year using GnuCash, and it continues to go well. We can easily predict that we will not be going back to proprietary solutions anytime soon.

In summary

While the free-software community tends to hold up well in difficult times, it is not entirely immune to those difficulties. In this case, the fierce competition to hire some types of developer has eased up to an extent, making lucrative positions harder to find, and some jobs have been lost. Opportunities remain, though; free software is sufficiently important to businesses that they can only hold off on hiring for so long.

Our community was hurt this year by the loss of Bram Moolenaar, Abraham Raji, and Satoru Ueda, among others; they will all be sorely missed.

Free software remains strong, in that much of the technology industry (and beyond) relies heavily upon it; as a result, there is more software being written and released than ever. It is still true, though, that many of the problems we have seen over the years — failure to live up to licensing requirements, unwillingness to support developers and maintainers, communities that do not feel welcoming to all, etc. — remain with us, and are not necessarily getting better. It is not surprising that people get discouraged and drop out, or never settle into our community in the first place.

If one looks, though, the spirit of what we set out to do remains alive and well. The growth of the ActivityPub network (Mastodon and such) in 2023 is a good example; a decentralized network based on free software has taken up much of the role that was once filled by a large, centralized, proprietary service. Applications like Home Assistant are restoring control over the systems installed in homes to the people who live in those homes. Open-source large-language models are refusing to cede that space to large, proprietary players. And the community as a whole continues to produce more software, some of which is high-quality indeed.

By now the world has seen enough examples of malign technologies, like printers that refuse to print without a subscription payment, "smart" devices that leak personal data far and wide, cars that brick themselves on command, and doorbells that spy on the neighborhood, to understand that control over the software in one's life is important. Our community has spent decades working toward a world where that kind of control is possible and, to a great extent, we have succeeded. Maybe, in 2023, we have also succeeded, in some little way, in showing the world why this control is important. If that trend can accelerate in 2024, then this year may yet look like an important inflection point with long-reaching consequences.

Over the course of this year, LWN published 292 feature articles (41 of which were from guest authors) and reported from 13 conferences. We have done our best to follow the ups and downs of our community and, in return, the community has supported us. As we head into the end-of-year holidays, we wish the best to all of our readers; thanks for sticking with us this year, and we look forward to seeing you in the next.


to post comments

Looking back at 2023

Posted Dec 20, 2023 20:26 UTC (Wed) by burki99 (subscriber, #17149) [Link]

Thanks for another year of truly great reporting sprinkled with sparks of wonderful humor. Looking forward for many more years to come

Looking back at 2023

Posted Dec 20, 2023 23:51 UTC (Wed) by q_q_p_p (guest, #131113) [Link] (8 responses)

Another example of malign technology was trains software that makes trains not start when some conditions were met ("dieselgate, but for trains - heavyweight hardware hacking") ;)

Also one thing wasn't predicted, but could have been (given how many other corporations do this too) - IBM's Red Hat implements racist policies, which was exposed this year.

Looking back at 2023

Posted Dec 20, 2023 23:58 UTC (Wed) by willy (subscriber, #9762) [Link] (5 responses)

It seems you mean "Red Hat attempts to introduce diversity in their hiring process", because the only sites I can find talking about this are all about Teh Evil Discrimination Against White People, which, um, have you looked at photos from, eg the Kernel Summit?

Looking back at 2023

Posted Dec 21, 2023 0:02 UTC (Thu) by q_q_p_p (guest, #131113) [Link] (4 responses)

Looking back at 2023

Posted Dec 21, 2023 0:09 UTC (Thu) by willy (subscriber, #9762) [Link] (3 responses)

Looking back at 2023

Posted Dec 21, 2023 0:11 UTC (Thu) by q_q_p_p (guest, #131113) [Link] (2 responses)

"Disgraced". Well, it's not James that says racist things in that video.

Looking back at 2023

Posted Dec 21, 2023 0:42 UTC (Thu) by dskoll (subscriber, #1630) [Link] (1 responses)

Given his history of deceptive video editing, I don't think we should give that video any weight whatsoever.

More on his history at [1], [2], [3], [4], and [5].

Let's stop here

Posted Dec 21, 2023 0:46 UTC (Thu) by jake (editor, #205) [Link]

I strongly doubt this thread is going anywhere very useful for anyone.

Let's stop it here, folks, thanks ...

jake

Looking back at 2023

Posted Dec 21, 2023 1:20 UTC (Thu) by brunowolff (guest, #71160) [Link]

There is a CCC talk about this at this year's congress (next week).
https://fahrplan.events.ccc.de/congress/2023/fahrplan/eve...

Looking back at 2023

Posted Jan 1, 2024 14:12 UTC (Mon) by kaesaecracker (subscriber, #126447) [Link]

You can see a great talk by the hackers who unblocked the trains: https://media.ccc.de/v/37c3-12142-breaking_drm_in_polish_...

It will probably be available to watch on YouTube as well soon. I had the privilege to see it live and would definitely recommend watching it.

Looking back at 2023

Posted Dec 21, 2023 3:30 UTC (Thu) by PengZheng (subscriber, #108006) [Link]

> Our first prediction was that the community would see a spike in AI-generated material submitted as contributions. If that has indeed happened, the quality has been high enough that those submissions have not been identified as coming from machine-learning applications. That is perhaps surprising, given the common reports that large numbers of developers are working with machine-learning assistance at this point. Be that as it may, it seems fair to say that the flood we predicted has not, as yet, arrived.

I use GitHub Copilot for unit testing heavily, and suspect unit testing is still the main usage of such tools.
Note that it started October 2021, is it safe to say that AI-coding assistant does not make great breakthrough in the past year?

New physics? The LLM uncertainty principle

Posted Dec 21, 2023 5:26 UTC (Thu) by SnoopJ (guest, #162807) [Link] (2 responses)

It's kinda amusing that this article speculates that language models might be producing patches of exceptional quality *and also* producing formulaic drivel that is nonsense even by the standards of email spam. Perhaps there is new physics at work in the tech community's general uncertainty over the capabilities of these models. 😅

For whatever it's worth: I have personally seen a decent amount of generated code this year, and almost all of it has been supremely underwhelming.

---

Thanks for another year of great reporting, it was (mostly) fun to read over these predictions. In a world increasingly filled with crapware and junk info, organizations like LWN are a breath of fresh air, and I look forward to seeing what y'all see in the tea leaves for the year ahead.

New physics? The LLM uncertainty principle

Posted Dec 22, 2023 5:58 UTC (Fri) by NYKevin (subscriber, #129325) [Link] (1 responses)

It's my experience that non-programmers (or people who seldom program) tend to be much more impressed by LLM-generated code than programmers. Perhaps they overrate the difficulty of programming. Perhaps programmers are too quick to discount our own skills. Or maybe it's just that they're having their first "I told the computer what to do and it *worked*" moment (you know, the one that all programmers have the first time they write a non-trivial program).

New physics? The LLM uncertainty principle

Posted Dec 23, 2023 19:12 UTC (Sat) by shemminger (subscriber, #5739) [Link]

Agree. My experience is that LLM only give the template for how to write some code. Kind of like the starting point examples given as part of college assignments. And when code is produced often has simple to find obvious bugs.

Looking back at 2023

Posted Dec 21, 2023 9:51 UTC (Thu) by GCMorGoHome (subscriber, #151226) [Link]

A big thank you to LWN for keeping up the high quality content! I'm truly grateful for your work :)
Looking forward to another year of interesting linux news and insights.

Looking back at 2023

Posted Dec 21, 2023 13:48 UTC (Thu) by smitty_one_each (subscriber, #28989) [Link]

Thanks for remaining the best technical news outlet on the internet.

Best wishes in the new year.

Looking back at 2023

Posted Dec 21, 2023 14:01 UTC (Thu) by daenzer (subscriber, #7050) [Link] (10 responses)

"Red Hat's [...] decision in 2023 to stop making its patches generally available" seems inaccurate, seeing as full source code and Git history is publicly available at https://gitlab.com/redhat/centos-stream/src (ahead of the resulting RHEL release).

Disclaimer: I work for Red Hat's GPU infrastructure team. The above is my personal opinion.

Looking back at 2023

Posted Dec 21, 2023 17:30 UTC (Thu) by rahulsundaram (subscriber, #21946) [Link] (9 responses)

> "Red Hat's [...] decision in 2023 to stop making its patches generally available" seems inaccurate, seeing as full source code and Git history is publicly available at https://gitlab.com/redhat/centos-stream/src (ahead of the resulting RHEL release).

> Disclaimer: I work for Red Hat's GPU infrastructure team. The above is my personal opinion.

There seems to be conflicting opinions here including from other Red Hat employees who have pointed that atleast some security patches are not being made available publicly as separate patches. If that is not the case, can you provide a precise technical summary of what exactly was the scope of the change Red Hat announced?

Looking back at 2023

Posted Dec 21, 2023 17:53 UTC (Thu) by daenzer (subscriber, #7050) [Link] (8 responses)

> [...] atleast some security patches are not being made available publicly as separate patches.

Fixes for embargoed security issues are indeed the only exception, they obviously cannot be published before the embargo is lifted.

> can you provide a precise technical summary of what exactly was the scope of the change Red Hat announced?

It was about git.centos.org. Red Hat employees used to remove any Red-Hat-trademarked content from every RHEL SRPM, and upload the result there. That is no longer happening. Those SRPMs were only really needed for creating a "1:1" (modulo trademarked content) clone of RHEL without putting in the corresponding work though. Now making a clone requires putting in corresponding work. Everybody else can get the full source code and Git history from https://gitlab.com/redhat/centos-stream/src .

For more background, see https://www.redhat.com/en/blog/red-hats-commitment-open-s... .

Looking back at 2023

Posted Dec 22, 2023 1:41 UTC (Fri) by rahulsundaram (subscriber, #21946) [Link] (7 responses)

> Fixes for embargoed security issues are indeed the only exception, they obviously cannot be published before the embargo is lifted.

Sure but my understanding is that after the embargo gets lifted, said patches just get merged in a branch in CentOS stream and not gets split specifically as a security patch anymore.

> Now making a clone requires putting in corresponding work

I am not sure any of them do that. It seems what they end up actually doing is pulling SRPMS from UBI containers or cloud instances and such. So all of this doesn't seem to have accomplished the intended effect. In any case, is the corresponding work figuring out which patches are needed to reproduce a stable build from the dev branch?

Looking back at 2023

Posted Dec 22, 2023 8:26 UTC (Fri) by daenzer (subscriber, #7050) [Link]

> Sure but my understanding is that after the embargo gets lifted, said patches just get merged in a branch in CentOS stream and not gets split specifically as a security patch anymore.

I'm not intimately familiar with how that's handled offhand, sounds plausible though. Even so, they're "generally available" though.

Looking back at 2023

Posted Dec 22, 2023 14:54 UTC (Fri) by pbonzini (subscriber, #60935) [Link]

It depends. It's true that in some cases CentOS Stream (and RHEL x.(y+1) as well when it's released) will get the next upstream patch release, while RHEL x.y will get a backport. In other cases a backport is applied to both.

Looking back at 2023

Posted Dec 23, 2023 3:55 UTC (Sat) by NYKevin (subscriber, #129325) [Link] (4 responses)

> Sure but my understanding is that after the embargo gets lifted, said patches just get merged in a branch in CentOS stream and not gets split specifically as a security patch anymore.

Let's be clear about what the GPL actually says. When you distribute modified versions of a GPL'd work, you must:

* Provide attribution.
* Provide source code (the "preferred form of the work for making modifications to it").
* Include "prominent notices" stating that the work is under the GPL.
* Include "prominent notices stating that you modified it."
* License the modified version under the GPL.
* Preserve any copyright and other legal notices (e.g. lack of warranty) in the work's UI.
* Also there are extra rules (under GPLv3) if it's sold as an integral part of consumer hardware, but that doesn't apply to RHEL.

There is absolutely nothing, in either version of the GPL, which says you have to separate out patches in a convenient format, so long as the complete corresponding source code is available. For that matter, you're not even required to distribute the source code publicly at all, as long as it is provided to the recipient.

There are lingering questions about whether Red Hat can validly refuse to do business with clients who exercise the full extent of their GPL rights. But that is a separate issue. For GPL purposes, Red Hat is under absolutely no obligation to provide individual patches, even to their clients. The only (relevant) requirement is that the code they give to their clients must correspond to the binaries they give to their clients. They can satisfy that requirement with an opaque tarball, sans Git history.

Looking back at 2023

Posted Dec 23, 2023 12:29 UTC (Sat) by rahulsundaram (subscriber, #21946) [Link]

> Let's be clear about what the GPL actually says.

I am not sure what gave you the impression that any of my questions had anything to do with the licensing obligations. My questions were entirely about the precise nature of the technical changes within CentOS stream

Looking back at 2023

Posted Dec 25, 2023 7:47 UTC (Mon) by Sesse (subscriber, #53779) [Link] (1 responses)

You _could_ argue that the patch series is the preferred form of making modifications to the software, given that Red Hat clearly keeps that internally and prefers it themselves. Whether that argument would actually convince a court is a completely different matter, of course.

Looking back at 2023

Posted Dec 25, 2023 10:50 UTC (Mon) by daenzer (subscriber, #7050) [Link]

> [...] given that Red Hat clearly keeps that internally and prefers it themselves.

Did you read the posts higher up in this thread?

Red Hat employees are using https://gitlab.com/redhat/centos-stream/src for developing RHEL, which is publicly accessible. There is nothing else which is kept internally.

Looking back at 2023

Posted Jan 5, 2024 21:40 UTC (Fri) by Wol (subscriber, #4433) [Link]

> There are lingering questions about whether Red Hat can validly refuse to do business with clients who exercise the full extent of their GPL rights.

It is (for the most part) completely accepted that the law does NOT interfere with relationships between adults (legal persons, or legal fictional persons). If Red Hat does not want to do business with you, that is down to Red Hat, and absolutely nothing to do with the Government or the Courts.

If Red Hat breaks their contract with you (and Red Hat has explicitly reserved the right to walk away from the contract!!!) then THAT is when the Courts can get involved.

Cheers,
Wol

Looking back at 2023

Posted Dec 22, 2023 15:33 UTC (Fri) by salimma (subscriber, #34460) [Link] (2 responses)

Meta starting to federate Threads with the fediverse probably is a good sign that the distributed social networking concept should be taken seriously, whether people think that's a good or bad thing.

Looking back at 2023

Posted Dec 22, 2023 18:45 UTC (Fri) by dskoll (subscriber, #1630) [Link] (1 responses)

I don't know if I like this. Meta is simply going to use the fediverse as another source of data to gather. I would not be surprised if a significant number of instance operators decline to federate with Meta.

Looking back at 2023

Posted Jan 5, 2024 21:09 UTC (Fri) by salimma (subscriber, #34460) [Link]

Yeah, not wearing my employee hat, I'm ambivalent about what it means. Still, worst case that means the Fediverse is worth taking seriously enough to EEE

Looking back at 2023

Posted Dec 22, 2023 22:19 UTC (Fri) by gerdesj (subscriber, #5446) [Link]

Thank you to the elves at LWN for another fine year of reporting and the epitome of discussion fora.

Cheers
Jon

Looking back at 2023

Posted Dec 24, 2023 22:28 UTC (Sun) by pj (subscriber, #4506) [Link]

>Over the course of this year, LWN published 292 feature articles (41 of which were from guest authors) and reported from 13 conferences.

...and now I want graphs :) How about adding an 'LWN by the numbers' segment to this (yearly) article? Count articles, authors, conferences, comments, commentors... you could even to breakdowns by topic 'kernel', 'languages', 'reviews', etc.

Just an idea, thougI guess some of that may phase over into 'business intelligence' you may not want to share. Anyway, thanks for another amazing year!

Looking back at 2023

Posted Dec 26, 2023 17:12 UTC (Tue) by ecm (subscriber, #129897) [Link] (3 responses)

> The same cannot be said for submissions to LWN. We have, for many years, gotten offers of "articles" to publish, many of which come with promise of payment for publication (an offer we have never accepted in all of LWN's history, incidentally).

I'm unsure what direction the "payment" is supposed to be read as here. We're guessing here the offer was to pay LWN in order for you to publish the articles? Is that correct?

Looking back at 2023

Posted Dec 26, 2023 21:53 UTC (Tue) by atnot (subscriber, #124910) [Link] (2 responses)

It would have to be, as the other direction happens routinely: https://lwn.net/op/AuthorGuide.lwn

Looking back at 2023

Posted Dec 28, 2023 5:53 UTC (Thu) by NYKevin (subscriber, #129325) [Link] (1 responses)

This is also implied by the broader context of "LWN is a news service."

Paying freelancers for submissions is entirely normal in this industry. Paying to get your own article published is not a thing (among reputable news agencies, anyway). It is the journalism equivalent of receiving email from the deposed prince of Nigeria.

Well, maybe it's not quite that bad. Probably these are just overzealous advertisers/spammers who think they can bribe LWN to write an article about their shiny new [thing that we sell]. The more conspiratorial explanations (e.g. it's a bunch of scammers trying to create a fake online persona of a tech journalist for some nefarious purpose) just seem like they wouldn't generate a notable volume of inquiries in comparison to run-of-the-mill press release spam.

Looking back at 2023

Posted Dec 28, 2023 22:36 UTC (Thu) by tialaramex (subscriber, #21167) [Link]

The "legitimate" way you get your preferred material into the news is you make it incredibly easy for freelancers to write your story. When I worked for a start-up we had a PR firm to do this. Freelancers get paid the same whether they take a PR email with ready-to-use quotes and a suggested story outline and make that into a publishable story in an hour, or they spend all day actually investigating something and doing journalism, so no surprise that even if they like to do the latter when they can, they often do the former.


Copyright © 2023, Eklektix, Inc.
This article may be redistributed under the terms of the Creative Commons CC BY-SA 4.0 license
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds