44 ms·
As someone who works on BSD-licensed opensource software, this is fantastic news. Regardless of your opinion of Sony as a company, this is exactly why I love li
by josephg 13y ago
As someone who works on BSD-licensed opensource software, this is fantastic news. Regardless of your opinion of Sony as a company, this is exactly why I love licenses like BSD & MIT - you enable engineers everywhere to build better products.
- zimbatm 13y agoIt would be interesting to know what made them choose that OS. Is it because FreeBSD was better adapted to their needs or because unlike Linux they wouldn't be forced to contribute back to the enormous pile of work that they inherit ? I hope it's the first one and that we'll soon see commits from Sony flowing in.
- ceph_ 13y agoFreeBSD and Netbsd are often chosen due to the more permissive licensing agreements. They allow the revised platform to be fully commercial and proprietary. Another example would be Juniper's JunOS.
- pbsdp 13y agoWhat's interesting is that while Juniper's software is proprietary, they've still contributed patches and funded dedicated upstream development. This is something enabled by not being required to share more than what they're comfortable with sharing.
- cperciva 13y agoNot just Juniper, either. Most large users of FreeBSD contribute patches back -- the great success of BSD as a license is the recognition that if you use open source, it makes sense to contribute back any non-proprietary improvements, without needing any "encouragement" from the license.
- runeks 13y ago> Most large users of FreeBSD contribute patches back -- the great success of BSD as a license is the recognition that if you use open source, it makes sense to contribute back any non-proprietary improvements, without needing any "encouragement" from the license. I've had the same thoughts recently. At some point it must simply become unmanageable to maintain a fork, at least if you want to enjoy updates to master. But I suspect Sony might not be interested in future updates to FreeBSD, since they will probably prefer working on a static platform, and since the hardware will remain the same as well.
- cperciva 13y agoTwo answers come to mind about that. First, according to wikipedia, the PS4 has been in development since 2008 -- long before FreeBSD 9.0 was released -- so the "enjoy updates to master" argument would have applied during the development cycle even if not after the product is released. Second, even if they're dealing with a mostly static platform, I'm sure there would be some changes -- in hardware, replacing components with newer/cheaper ones, and in software, patching security vulnerabilities -- so there would still be some incentive to make merging easy (although not as much as if they were continuing development, to be sure). Of course, for all I know, they might be planning a PlayStation 5 based on FreeBSD 11.0 to be launched in 2017, in which case they would have very good reasons to merge as much non-proprietary work upstream.
- devcpp 13y agoThe even greater success of GPL as a license is that it not only makes sense to contribue back, but you have to. This is much more efficient for good contributions flowing from everywhere. The fact that good non-GPL alternatives like BSD exist kind of destroys it though.
- testbro 13y agoI'd wager that there are a lot of in-house re-implementations of GPL software because the license isn't permissive enough. I think the fact that good non-GPL alternatives exist supports my hypothesis; given the choice between GPL and reinvent the wheel, it's feasible for someone to take the latter path.
- lambda 13y agoSure, but there are lots more companies that have contributed patches and funded dedicated upstream development for the Linux kernel, in part because they knew that their competitors couldn't just take it and release a proprietary product built on top of it without revealing their changes. As a developer who works with a boss who has a somewhat equivocal position on open source software, I'm glad for the GPL requirements on the software that we modify and ship. He likes to use open source software, and in theory likes to pay lip-service to contributing change upstream, but when push comes to shove he's always worried that we'll let competitors get a jump on us. With GPL licensed software, I can always make the argument that we have to release the source code anyhow, so we might as well push the changes upstream and avoid the pain of maintaining a fork. With other software, well, it's always somewhere far down on the priority stack to actually release the code, and so we wind up maintaining patch stacks for years and shipping with major security vulnerabilities because we're afraid to update as it will take a lot of work to port our changes forward.
- profquail 13y agoYou're giving two entirely separate reasons for why it makes sense for you to contribute patches upstream: * You're modifying GPL'd software, which means you're required to release the source code including your modifications. * Pushing the patches upstream reduces the costs to your business in the long-term, because it avoids the need to maintain separate branches for your own changes. IMO, the second reason is a much bigger win for businesses, and exactly the reason permissive licenses (BSD, Apache 2.0) are getting more and more popular. Permissive licenses allow businesses to collaborate on code which is going to be common within and across industries (reducing development costs and time-to-market) while allowing them to keep some other parts of their code private.
- fabjan 13y agoCompanies using GPLed software also don't have to share more than they're comfortable with sharing, or they would not be doing it. They are just comfortable with a bit more than other companies.
- skreuzer 13y agoNot sure if the license is the reason they choose FreeBSD, but they have made some contributions back to FreeBSD A patch for AVX support was submitted from someone at Sony http://lists.freebsd.org/pipermail/freebsd-amd64/2011-March/013740.html http://lists.freebsd.org/pipermail/freebsd-amd64/2011-March/...
- zvrba 13y agoI don't think it has anything to do with the will to contribute something back. You need a lawyer to do anything with GPL'd software in commercial setting, and even lawyers will sometimes disagree (e.g., what is a derivative work?). With BSD-licensed software you don't have to worry about lawyers. So which software do you pick?
- 4ad 13y agoEveryone talks about licensing but nobody talks about technology. DTrace is something you'd want on such a device. We know that Sony is interested in DTrace, they ported to the PSP a few years back.
- mwcampbell 13y agoThe absence of DTrace in Linux is ultimately a licensing issue, because the CDDL and the GPL version 2 are incompatible.
- th0br0 13y agoFor Linux, there's actually SystemTap which has some features than DTrace according to [1]. Sadly, I believe it's only on Fedora/RHEL/CentOS currently. [1] http://sourceware.org/systemtap/wiki/SystemtapDtraceComparison http://sourceware.org/systemtap/wiki/SystemtapDtraceComparis...
- bingaling 13y agoAlso perf can do some interesting dynamic tracing on linux. This talk (by one of the dtrace guys) discusses methods of linux performance analysis: https://www.joyent.com/blog/linux-performance-analysis-and-tools-brendan-gregg-s-talk-at-scale-11x https://www.joyent.com/blog/linux-performance-analysis-and-t...
- profquail 13y agoSpeaking of which -- for those of you who haven't ever seen or used DTrace, I stumbled across a fantastic little tutorial yesterday which really opened my eyes as to just how useful DTrace can be for developers: http://www.freebsdonline.com/content/view/933/531/ http://www.freebsdonline.com/content/view/933/531/ I also found a well-written quick-start guide for DTrace: http://www.tablespace.net/quicksheet/dtrace-quickstart.html http://www.tablespace.net/quicksheet/dtrace-quickstart.html Remember, DTrace also ships as part of OS X (and Solaris) too, so it's worth learning if you're doing any serious development on those platforms.
- brvs 13y agoI prefer to use proprietary and closed-source software. But to each his own, I guess.
- devcpp 13y agoSo you don't care about backdoors, malware, who knows whatever else they may put in that code?
- brvs 13y agoI would care if they were present. But I have no positive evidence that my computer is infected by any of that. I don't need to manually scan through C code to feel safe. Just like I don't have to watch my food being prepared to be sure it isn't being poisoned.
- protomyth 13y agoAlthough not agreeing with the GP, OpenVMS is closed source and has a pretty good record on security. Closed doesn't necessarily mean less secure.
- guard-of-terra 13y agoDo you prefer to write it all from scratch? Because you can't materialize a new closed-source operating system in time for a console lifecycle without basing it upon some open source one. So you don't have much choice: it's Microsoft or open source, and guess what? Microsoft already have a console of its own.