Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)N

nous

@ nous @programming.dev

Posts
0
Comments
359
Joined
2 yr. ago

  • Systemd timers or classic cron?

    Jump

  • Email support was the bain of my existence. I forgot how many misconfigured system I came across decades ago that would fill up their filesystem with logs from crons in the root mail dir. Such a stupid default setting. We have vastly better methods for monitoring systems these days then firing off an email when a cron runs.

  • Systemd timers or classic cron?

    Jump

  • You can also easily see when the job last ran, if it was successful and when it will next run. As well as just trigger the service if you want it to run now.

  • Is the FOSS world in danger of a corporate takeover, thanks to pushover licenses?

    Jump

  • I was not trying to brush away the differences for GPL 2 vs 3. My point was just that I don't think a more permissive license on Coreutils would have caused every company to want to steal the code, get everyone using it and force out the GPLed version. But a more restrictive license (say one that infects other binaries on the system) would have meant fewer companies using it and thus fewer distros and everyone else using it.

    But for other projects the balance is different and a more permissive license would cause issues. There are some projects that even the GPLv2 or even v3 is too permissive for.

  • Is the FOSS world in danger of a corporate takeover, thanks to pushover licenses?

    Jump

  • sudo is not GPL3. It is not even GPL2. It is an old license that is just as permissive as the MIT license. It has never had any big problems with that being the case. I don't think that coreutils being GPL has really done anything to force companies to contribute back to it. It is mostly fixed in its function and does not really have much room for companies taking and modifying it to a point where others will favor the closed version over the open on. And what it provides is fairly trivial functions overall that if someone did want to take part of it then it is not terribly hard to rewrite it from scratch.

    GNU Coreutils is not the only implementation of those POSIX features - just the most popular one. FreeBSD has its own, there is busybox, the rust ports and loads of other rewrites of the same functionality to various degrees. None of that really matters though as they dont really add much if any value to what coreutils provides as there is just not that much more value to add to these utilities now.

    And it is not like the GPL license of coreutils affects other binaries on the system. So if you dont need to modify it and it does not infect other things there is little point in trying to take it over or use an alternative.

    MacOS does not use a later version because they cannot. But also they don't care enough to even try to maintain their own.

    GPL is important on other larger/more complex bits of software. But on coreutils/sudo IMO it does not matter nearly as much as people think it does.

  • Is the FOSS world in danger of a corporate takeover, thanks to pushover licenses?

    Jump

  • Core Android and ChromOS don't need to be FOSS because they use the GPL. You can use the Linux kernel without having to make everything that runs on it GPL as well. Things that run on the kernel are not derivative works of the kernel. These projects are FOSS because google at the time thought it would give them an advantage to make the FOSS.

    If you add too many restrictions to a license it does not force companies to give their stuff away for free, it just means they wont use your project which can drastically stunt the growth of your project. If Linux had a more restrictive license to start with all that would of happened is no one would have heard of it today as companies would have created something else that they can use.

  • Is the FOSS world in danger of a corporate takeover, thanks to pushover licenses?

    Jump

  • There is no one size fits all safest option. Details matter and each project needs to read the licenses and decide on which suits their needs best.

    MIT is probably the safest option for a company creating a library wrapping their service where there is no real value in others taking that code. Or for simpler libraries that are fairly easy to reproduce so the need to steal the code is low. Or you just don't care what others do with the code.

    GPL is probably safest for some hobbies that does not care about companies and just wants everyone that is using their project to not bake it into a product they distribute. But also means companies likely wont want to use your project if it is a library.

    LGPL might be a good option for library code if you want other companies to use and contribute back to some complex library you are using that is hard to reproduce in isolation.

    Other licenses are needed if you want to prevent other hosted services from using your project without contributing back.

    Different licenses exist for different reasons and it all depends on what you want for your project.

  • Is the FOSS world in danger of a corporate takeover, thanks to pushover licenses?

    Jump

  • I don't think there is a good license for that. The ones MongoDB used turned the open source community against them. But that is not really my point. I just mean that some projects using MIT won't suddenly mean every company will start stealing and closing that software. Some things like coreutils and sudo just don't have the commercial value to make that worth the effort. So there is no real need to worry about these two projects IMO. Other projects are a different story altogether though. Each project needs to make its own decision on what licence best suits it. The GPL is not the one and only license that is worth using.

  • Rust in Android: move fast and fix things

    Jump

  • Inertia also accounts for time and popularity. The longer something has been around and popular the more inertia it has and the harder it is for something to change it. Back in 1985 things had a lot less inertia then they do today - C and C++ have been gaining it constantly for 30 years since then.

  • Is the FOSS world in danger of a corporate takeover, thanks to pushover licenses?

    Jump

  • Coreutils has little commercial value to take can create a proprietary fork of. There is little value that can be added to it to make it worthwhile. The same is for sudo - which has had a permissive licence from the start. In all that time no one has cared enough to fork it for profit.

    Not saying that is true of every project. But at the same time even GPL software has issues with large companies profiting off it and not contributing back. Since unless you are distributing binaries the GPL does not force you to do anything really. See mongodb and their move to even more restrictive licences.

    The GPL is not the only thing that stops companies from taking open software. Nor does it fully protect against that.

    Not does everything need to be GPL. It makes sense for some projects and less sense for others. Especially libraries as that basically forces no company from using them for anything. Which is also not what you want from a library.

  • Is the FOSS world in danger of a corporate takeover, thanks to pushover licenses?

    Jump

  • You can profit from GPL software. The only restriction is if you distribute it you also need to distribute modifications under the GPL.

    GPL also does nothing for software as a service since it is never distributed.

    GPL even explicitly allows selling GPL software. This is effectively what redhat do. They just need to distribute the source to those that they sell it to.

  • In the US we have Breast Cancer Awarnes month and a bunch of others. All we do is throw money at a problem and hope it goes away How come the Gov don't take care of people from starving?

    Jump

  • The US government does not like welfare programs because it gives money to the poor. They would rather give tax reliefs to the rich instead.

    There is loads of evidence that welfare programs can save more money then they cost. But that does not funnel money to those in charge.

  • Removed

    Hot take: Unit tests are love letters to future you, integration tests are group therapy, and end-to-end tests are necromancy

    Jump

  • I find most people don't create good unit tests. They create them too small which results in them being fragile to change or near useless. They end up being a tray for future you not a love letter.

    The number of times I have refactored some code and broken a whole bunch of unit tests is unreal. These types of tests are less then useless. If you cannot refactor code then what is the point in a unit test? I don't need to know that if I don't change the code under test it doesn't break... I need to know that when I change code my assumptions still hold true.

    We should be testing modules as a whole using their external API (that is external to the module, not necessarily the project as a whole), not individual functions. Most people seem to call these integration tests though...

  • Rust in Android: move fast and fix things

    Jump

  • 5 years is optimistic. More likely 10-20 years at least. Established languages have a lot of inertia and it takes a very long time for that to change.

  • Which command substitution do you prefer in shell scripts: backquotes `` or $() syntax?

    Jump

  • Why wrap it in a function at all? Why not just put the if at the top of the file?

  • iPhone Pocket: a beautiful way to wear and carry iPhone

    Jump

  • Crafted in Japan, iPhone Pocket features a singular 3D-knitted construction that is the result of research and development carried out at ISSEY MIYAKE.

    It's just a knitted tube... Basically a iPhone sock.

    Think I am going to start calling all my socks 3D-knitted to make them sound cooler.

    iPhone Pocket in the short strap design retails at $149.95 (U.S.), and the long strap design at $229.95 (U.S.).

    ... Seriously... They charge way to much for such simple things.

  • Why do some people fork repos but make no changes to them?

    Jump

  • While true and some will do it for that reason, I bet most do it simply because the friction to forking is so low.

    Some might have an intention to work on it but then don't or might start looking at it in detail then give up or get to busy or lose interest.

    Others might just click it to save it for later.

    And don't forget all the people that click it by accident.

    It's not like it is a big investment to click the button.

  • Why do some people hate Manjaro?

    Jump

  • Probably something to do with their main package deleting the pacman lock file so it can run a nested pacman update command... Which means two pacman instances running at the same time and nothing stopping other ones after that nested one has completed.

  • I am sorry, but everyone is getting syntax highlighting wrong

    Jump

  • If everything is highlighted, nothing is highlighted.

    Kinda ironic given the whole site looks like someone attacked it with a highlighter.

  • Linux Users

    Jump

  • I have more then once gave up on pressing up, hit ctrl + c to reset only to see the command I wanted briefly flash up as I am hitting ctrl + c