Open Source Software Community - it's about ethics in Code of Conducts

  • Want to keep track of this thread?
    Accounts can bookmark posts, watch threads for updates, and jump back to where you stopped reading.
    Create account
So say theoretically I was writing a piece of open source code where I would be fine if people used it in their own proprietary software as long as they contribute bug fixes and new features to my original code, which license should I use?
 
This is actually a greatly exaggerated issue. Most modern CPUs actually use a lot of clever emulation tricks to fake Good Enough™ approximations of legacy features to avoid losing performance and efficiency to them.
You do understand that those "clever emulation tricks" amounts to having horribly complicated decoding logic to decompose complex instructions into microinstructions for dispatch, right? That logic isn't made of magic pixie dust... it takes up actual space on the die. That's why an ARM core doesn't take up anywhere near as much silicon as an x86 core. That's also why an ARM core has a better cycles/watt ratio than any comparable x86 processor. This isn't exaggerated... this is the reality of microprocessor design. x86 microprocessors are compelled to carry around lots of instructions that few people use because of technical debt. A platform lacking that technical debt can be smaller, faster, cheaper, and use less power.. That's why ARM succeeds in the mobile space.
Literally the first company Apple approached looking for CPUs for the original iPhone was Intel, and Intel refused because they thought the iPhone was going to be a commercial failure. ARM was their backup plan. Mind you, this was while AMD's Athlons and Phenoms were actively kicking the shit out of Intel at every turn on power efficiency. Stop uncritically eating up the revisionist tech history myths.
And what's your excuse for Android then? Were Android OEMs simply copying what Apple did? They (Motorola, et al) could very well have chosen to go with Intel, but they didn't. What was the thinking? For that matter, why didn't they go with AMD? Apple had solid reasons for considering Intel, but in the end if you show people two phones that are of comparable functionality and one of them has less battery life because they went with Intel, I think we both know which phone they're going to buy, ceteris paribus.
Can you just call it the unlicensed rectangular port and get away with that?
Insofar as there may be patents involved in implementing so much as USB2, no, you can't. For USB1? You probably could. People have done similar with DisplayPort and HDMI.
Reminder that Stallman, the inventor of the GPL, had to invent a much more permissive copyright license for gcc headers because nobody would have used his compiler if it was under the GPL. The GPL infects codebases and inconveniences people by design. I much prefer the MIT license for this reason.
Or then there was the time he rewrote the FDL to let Wikipedia use CC-BY-SA because the previous version would be broadly incompatible with that. Oh, or then there was the time he went after Tivo for doing something that even he himself agreed didn't violate GPLv2 and effectively split the free software community because Linus and everyone else who'd bought into GPLv2 thought he was being an asshole and refused to relicense their stuff under GPLv3. Guy really has a history of doing dumb shit.
Is BcacheFS made by the guy who keeps trying to cowboy his patches past the release window? Linus telling someone to STFU is honestly pretty tame for him.
I think so, yeah. Christ, there's several people like that, honestly. However, didn't they just remove BcacheFS from the kernel? I thought I read that the other day.
 
Were Android OEMs simply copying what Apple did?
Yes, now take your meds.

As for all that schizoposting about technical debt, RISCfags have been crowing about how it's over for x86, RISC is the future, x86 is doomed by its technical debt for thirty fucking years now. Give it up, bro, it's not happening, x86 is immortal because the immense weight of legacy code and legacy software is too much for RISC to handle. Rewriting 40 years of software for RISC isn't going to happen, and the losses from emulating the entirety of x86 on a reduced instruction set is so great that it's more efficient to just keep using x86. Cope and seethe, RISC only dominates mobile because mobile started from zero.
 
Last edited:
So say theoretically I was writing a piece of open source code where I would be fine if people used it in their own proprietary software as long as they contribute bug fixes and new features to my original code, which license should I use?
If it's proprietary then by definition they don't owe you any of their derivative work, bugfixes or otherwise. So if you're fine with that then just release it under the BSD or MIT license and be done with it. Both of those are pretty much "don't claim this is yours" and not a lot else. If you're not fine with that you might want to stop and ask yourself why before considering Apache, GPL, or other such licenses.
 
So say theoretically I was writing a piece of open source code where I would be fine if people used it in their own proprietary software as long as they contribute bug fixes and new features to my original code, which license should I use?
lgpl probably
the lgpl permits linking from proprietary software, but you have to distribute your modified sources of the lgpl-licensed library if you make any changes
depending on how you feel about tivoization, you might want to choose further between lgpl3+ or lgpl2.1+
before considering Apache
apache is a copyleft license, android is released under it
and if you know just how bad android is as a platform you would understand why the apache license is not a great idea if you care about user freedom
Oh, or then there was the time he went after Tivo for doing something that even he himself agreed didn't violate GPLv2 and effectively split the free software community because Linus and everyone else who'd bought into GPLv2 thought he was being an asshole and refused to relicense their stuff under GPLv3.
this is actually a plain demonstration of the difference between "open source" and free software: linus wants you to share your modified code and doesn't mind if you pull a tivo, while stallman wants you to never interfere with the user's right to do what they want to with their computer. that's why he wrote the gpl3: to fix a hole he left open in the gpl2
the free software community pretty much agrees that the gpl3 is better for freedom than gpl2, so most new projects use it, along with all the projects that did the fsf-recommended practice of adding "or any later version" to the license file (it eliminates a lot of potential license compatibility issues and also (as a secondary effect) allows issues such as tivoization to be fixed more easily)
linux actually couldn't be relicensed if linus wanted to, he would have to chase down every single contributor and get them all to agree (basically impossible)
 
Most companies (except big-tech) don't give a flying fuck what open source license a piece of software uses, if it does what they need they'll use it regardless. In practice there exists only public and private code. Don't want evil entities to use it? Then don't publish it on the Internet.
I usually add the MIT license for completeness sake and its brevity, or I just don't add a license at all.
 
That's also why an ARM core has a better cycles/watt ratio than any comparable x86 processor. This isn't exaggerated... this is the reality of microprocessor design. x86 microprocessors are compelled to carry around lots of instructions that few people use because of technical debt. A platform lacking that technical debt can be smaller, faster, cheaper, and use less power.. That's why ARM succeeds in the mobile space.
It's not that simple, back in 2015 Asus partnered with Intel to use an Intel Atom x86 chip in their Zenfone 2, which had comparable battery life to other flagships at the time https://www.tomshardware.com/reviews/asus-zenfone-2,4267-9.html For reference, the Zenfone 2 had a 3000 mAh battery, the same as the LG G4. The reason why ARM took over in mobile computing is because early ARM chips were already designed to be low wattage, and it's easy to buy an ARM license to make chips suitable for your phone or gameboy. On the other hand, x86 is exclusive to Intel and AMD, and it took a while for either of them to decide to make a mobile chip, and by the time the Atom existed, it was already too late for Intel to gain any ground in the phone market. The Atom was very successful in the Netbook market, however, until Steve Jobs killed it permanently with the iPad.
And what's your excuse for Android then? Were Android OEMs simply copying what Apple did? They (Motorola, et al) could very well have chosen to go with Intel, but they didn't. What was the thinking? For that matter, why didn't they go with AMD? Apple had solid reasons for considering Intel, but in the end if you show people two phones that are of comparable functionality and one of them has less battery life because they went with Intel, I think we both know which phone they're going to buy, ceteris paribus.
Google was already developing Android (as basically a Blackberry clone) when Apple approached them as a partner for the iPhone. If they had wanted to use Intel chips, they would have almost certainly used their ARM mobile chips, although it's not impossible that they could have already gotten their hands on Stealey chips. However, ARM had a huge advantage for Android, since it was a more or less freely available standard, instead of being vendor locked to one manufacturer, and so there is no chance that Google and HTC would have ever chosen an Atom for the Dream. Even Intel's ARM chips had a history of proprietary extensions for vendor locking, which is why they were unpopular, and Intel sold their rights.
 
I wonder what kind of nightmares go on in things like modern intel wifi chips.
I wouldn't be surprised if they had a tiny embedded ARM core in the Wi-Fi adapter. Remember the PS4 has two small ARM cores instead of a Southbridge on their x86 boards (according to the fail0verflow group that worked on getting PS4 support into the mainline kernel), and many other weird horrors.

VIA has been making amd64 SoCs since Bush was still in office. This is why the Chiniggers have been licensing their licenses for their own "home-grown" silicon.
Ah I knew about VIA (who acquired their license when they got Cyrix) but forgot they had the x86_64 stuff too. I remember the benchmarks for the Zhaoxin chips being terrible years ago. It would be nice if they could make something competitive .. or even competitive on wattage/power for lower end embedded chips. There needs to be a 3rd player in the x86 space.

Remember the VIA C6 processor family also had their own Rosenbridge architecture side-by-side the x86 stuff. They were trying to sideline their own processor next to x86, but ended up just making a non-patchable hole in these chips (often used in point-of-sale machines) because you could switch to the second instruction set in user-mode (there's a great talk from DEF CON 26 / 2018 about finding this exploit).

Ideas, not source code, are what matter, and those aren't protectable by copyright.
New Zealand is a terribly authoritarian state with too much socialism and zero freedom of speech or gun rights, but they did ban software patents. Software patents are idiotic and really need to go away.

by the time the Atom existed, it was already too late for Intel to gain any ground in the phone market. The Atom was very successful in the Netbook market
I really like the Atom chips. I still have one running on the Linux machine I use as a router. It's and old industrial network device I found on eBay and it's passively cooled with the top of the metal case being one big head sink. It can handle 1Gb traffic fine. I never had an Edison board, but I heard Intel really fucked up in competing in the Raspberry Pi space with a lot of those kits being terribly unreliable. It would have been great to see more x86 in mobile. AMD had similar chips like the Athlon II Neo, but they weren't nearly as good.

The current version of the Intel Atom line seems to be the N100? I have one of those in a mini-PC and it works alright.

I hate ARM on mobile because there's no standard. At least Microsoft mandated UEFI+ARM on all their Nokia mobile devices, which could potentially be a great starting point for Linux phones, but no body really bothered to try to get anything working on them. The Postmarket OS page on the Lumia 950 shows that even with UEFI, it still needed a devicetree for ACPI: https://wiki.postmarketos.org/wiki/Microsoft_Lumia_950_(microsoft-talkman)

What made Linux shine on PC was that the IBM PC architecture was pretty damn standard. Every PC was guaranteed to have a lot of basic things. (The PS4 is a great example of an x86 that is not a standard PC and can't boot like one). All our phone-slop is a random ARM with random shit soldered to random pins and buses plopped down wherever the fuck we feel like cause fuck you that's why. Here's the source code for our kernel on a random Chinese website in a tar.zip file. It's a dumpster fire. We're not violating the GPL but at the same time: fuck you.

The only team that's made headway into truly alternative OSes on the mobile space is PostmarketOS and it's a hard uphill struggle for sure.
 
hard drives don't store data with photons
and if he's using an array of dvd drives to store his website data then maybe that is the real source of his problem
I'm here to A-log correct you, he's referring the signal passing through the transistors. Of course, those aren't photons either, but he's a Podcast Engineer, not an entomologist. As always, this situation can be reduced to the old proverb "local man attempts to improve things slightly, fails".
 
this is actually a plain demonstration of the difference between "open source" and free software: linus wants you to share your modified code and doesn't mind if you pull a tivo, while stallman wants you to never interfere with the user's right to do what they want to with their computer. that's why he wrote the gpl3: to fix a hole he left open in the gpl2
Stallman literally rewrote the rules when Tivo did nothing wrong. You don't get to pretend that didn't happen and retroactively claim they did something wrong. For some strange reason that rubbed people the wrong way. And no, you also don't get to pretend that everyone piled behind him and supported GPLv3. That didn't happen. Check the stats on github and elsewhere.
New Zealand is a terribly authoritarian state with too much socialism and zero freedom of speech or gun rights, but they did ban software patents. Software patents are idiotic and really need to go away.
Patents are one of the few things that works when it comes to making corporations pay what they fucking owe. I'm not willing to give up on that just because patent trolls exist... especially not since the America Invents Act added the ex parte review system which has been quite successful in shitcanning bad patents (software patents included). As far as I'm concerned if you've got a software patent then as long as you offer a carve-out to open source/free software such that merely writing software and distributing it is not infringement, but deployment in SaaS or OEM'ing it into products is. That's more or less what MPEG-LA has been doing for the better part of a decade now and it works. This is an easy stance to take, I suppose, in that there really isn't a lot that would qualify as patent-worthy in the field of computer science anymore... so most patents are 98% guaranteed to be bullshit. Not willing to toss away that 2% if it means corpos get stuck with a hefty bill.
 
The way I interpreted Dear Feeder's statement, the platter isn't the spinning rust the filesystem's on, it's the screen in front of you, that you're currently using to read my post about the Dear Feeder's, and I say this without any snark or irony intended in my words, perfectly valid and entirely understandable crashout over IT being the worst imaginable desk job.
 
Stallman literally rewrote the rules
Yes.
anybody with any backbone at all knows to rewrite some rules when somebody violates them in spirit but not in letter
when Tivo did nothing wrong
do you have your four freedoms on a tivo device? can you choose not to run tivo's software on the device? can you make modified versions of your tivo software and then run it on your device?
And no, you also don't get to pretend that everyone piled behind him and supported GPLv3.
of course not everybody supported gpl3, but most of the people who didn't are not actually free software people
That didn't happen. Check the stats on github and elsewhere.
i'm sure a software forge where 99% of the projects are inactive is a great place to check numbers for license usage
i sure as hell see a lot more gpl3 than i do gpl2
 
That didn't happen. Check the stats on github and elsewhere
I don't think saying the entire FOSS community agreed with Stallman is right. But saying almost everyone disagreed too. There were definitely people that wanted things to move to gplv3. Linus pushing back definitely had an effect on the opinion of people around the license change. I do know, after the gplv3 was revised, even his opinions on it softened. Because it made exceptions for the things he particularly had a problem with. Like legal reasons for not allowing open source software (I personally don't really buy into security by obscurity, at least not if it's a sophisticated enough attacker. so I feel like the legal enforcement of that is bullshit, but that's another topic). I would say people were split on the GPLv3.
 
I would say people were split on the GPLv3.
it all depends on whether you're a free software supporter or an open source enjoyer
a lot of people seem to think the two groups are more or less the same, when they really have almost nothing in common besides that thing they do where they share program sources under terms that let you use the source too
open source is basically about sharing code for efficiency, while free software is like right to repair taken to its logical conclusion in the software world
 
Back
Top Bottom