It seems as if very few really understand the point of the original text... Once you abandon the 80 column standard in a software project the source code has become a competition arena for all developers to show off how big monitors they have or how sharp eyed they are to stand with smallest possible font. The winner of this competition will be a young person with sharp eyes, cash enough to buy biggest possible monitor and the ability to use the diagonal of the monitor. The winner will force all the losers to use horizontal scroll bars to read lines with function calls with many long parameters and an even longer explaining comment on the same line.

The article ends with a misleading conclusion from Georg Steinhauser: "Once released, a radioactive substance can never be unreleased again — and nature doesn’t forget.". Cesium-137 has a half-life of about 30 years. This means that if you think that it today is too much cesium-137 from nuclear weapons testings about 60 years ago you should be aware that 60 years ago the amount of cesium-137 was about 4 times as much from those sources. Wait another 60 years and there will only be 1/4 left of cesium-137 from those sources.

Then you will end up with all 3 licenses which will boil down to the terms of 2 licenses. All licenses will require you to ship the license information with your application. The BSD-like license will require you to mention that the copyright holders of that source have that copyright. The GPL license will require you, at least upon request, will provide the entire source of your application to the end user that so requests and that end user has the right to modify any part of the source and run and distribute his modified version with the same licenses. All the terms of the LGPL-like license will be covered by the GPL-like license.

In short there are 3 kinds of open source licenses:

1) BSD-like licenses which allow you to create derivative works like executable programs, libraries or trained AI models as long as you with the derivative work include a text which tells about the license and who the copyright holders are of the original code.

2) LGPL-like licenses which allow you to create derivative works as long as the end user is informed of the license and at least on request gets access to the source code of the part with LGPL license and is given the ability to modify that part of the source and rebuild the derivate work which might be a program, a library or a trained AI model.

3) GPL-like licenses which allow you to create derivative works as long as the end user is informed about the license so she/he knows his/her right to ask for the complete source of the derivative work and gets the ability to modify the parts of the sources the users wants to modify and then rebuild the derivative work with his moidfied sources.

Then there is also AGPL-like licenses which points out that the end user might not be the administrator of a network server like a web server, but the remote users connecting to that server.

I would say that any licenses on source used to train an AI model applies both to that trained model and any source that it produces. If you don't like what some of those licenses say you should not use such code as your training data.

I would say that GPUs are not the reason that we don't need faster CPUs. It is rather the lack of faster CPUs that has made gamers and heavy computations like machine learning move to GPUs. It is also the lack of increase in clock-speed that has made CPU makers put more cores into their CPUs. 30 years ago, you would if you upgraded your computer every third year get a computer that was twice as fast as your old computer. That is no longer true, and now people no longer upgrade their computers every third year. June 1995 Intel released a 200 MHz pentium CPU. Less than 3 years later, April 1998, Intel released a 400 MHz Pentium II. August 2015 Core i7 with base frequency 4 GHz was released and now, almost 8 years later, that is still about the speed we can get.

I would say that Slackware does have support for dependency check for packages. It is true that the Slackware packages themselves does not support dependency check (for good and bad). So your best bet is to make a full install of Slackware. However, once you have this rather small full install of Slackware you can continue to install packages from slackbuilds.org. Slackbuild.org does track dependencies between packages and you can use tools like slpkg to easily install a package with all its dependencies. Example: slpkg -s sbo vlc To install the VLC media player with its 50+ dependencies.