gillianseed

15 ms·

91.
by gillianseed 12y ago
I made a swedish to english translation of the actual allegation (as in the actual case file), the original can be found here, naturally it's in swedish: http://www.magasinetparagraf.se/bilden/forundersokningen-avs
92.
by gillianseed 12y ago
Heh, hej Ludde!
93.
by gillianseed 12y ago
Because Bittorrent inc bought it for (I assume) a decent sum of money and now they are desperately from the looks of it, trying to recoup on their investment. From an end user perspective it sucks, but like others have mentioned there are l
94.
by gillianseed 12y ago
A bit of background on µTorrent, it was written by a guy named Ludvig Strigeus (creator of well-known FOSS projects like OpenTTD and ScummVM), and was free albeit proprietary, with no adware/spyware but simply a lean (in resources) yet
95.
by gillianseed 12y ago
Go is also supported in GCC, as GccGo.
96.
by gillianseed 12y ago
>For one I'm pretty sure it would wreck binary compatibility with BeOS without the addition of a compatibility layer. There's already 64-bit Haiku binaries which can be used alongside the old BeOS binaries so I doubt that this
97.
by gillianseed 12y ago
Why would relying on an existing kernel (linux, bsd) 'nuke' the point of Haiku ? The API's (kits) would not have to change in any way, which is the part that application developers face, and from a user perspective the only d
98.
by gillianseed 12y ago
It seems it was just someone trolling, no code has surfaced at all. Still the discussion it generated was interesting.
99.
by gillianseed 12y ago
Eh? Unless storage becomes enormously cheaper I don't see that having a chance of happening. The key to lossy compression is that you can have huge file size savings while not causing visible degradation (visible here being the human e
100.
by gillianseed 12y ago
Actually, the Arch devs said that if anyone stepped up and maintained the sysv scripts it would continue to be officially supported, no one did, and that was that.
101.
by gillianseed 12y ago
Whether you find it likely or unlikely to happen is not part of the equation, copyleft was created to _ensure_ as far as possible that the end user would have certain rights. >The ability to develop plugins for GCC has existed for years
102.
by gillianseed 12y ago
>In the world RMS wants, Apple would not have the right to develop Swift and make it proprietary. In the world RMS wants, people would shun proprietary software due to it not giving them the rights which are afforded to them through copy
103.
by gillianseed 12y ago
egcs was free software working exactly as it should, you don't like the current direction, fork it, and thanks to it being copyleft the fork is entirely open and can later be merged back or as in this case, become the new official proj
104.
by gillianseed 12y ago
I don't see any change in the licensing landscape at all, permissive licensing remains king for libraries, frameworks, while copyleft remains king for 'full end product' style projects. Some people seem to take the upswing of
105.
by gillianseed 12y ago
>out of fear of a closed-source boogyman which doesn't exist any more, thanks to clang (if it ever did). Eh, what ? Apple is already shipping their proprietary fork of Clang which supports their proprietary language Swift, this is e
106.
by gillianseed 12y ago
True, one thing though is that the Bittorrent protocol favours a 'tit for tat' type data exchange between peers unlike say, Emule which uses a queue system with a slight bonus for people who has given you data, this is in my view
107.
by gillianseed 12y ago
>Except Java and C# are significantly better at all of these points except for boilerplate, which I would even dispute whether that is a bad thing overall. C# on Mono certainly isn't significantly better performing than Go from my e
108.
by gillianseed 12y ago
Sure, but the whole point behind x265 is to provide better quality per bit than x264.
109.
by gillianseed 12y ago
>It's good for bitrate starved files, but x264 is actually still more efficient for transparent encodes. x265 currently can't handle noise very well. Yes this is my impression as well from the tests I've made. >x265 is
110.
by gillianseed 12y ago
I've never had any audio sync problems with Handbrake, then again I've never done anything 'exotic' (basically encode my dvd's to x264+audio passthrough) and everything has worked fine.
111.
by gillianseed 12y ago
>It seems overly defensive. Based upon this one instance where he shows up and correct misgivings ? Seriously ? If anything you come across annoyed that your uninformed ranting was corrected.
112.
by gillianseed 12y ago
>I have to ask, though - why engage in a thread like this? Does he need an excuse for wanting to correct misinformation ?
113.
by gillianseed 12y ago
>and just in general I favor the BSD/MIT/ISC licenses to the GPL. Curious then as to your choice of licensing your Higan/BSnes emulators under GPLv3.
114.
by gillianseed 12y ago
Which is a drop in the ocean as far as the FOSS app ecosystem go, and to be honest after all this time I can't see either of GTK or Qt winning the 'toolkit war'. If either of those would have the capacity to emerge as the de
115.
by gillianseed 12y ago
>I picked the 32 bit version of the benchmarks, since the demo program didn't need multiple GB worth of memory, FWIW. More addressable memory is but one advantage of 64-bit versus 32-bit, the fact that it has double the amount of re
116.
by gillianseed 12y ago
Why only compare based upon one of the benchmarks (binary-trees), and also why choose 32-bit which the most unlikely architecture this would run on as I see it ? Here's java compared to go on all benchmarks, 64-bit: quad-core: http:&#
117.
by gillianseed 12y ago
Well there are likely lots of potential markets where a prerequisite of allowing the end user to swap out LGPL libraries won't be accepted (sadly), not only Apple but the consoles as well, so from that perspective Unity needs to buy a
118.
by gillianseed 12y ago
>Unity has negotiated a license with Novell. Now they would have to do it again with Xamarin for the newer version of Mono. Ah, so the deal was before Xamarin bought the rights to Mono from Attachmate/Novell, I didn't know that
119.
by gillianseed 12y ago
>We only require licensing for uses of Mono and Moonlight on embedded systems, or systems where you are unable to fulfill the obligations of the GNU LGPL. In other words, you have to pay a license fee for shipping the Mono runtime in a p
120.
by gillianseed 12y ago
>The general perception... Based upon what anecdotal evidence is that the 'general perception' ? And furthermore how on earth would he be able to 'push this software' just because he works at Red Hat ?

More ›