Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The MIT licence does not require this.


I'm not an expert, but I very much doubt this.

The FSF calls it a "free license" [1] and I don't think they would if they didn't make the source code available.

Source code available is necessary but not sufficient for Free software, see [2]

> Freedoms 1 and 3 require source code to be available because studying and modifying software without its source code can range from highly impractical to nearly impossible.

[1] https://www.gnu.org/licenses/license-list.en.html#Expat

[2] https://en.wikipedia.org/wiki/Free_software

EDIT Oh sorry, you mean for the LICENSE to be available. Never mind then.


And you're entirely wrong. MIT just require attribution, not giving the source code.

That is why companies and corpo programmers LOVE BSD/MIT code, they can freely steal I mean use it in their for-profit products without giving anything back but some bit of text hidden in about box


You can compile MIT software and distribute the binary while saying “fuck you” to anyone who asks for the source.

You are thinking of copyleft (e.g. GPL)


If that were true, the FSF wouldn't call it a free license.


> If that were true, the FSF wouldn't call it a free license.

It is true; the license gives you the source, to do with as you please, including closing it off.

Famously, Microsoft included BSD licensed tools in Windows since the 90s and did not distribute the sources!

And that is completely legal. If you want to force the users to distribute their changes to your open source product when they are redistributing the product, you need to use GPL.


You should have linked the MIT License on Wikipedia (or anywhere else) instead of Free Software.

The license is only three paragraphs long. You can see it does not contain text supporting your claim.

https://en.wikipedia.org/wiki/MIT_License


Well, I'm confused.


It's actually very simple:

MIT/BSD licenses are pro-business - any business can take the product, change a few lines and redistribute the result without making their changes available.

GPL is pro-user - anyone who gets the source, makes changes, and then redistributes the result has to make their changed sources available as well.


The FSF has written extensively on why (in their opinion) you should prefer copyleft licenses over non-copyleft licenses, but they don't require a license to be copyleft in order to be considered free. It's worth spending a bit of time on their site to understand their point of view. Just be careful not to drink too much of the Kool-Aid or you'll become one of those annoying people who never shut up about the GPL on forums.


> you should prefer copyleft licenses over non-copyleft licenses,

For most, but not all, software. Stallman did famously argue for libvorbis, which you may know as the ogg codec used mostly by games and spotify, to be licensed under BSD instead of the (L)GPL.


True, there are exceptions. Stallman thought strategically. Having a free-but-non-copyleft licensed reference implementation is necessary if you are trying to wrest dominance from an established but proprietary standard.

But I'm willing to bet that he'd have pushed for GPL if he wasn't trying to topple MP3.


Don't listen to spauldo, GP. Drink the delicious Kool Aid that is free software. Bring that joy to everyone else you find.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: