7 ms·
I think you're confusing developers who want to use open source software in closed source applications with the free software movement. To stereotype: GPL
by falcolas 13y ago
I think you're confusing developers who want to use open source software in closed source applications with the free software movement.
To stereotype:
GPL == best for users
BSD == best for developers
- btown 13y agoHowever, many (nontechnical) users just want software that's free (as in beer) and works well. Therefore, what's best for developers (i.e. what attracts developers) is also seen as good for these users.
- sillysaurus2 13y agoAs a game developer, you're hurting our entire industry by shutting us out of using your software. And in the end, we'll find a way, with or without you. We'd rather stand with you, but we can't go near GPL'd code. You know CodeCombat recently open sourced their game? They're basically the first gamedev company in the history of gamedev to do that -- a non-indie company who open sourced their current-gen tech. It's a good idea, and I hope more companies follow. So, times are changing, but in the meantime your strict adherence to "GPL license == good guys; MIT license == bad guys" is detrimental to pretty much an entire community of programmers. (Programmers with zero options; they're not going to ragequit the gamedev industry just because engines are closed source.)
- _delirium 13y agoWhy would I want to give free labor to massively wealthy AAA studios who don't want to give back anything? If they want to use my code in their proprietary products, they can pay me to license it, just like they expect others to pay them. I don't see how it's "standing with me" to use my code to make the next Madden, without giving back either code or cash.
- teamonkey 13y ago> massively wealthy AAA studios Straw man. > who don't want to give back anything Straw man.
- eropple 13y agoYup. Personally, as an indie developer who is certainly not massively wealthy, I've submitted a PR to GLFW (my windowing/input system) to support Retina screens on OS X. Of my other open-source dependencies (boost, vorbisfile, logog, physfs, and GLEW), there's just nothing I've needed to patch. Otherwise I would've. There's nothing under GPL/LGPL I need or particularly want, but I do benefit from BSD-based stuff if only because I can't statically link LGPL stuff and I find the GPL unethical. Of course I'll give back where I change stuff, because I'm not an asshole. But GPL/LGPL ignores reality in too many ways to be viable; I personally like the CDDL quite a bit but nobody uses it.
- justinhj 13y agoBy this logic why would anyone contribute to the OSS of large corporations like Oracle or Facebook? I'm also a game developer and was able to open source a chunk of AI software to the development community which has been used in commercial games but also many education and personal projects. That would not be possible without licenses like MIT.
- lutorm 13y agoThat's not correct. If you wrote the software you can do whatever you want with it, including releasing it under the GPL.
- sillysaurus2 13y agoIf you wrote the software you can do whatever you want with it, including releasing it under the GPL. Nope. Gamedevs are covered under both non-disclosure and non-compete agreements. There's a lot of red tape to cut through to release something as open source. Even if you've written it at home on your own time, companies have made a big deal about employees open-sourcing code before. This is doubly true in the finance industry. Without MIT licensing, there would be an extra hurdle of "GPL? We cannot under any circumstances be associated with GPL." It's absolutely silly, but absolutely true. I'm speaking as someone with firsthand, I've-been-there-in-person-and-dealt-with-this experience. Also, by releasing it as GPL, no other gamedevs can use it. We gamedevs like to release code that other gamedevs can use.
- Morgawr 13y agoThat doesn't sound like a GPL problem, it sounds like an industry problem. As a game developer I'd rather complain with the industry and try to follow an ethical path (i.e. freedom with GPL) rather than complain to those people who release their hard work for free under the GPL. I admire those people.
- justinhj 13y agoSome game developers have been able to contribute software using LGPL to get around the restrictions of both corporate legal departments and the confidentiality agreements you have to make with Sony, Microsoft and so on. Electronic Arts for example made a port of Webkit which can run Playstation and Xbox, which is a linkable library and includes no reference to third party API's. Personally I choose a license relevant for the kind of software and what it will be used for. When that includes software I want people to be able to use in commercial software I use MIT. I'm still releasing hard work for free, I don't have your admiration, but people get to use it. Facebook uses the PHP license for HHVM which is a very significant OSS contribution, and has very similar terms to MIT.
- deleted 13y ago[deleted]
- perbu 13y agoYes! If my work can generate wealth for other it makes me happy. It's not a zero sum game.
- klrr 13y agoYou know Id Software open sourced many of their engines[0] and that have spawned tons of derived works[1]. 0. https://github.com/id-Software https://github.com/id-Software 1. http://en.whttp://en.wikipedia.org/wiki/File:Quake_-_family_tree.svg http://en.whttp://en.wikipedia.org/wiki/File:Quake_-_family_...
- sillysaurus2 13y agoYes. Those are old engines, not current-gen tech. They make money off current-gen tech until open-sourcing it makes more sense to them from a financial perspective. This is distinctly different from what CodeCombat has done, which is to open-source their current-gen tech. There aren't going to be any financial consequences (or any other kind), because it's a good idea and there's no reason not to open source. I'm just saying they're the first non-indie Gamedev company to do so (as far as I know) and they deserve all the credit for it.
- CJefferson 13y agoThey only open-sourced them once their value to Id was approximately zero. It's still a really cool thing to do, but neither Id (or any other game company I'm aware of, anywhere, ever), has released their game as GPL while they were still making significant amounts of money from it (which in practice means within the first couple of months, for almost all games).
- hisham_hm 13y ago> As a game developer, you're hurting our entire industry by shutting us out of using your software. And in the end, we'll find a way, with or without you. We'd rather stand with you, but we can't go near GPL'd code. Poor you. The game industry _chooses_ not to go near GPL'd code because they want to sell proprietary software. Counteracting the existence of companies doing proprietary software is the very reason why the free software movement was started in the first place. Yes, the free software movement is supposed to be detrimental to the developers of proprietary software and has no incentive to cater to their needs. Do you think we want to make Windows or iOS a more attractive platform? Or to build components to be used to improve proprietary engines instead of helping free ones because hey, the proprietary devs may send a bugfix our way? No. MIT-license users are not bad guys -- I have both GPL and MIT code out there myself -- but choosing a non-copyleft license because it helps proprietary developers is not a good reason. I chose MIT to interoperate with other free software; if it wasn't for that I would have chosen the GPL or the LGPL. > hurting our entire industry I think the entire software industry is _helped_ if I drive it towards free software. I don't care how many billions the next Call of Duty game will make. I care if local developers in my country can get a consulting gig because the system my government uses is open source and so they have a shot at fixing its bugs instead of having my government sign a multimillion dollar contract with a major foreign company and get locked-in to it. > (Programmers with zero options; they're not going to ragequit the gamedev industry just because engines are closed source.) Weak argument. Back then would you say "system programmers are not going to ragequit the industry just because operating systems are closed source". But instead, they wrote open operating systems. Follow their example. Write a free engine. That's the entire point.
- sillysaurus2 13y agoFirstly, I want to be clear that I responded specifically to the idea that "MIT license == somehow bad". Releasing code under GPL is not in any way a bad thing, and I'm not arguing against the GPL. People can do whatever they want, and there are a lot of solid reasons to prefer the GPL. My purpose here is to stick up for fellow gamedevs, because it's absurd to believe that we're not interested in contributing to open source just because we prefer the MIT license. I could name several gamedevs off the top of my head who have contributed in a big way to open source software. Interestingly, they all tend to use MIT licenses. Back then would you say "system programmers are not going to ragequit the industry just because operating systems are closed source". But instead, they wrote open operating systems. Follow their example. Write a free engine. That's the entire point. The gamedev industry isn't like other industries. You can't spend a decade writing an engine. You therefore need talent in order to write a competitive non-toy engine. This means you must work in the game industry for a period of time to get that talent. You also need to be brought up steeped in the sort of culture that makes you mentally inclined to open source your years of hard work rather than keeping it closed and proprietary. That's why it's a mistake to villify the MIT license -- you're cutting off an entire generation of programmers from open source culture. Specifically, the generation of programmers who want to be game developers. The reason is because they are going to be working in the gamedev industry, and hence the MIT license is going to be their only option to participate in open source culture. Villifying them will drive them away, and future talent will write proprietary closed-source engines as a result rather than free and open source ones. In summary, villifying the MIT license is directly counterproductive to your philosophical goal of seeing less proprietary software.
- davexunit 13y agoTalk about entitlement. People choose the GPL because they don't want their code used in proprietary software. We don't want to help the proprietary game development industry. We care about user freedom, not programmer freedom.
- eligos 13y agoTell that to the OpenGL comunity
- randomdata 13y agoAs a game player, you're hurting an entire customer base by shutting us out of modifying your software. The primary goal of the GPL is to allow end users the freedom to fully utilize the software that they use, including the ability to extend as they see fit, not for developers to collaborate with each other.
- falcolas 13y agoI'm not a game developer; that industry is welcome to continue on without me, they have done great so far. The fact that some code is licensed with the GPL is in no way detrimental to anybody. If the person who had written the GPL code had instead made the code completely closed source, "game programmers" would have been in a situation that would can only be the same, or worse. They would still have to write their own code, and wouldn't have even the choice of building upon the free software and making it free to everyone else. Open source developers are under no obligation to do your work for you, or to make your life easier. That some choose to do so is fantastic. To expect everyone to give away their code with no form of compensation is silly (even if that compensation is simply paying it forward). And there's always the third option... pay someone for an alternate license to the code. Do you really dig Lighttable, and want to incorporate it in your closed source videogame? Pay the developer enough money that he'll license it to you without any of the GPL clauses.
- sillysaurus2 13y agoYou're preaching to the choir, my friend. I think the GPL is great. I also think the MIT license is great, or at the very least that people who use it shouldn't be vilified. As I mentioned elsewhere, vilifying the MIT license is counterproductive to our mutual goal of seeing less proprietary software. https://news.ycombinator.com/item?id=7026368 https://news.ycombinator.com/item?id=7026368
- shizzy0 13y agoI think that game industry's reliance on the proprietary model is somewhat odd because they could do a really nice code is open source, but the art assets, sounds, etc. are licensed. Let people have and modify the engine, and if they purchased the game, they're free to add or do whatever, but no one can take your assets and resell them legally.
- bad_user 13y agoThat stereotype leads to a paradox, because in many cases: developers == users
- gillianseed 13y agoI'd say this is a strong reason why GPL is the most popular licence as it also benefits developers as they in turn become end users when someone distributes changes made to their code, which then means they have the right to recieve the source code of those modifications made to their code.
- bad_user 13y agoNot with dual-licensing. GPL is perfectly fine. It's a good match for something like LightTable. However companies that practice dual-licensing and that require copyright assignment for contributions do not have to play by the same rules as the third-parties that are contributing and I think this is poisonous. It's a good business strategy of course, however, how many times have you heard of such a company that does profit sharing with the third-parties that contributed code? It's also bad for the company ... if some third-party releases some really good plugin as GPL, without doing copyright assignment, then it means the plugin in question will never be a part of the official distribution, which hurts all parties. This is why I prefer the open core model, in which anybody can build proprietary things on top. For example IntelliJ IDEA Community Edition is licensed with the Apache 2.0 license. Apache 2.0 is IMHO the best open-source license. IntelliJ IDEA Ultimate edition includes all kinds of smarts and JetBrains is doing well - it obviously doesn't hurt them when third-parties release plugins such as this one: http://cursiveclojure.com/ http://cursiveclojure.com/ - it actually helps them, because they don't have the resources to build plugins for everything under the sun. BTW - I'm happy that LightTable was released as open-source. I would have preferred another license, preferably one that is compatible with EPL (that's pervasive in Clojure's ecosystem), but can't complain, it's their right to do as they please.
- gillianseed 13y agoI know x264 (and upcoming x265) uses this method to make money off their open source software, they release it for anyone to use under GPL but also offer licences for those who wants to use it in proprietary projects. AFAIK the money made is shared amongst x264 key contributors, but I have no idea if any money trickles down to less prolific contributors. > if some third-party releases some really good plugin as GPL, without doing copyright assignment, then it means the plugin in question will never be a part of the official distribution, Why not? I don't see why a third-party plugin should be excluded from the official open source distribution? Obviously they can't offer a proprietary licence for it alongside their own code, but it could still be part of the official release. >This is why I prefer the open core model, in which anybody can build proprietary things on top. Hmm... actually I prefer that if someone should make money off proprietary use of open source code, then it should be the authors of that open source code, so personally I prefer the dual-licence mechanism that the x264 devs use. Anyone can use x264 in full open source fashion under GPL, if someone wants to use their work for proprietary means, the x264 developers are compensated for allowing this.
- dragonwriter 13y agoPermissive licenses (or "licenses" like SQLite's Public Domain declaration) like BSD/MIT have lower barriers for use by many organizations, and many of them will contribute back because having a bigger community involved in maintenance benefits them, even without a GPL-shaped gun to their head. That community effect can make BSD/MIT/etc. better for users. The idea that GPL is "best for users" seems to rest on at least one two assumptions, both of which are flawed: 1. No one considers licenses when they select free software, so that someone who would use a piece of software under a permissive license will use it under a GPL-style license (discounting the fact that there are organizations that simply won't touch software with GPL-style terms, that would use it with BSD-style terms), 2. People always and only give back when legally required to do so.
- riquito 13y ago> 2. People always and only give back when legally required to do so. In the world where I live there is also a different kind of people
- andyroid 13y agoThere are lots of communities around GPL licensed software as well, so that's kinda a moot point, no? The assumptions you cite are not the primary reason GPL software is considered "best for users" (by some). The second point is not even relevant for users but developers. GPL software is guaranteed to stay free. That's what's relevant for the user. (Personally I like both kinds of licenses, so I'm not arguing for/against either)
- dragonwriter 13y ago> There are lots of communities around GPL licensed software as well, so that's kinda a moot point, no? No, the point wasn't "only permissively licensed software can have communities" (which would be ridiculous), it was "the fact that many organizations are less receptive to the GPL can result in larger potential contributing communities for permissively-licensed projects". > GPL software is guaranteed to stay free. GPL software is no more guaranteed to stay free than permissively licensed software is. The closest thing to that that is a real difference between GPL and permissively-licensed software is that, assuming no radical change on the part of the FSF (or, alternatively, assuming the "or any later version" option isn't used), GPL software is guarantted to not have legal non-free derivative works not separately licensed by the copyright owner. Which is relevant to the degree of control that the copyright owner can exercise -- and why it is popular for commercial Open Core schemes -- but not particularly relevant, at least in a positive sense, for users.