- @hfkldjbuq@beehaw.org to
- â˘
- www.marktarver.com
- â˘
- 5 hilabete
- â˘
- @hfkldjbuq@beehaw.org to
- â˘
- www.marktarver.com
- â˘
- 5 hilabete
- â˘
cross-posted from: https://beehaw.org/post/113520
Some quotes
Twenty years ago, the phrase âopen sourceâ had a definite meaning in computing which is quite different from the sense it has nowâŚ
Why is Free Software so Bad in Quality?
Most free software is poor or unusable. This is heavily disguised because protagonists like to use the isolated points fallacy to sell the idea FOSS is great.
âŚ
âŚif youâre lucky enough to attract such a team you need to keep them together. And for that you need capital and that is exactly where FOSS falls down. This is the main reason why so much FOSS is of poor quality.1
FOSS was Built Out of Corporation and Tax Money
Open Office was derived from Star Office which was the product of StarDivision and Sun Microsystems. It was not put together by a hacker living in his momâs spare bedroomâŚ
Emacs was supported financially by people working at the MIT AI Lab, which means that it was funded by Uncle SamâŚ
Linux isâŚmostly a copy of Unix, despite howls to the contrary it is deeply unoriginal, being based on ideas going back to the time of the Vietnam War. These ideas were in turn evolved within Bell Labs by its creators who were also well-paid professionals. Linus Torvalds really copied an idea whose basis had been funded by university and corporation money and without that basis there would have been no Linux.
Free Open Source is not often Innovative
âŚlot of FOSS is poorly written reverse-engineered copies of existing commercial software. Innovation is hard; it requires time and brains. Reverse engineering is a powerful disincentive to innovation since anybody who does spend R&D capital in innovation, can have their ideas reverse engineered.
âŚ
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- Itâs FOSS
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
Community icon from opensource.org, but we are not affiliated with them.
- 0 users online
- 4 users / day
- 17 users / week
- 47 users / month
- 282 users / 6 months
- 17 subscribers
- 1.55K Posts
- 5.37K Comments
- Modlog
What kind of bullshit is this. I donât even know where to start unpacking this. đ¤Śââď¸
You gotta start somewhere otherwise you never start anywhere
Sure. Letâs start here:
One can use the term âFLOSSâ (âFree/Libre/Open Source Souftwareâ, the term I personally prefer) or âFOSSâ (âFree and Open Source Souftwareâ), and the author does it every now and then, but it needs to be done thoughtfully.
Itâs like using âbussesâ, âtramsâ, âbus-tramsâ, and âpublic transportâ interchangeably. This alone shows that the author has no clue what theyâre writing about.
If you doubt that second part, just look at the absolute clusterfsck that Log4shell was, and how it affected every single Big Tech company (proving they use the FLOSS Log4j software package).
Plenty of FLOSS projects are supported by donations (in time, and in money). Some are supported by grants. Some are supported by corporate sponsors.
What is the point there? Can FLOSS developers not be allowed to earn a living developing their freely-shared software?
Also, in the previous point the author notes:
How can you get that âcapitalâ if you donât accept donations and donât apply for grants?
Thereâs plenty of problems with FLOSS (including how toxic corporate sponsorship can be), but this person has no clue what theyâre talking about. Low quality hot takes by someone with zero understanding of FLOSS.
Could you please quote the author in that? Because I do not think Mark Tarver conflates them. The author begins by contextualizing the shift in meaning of the term âopen sourceâ, also explicitly states the meaning in text of âfree open source softwareâ
then even mentions the term free
In point 2, the author did not actually measure it other than having an opinion. But historically many free software (or most software in general) has bad usability: GIMP (try drawing a circle or adding text), KDE apps and Element matrix (convoluted interface with so many buttons), Emacs (its proposition is different, but still the oldest example of a hard to use free software). IMO mostly GNOME apps are easier, more intuitive to use in general, but in many ways it is a clone of MacOS. Bad UX/UI is because historically there are only constructors (aka programmers) doing the job, so they do not mind designing, iterating, assessing the UX/UI first, also taking into account accessibility, etc.
That is the exact point. That generally relying on donations (as many free software do) is not a sustainable model, or at least a great risk as exemplified with OpenBSD and OpenSSL. That is, for developing good quality, software that is continuously maintained, developers need to be financed by companies or a commercial ecosystem (https://www.gwern.net/Complement) so they can have decent living instead of doing impossible volunteer work forever or just stop maintaining the project entirely.
Many (probably most) companies just will not donate or contribute code back to free software they use. They just want to profit the max they can. do read
A good start would be Brandoliniâs principle of bullshit, stating that âThe amount of energy needed to refute bullshit is an order of magnitude larger than to produce it.â
That does not add useful info to the discussion, quite the contrary. I prefer having insightful discussion when people have different views so that maybe we can learn some pertinent info instead.
It does add meaningful info to the discussion: it shows why people would be less-than-eager to reply to a post to contradict it. It also shows that good faith discussion, trying to achieve a consensus (or at the very least better understanding) should start with simple and basal claims, otherwise the other side will not answer.
Now analyse your own post, and notice how many claims you did to chain your argumentation:
Youâre also making a definition mess, for example at the end youâre contrasting âopen sourceâ with âcommercialâ, even if both attributes are orthogonal to each other. (i.e. you can have non-commercial closed source, and commercial open source). Thereâs also the issue with âfree-as-free-speech softwareâ and âopen sourceâ being conflated together.
I wonât bother defending free and open source here because, frankly, Iâm more of a lurker than a debater, but this is not the way to introduce a discussion.
Just in case, I did not write that piece. I just found it interesing so I shared it. It is interesting you point those out, but I cannot do anything about the way it was wrote; still I find many of the arguments to be relevant.
So all I wanted were strong counterarguments, but nobody was able to provide such.
Also on your points, it seems to me the author assumed some knowledge from the reader; indeed should have provided more references. For example for the 2 first points
Then my bad on claiming that those were âyourâ claims, what I said should apply to the original author.
My point still stands though. Those questions are still better addressed individually; for example, gathering some data on software quality and contrasting open and closed source, including the reference that you linked in #2. Then I bet that youâll get better arguments, as the matter is more approachable for discussion.
đŞđď¸ I smell bait đŞđď¸
This is particularly rancid bait.