Unpopular opinion: i64, int64_t, Int64 and similar types should be named according to their actual meaning, Ring64.
Even better, all programming languages should have a Ring[N] type that provides unit, zero addition and multiplication over a domain of N-bit strings, with the compiler applying proper optimizations when available (and requested).
It IS a ring on most implementations, but there were good flexibility (and portability) reasons behind all behaviours left undefined in C.
Yet this is a good objection... for standard C.
They are both right, btw.
Never trust non-GPL code... 🤣
You are technically right, but i think they SHOULD be rings (and named accordingly). So that programmers would learn from the beginning to live with the clear semantics of rings, always aware of the risk of overflow.
Actually the problem with #GPL and #AGPL is that they are not strong enough to protect and reserve the knowledge that free software expresses to the commons.
Full access to software sources and full right to hack it, just like writings and any other human expression, is the most fundamental human right.
Preventing such right to any human is preventing them to be human, a specie that defines itself as *homo sapiens sapiens*.
It's somewhat funny, but very incorrect.
Even MIT and BSD impose obligations on people builing on licensed code, just fewer than a #copyleft.
Actually, such swallow depiction of free software licenses is quite similar to calling int64_t as "integer". 😅
As for an even stronger copyleft, I wrote the #HackingLicense: http://www.tesio.it/documents/HACK.txt
I must admit that I'm not yet happy with its formulation, but it can give an idea of what I hate in weaker copylefts like the #AGPLv3.
I'm going to remove the "organizations" thing. Making it shorter would be nice but apparently I can't without opening to corporate abuse one way or another.
In any case, if you want to give it a read and show me a way it could advantage big corps, I'll promise I'll study a fix for that.
On the other hand, a smaller company is at a huge disadvantage when using GPL, because this way a bigger entity can just buy the product and take over. Again, utilizing sheer manpower. Having your source code closed or under a restrictive license is a huge benefit in this case.
BUT Google does not use or extend AGPL software. Why?
I'd argue that a strong copyleft is better than a permissive license against steer manpower.
And that against such big corporations not even keeping the software closed source provide an effective protection.
The Hacking License, instead, gives the original authors full (non exclusive) copyright and patent grants on any derived work.
>The Hacking License, instead, gives the original authors full (non exclusive) copyright and patent grants on any derived work.
Thanks. I'll stay away from this cancer as much as possible.
Fine... but why?
I mean, is this a philosophical hate against common good and the commons or something you consider pragmatic, apolitical... such as profit in a capitalist world or something like that?
Even if we do not agree on this matter (mostly because we do not agree), I'd really like to learn your perspective.
Mozart's music is common good.
So is Bethoven's or Vivaldi.
Shakespeare poems are common goods. And Montale's too.
Actually most of human knowledge is common good.
A huge amount of software is common good. I'd argue that most global cpu cycles at any given time this year are running free software that IS common good.
This does not means, in any way, that you shouldn't be paid for creating it if you want to.
So I deduce your is a fundamental mistrust in society, in the communities around you that could benefit from your work if it was available.
To be fair, you might be right on this. There is a huge risk we evolve back to egocentric apes unable to collaborate if not under the rule of few... owners.
As for me, I choose to still hope for the better from our specie.
Anyway... thank for sharing!
I don't.
On the contrary I expect most people to NOT subscribe my ideas, just because I've seen this happen so many times.
I'm really interested in your perspective, mostly because I do not understand it.
Being slaves of a common master (or few common master) is not enough to collaborate.
But in an individualist and materialist perspective, I see it's the best one can hope.
In a way, it's the curse of dimensionality at work.
You mentioned a bunch of dead people, but that's what they are now. Dead people. They can no longer benefit from the results of their endeavors. This is why there is this thing called public domain now, and I wouldn't mind if my works become public domain in many many years, but just as Shakespeare during his lifetime, I intend to profit from my work as much as I can right now.
Regarding Google and AGPL. One of the biggest risks related to this license is rather unclear application practices. They haven't been enough court cases to know what to expect in case you land there. Nobody wants to be the first one here, not even Google with their army of lawyers.
Here's their reasoning regarding AGPL:
>The primary risk presented by AGPL is that any product or service that depends on AGPL-licensed code, or includes anything copied or derived from AGPL-licensed code, may be subject to the virality of the AGPL license. This viral effect requires that the complete corresponding source code of the product or service be released to the world under the AGPL license. This is triggered if the product or service can be accessed over a remote network interface, so it does not even require that the product or service is actually distributed. Because Google’s core products are services that users interact with over a remote network interface (Search, Gmail, Maps, YouTube), the consequences of an engineer accidentally depending on AGPL for one of these services are so great that we maintain an aggressively-broad ban on all AGPL software to doubly-ensure that AGPL could never be incorporated in these services in any manner.
From https://opensource.google/docs/using/agpl-policy/
For a smaller company, the risk is even bigger. Imagine your competitor suing your on the grounds of the use of some AGPL piece of code and demanding you release the algorithm behind your successful whatever internet service, then copying it and incorporating into their service. Without actually releasing the source code. Totally realistic scenario, if you ask me.
Btw, Vivaldi died in poverty. As did many other famous artists in his time. Would you like to follow his example?
I'm not sure I understand what you describe as a risk for the smaller company in your example.
Suppose that they actually release their super cool software (not algorithm) as AGPL and a competitor includes it in his own codebase: then they are violating the small company copyright for profit, from a legal perspective a criminal act that would lead them to jail.
As for Google, I know why they don't want to use AGPL code... which to my eyes is a great advantage of such license.
The objection about Vivaldi dying in poverty is a good one, but easily dismissed: the problem is NOT the fact his art is common good, but the fact he lived in an unjust system.
And this is actually a huge problem today too.
BUT people living in an unjust system can fight such system... or not.
I do.
In case you have not noticed, we live in a very competitive world. If you won't take an advantage, someone else will. In my area, quite a lot of code ends up published on github under a permissive license like BSD or MIT, because it's just easier to maintain this way. Common good or any other similar concept doesn't apply here, it's just pure profit and convenience.
Oh... and there is no such thing as a perfectly just system.
Uhm... sure, maybe there is no "perfectly" just system, just like there is no perfect circle or perfect sphere in the real world.
Does it means that a sphere system is unconceivable?
If not, why should a just system be unconceivable?
Do we live in a just system?
No.
Could we live in a MORE just system?
Sure.
Now, I do not know exactly where you live but I'd guess it's somewhere in the US or in one of their colony.
I can really relate to your feeling: after decades of oppression it's totally natural to surrender and internalize the oppressor propaganda as if it was not just true, but the only possibly truth.
But, well... it's not.
"Homo homini lupus" is a very inefficient and irrational way of living together.
The energy each individual spend to compete with everybody else is subtracted to more productive tasks.
And obviously there are many alternatives.
One are gift societies, like nomadelfia https://www.nomadelfia.it/en/
But a less radical one is simply to produce common goods for a community, binding each member to rules to access such goods.
Community, commons and similar words all derive from latin "cum-munis" which meant "bound together by rules and mutually responsible".
Freed from competition, people can do much more with their time and energy!
But obviously, this simple rational consideration is not going to shaken your beliefs in individualism... that's not how oppressive religions work.
In any case... good luck!
@newt you accept the reign of proprietary software, the culture and the industry it established, and then try to come up with excuses for it. Copyleft rejects it and wants to displace it. The small company shouldn't compete with the large to establish it's own little international monopoly on it's own little obscure product, then whine about how copyleft doesn't help them. It should directly serve the local population like electricians, mechanics or plumbers do. It should create infrastructure and dictate quality standards. Nobody want to do this hard work, it's just easier accept the narrative that copyleft was tried and didn't work, which remains the last line of defense for the established culture. We don't know what a true competition is, in true competition most of us would be yer average plumbers, and none of us wants it.
@Ted @Shamar @duponin
The problem with GPL is that it hugely benefits bigger players, who can earn money from consulting and support, while leaving smaller software companies at a huge disadvantage. The latter are a lot better from using BSD or MIT licenses for their published works and some form of EULA with closed source code for end products.