3 ms·
And lets not forget he's also unwilling to help people out by uploading his OpenGL wrapper to github (or by extension any revision control system). http://www.
by retrogradeorbit 14y ago
And lets not forget he's also unwilling to help people out by uploading his OpenGL wrapper to github (or by extension any revision control system).
http://www.jwz.org/blog/2012/06/i-have-ported-xscreensaver-to-the-iphone/#comment-106782 http://www.jwz.org/blog/2012/06/i-have-ported-xscreensaver-t...
- cma 14y agothe exact same criticism applies to you. why haven't you posted it to github yet?
- retrogradeorbit 14y agoCause I don't care one bit. Unlike jwz who seems to care a hell of a lot.
- bzbarsky 14y agoThe source is available in http://www.jwz.org/xscreensaver/xscreensaver-5.16.tar.gz http://www.jwz.org/xscreensaver/xscreensaver-5.16.tar.gz and he mentions that in his blog post. How much more help are you expecting him to provide? Why would it be any more "helpful" for him to put it in some revision control system instead of just posting the source?
- retrogradeorbit 14y agoI meant the OpenGL wrapper part, not the entire xscreensaver code base. It's kind of hard to fork a tarball.
- gioele 14y agoThat is exactly what mercurial users say about code distributed on github. :) Please respect the author's right to decide how to distribute his code.
- bzbarsky 14y agoHow hard is it to untar, take the header and do whatever you want with it (including putting it on github if you want)? It's definitely a lower barrier to entry than requiring people to create a github account! Edit: the point being, that it's not just "in the tarball": it's in a specific header file, and the blog post says which exact header file you want.