Comments on: Writing WordPress New-BSD Library http://jacobsantos.com/2009/projects/writing-wordpress-new-bsd-library/ Rumblings, rants, essays, stories by Jacob Santos about Web Site Development, Persistent Browser-Based Games, personal journal, and Programming. Mon, 21 May 2012 13:04:07 +0000 hourly 1 http://wordpress.org/?v=3.3-aortic-dissection By: Jacob Santos http://jacobsantos.com/2009/projects/writing-wordpress-new-bsd-library/comment-page-1/#comment-33922 Jacob Santos Tue, 27 Jan 2009 13:07:26 +0000 http://www.santosj.name/?p=881#comment-33922 True, their arguments aren't correct, however it is difficult for commercial entities because they are used to having protection against people redistributing their software. I could care less about their arguments. The point is that, if someone wants to use a library, where they want to be completely legal with their claim against someone redistributing their software, then they should have to pay for said library, either from me or time and money spent writing it themselves. I'm not writing it to make money, but if I profit from one or two people trying to get around GPL, then I'm fine with that. I actually plan on using the library for another project that I didn't want to commit to something that uses PHP4 code. I don't want anything resembling PHP4 in my project, but I really liked the way WordPress table structure is. So I figure I can write the articles in WordPress and then use the library to display the articles. I'm also going to shoot for something that is optimized for opcode caching for performance (premature, perhaps, but tried and true method). It will be fun as hell to code the library and until it stops being fun, I will continue it. It is also doubtful anyone will actually use the library, so I'm doing it for me. Coding for PHP 5.3 is also awesome, I might have cried one or two times (not for joy, but WTF moments when using namespaces). That said, it is fun coding on a platform that no one is going to be using for years. True, their arguments aren’t correct, however it is difficult for commercial entities because they are used to having protection against people redistributing their software. I could care less about their arguments. The point is that, if someone wants to use a library, where they want to be completely legal with their claim against someone redistributing their software, then they should have to pay for said library, either from me or time and money spent writing it themselves. I’m not writing it to make money, but if I profit from one or two people trying to get around GPL, then I’m fine with that.

I actually plan on using the library for another project that I didn’t want to commit to something that uses PHP4 code. I don’t want anything resembling PHP4 in my project, but I really liked the way WordPress table structure is. So I figure I can write the articles in WordPress and then use the library to display the articles. I’m also going to shoot for something that is optimized for opcode caching for performance (premature, perhaps, but tried and true method).

It will be fun as hell to code the library and until it stops being fun, I will continue it. It is also doubtful anyone will actually use the library, so I’m doing it for me. Coding for PHP 5.3 is also awesome, I might have cried one or two times (not for joy, but WTF moments when using namespaces). That said, it is fun coding on a platform that no one is going to be using for years.

]]> By: Matt http://jacobsantos.com/2009/projects/writing-wordpress-new-bsd-library/comment-page-1/#comment-33917 Matt Tue, 27 Jan 2009 07:35:15 +0000 http://www.santosj.name/?p=881#comment-33917 Just because people complain or are loud doesn't mean they're right. Just because people complain or are loud doesn’t mean they’re right.

]]>