Slashdot Mirror

> It was mostly marketing I think, free versions of BSD were appearing at the same time but didn't generate excitement for a variety of reasons.

It was more then just marketing -- it a was a difference in Philosophy and how it was applied.

BSD, while "free", didn't provide the guarantee that the code would STAY free like GPL.

My understanding is that Stallman _could_ have used a corresponding WTFPL, Do-What-The-Fuck-You-Want Public License, aka Public Domain, but he was more concerned about companies "hijacking" the free source code and making it proprietary again.

Sometimes you need to restrict freedom in order to maintain it, ironically.

> The hobbiest already has Linux, the gamers are going to consoles it seems,

Aside from console exclusive games, gamers are all over the place.

PC Master Race is alive and well thank-you-very-much -- especially with the high performance demands of 4K, 120 Hz, and VR. Plus certain games such as Starcraft 2 will never be on shitty* consoles.

* Shitty is the technical term for dog-slow performance compared to PC -- they are great games on both PC and Console platforms.

Destiny 2 is rumored to also be coming to Windows.

That said,

* Sony uses FreeBSD for the PS3 and PS4 hypervisor kernel.
* Microsoft uses the Windows kernel the XBox 360 and and XBone.

> and the generic home user is happy with phones, tablets, and netbooks.

On PC, if the Steam Hardware Survey is accurate:

* Windows is ~96% of the market here,
* OSX is holding steady at ~3 %
* Linux usage, while also holding, is still a rounding error, for the most part, at ~0.76%

Mobile space is different:

* Android, with its 2+ Billion devices in 5 years, uses Linux, making WinCE and Windows Phones look like a total joke.
* iOS is also popular.

Sorry, I don't have stats for mobile.

What a coincidence

I'm not sure what your point is. Would you prefer that LibreSSL not acknowledge that OpenSSL found the bugs first? Are you implying that LibreSSL should have found the bugs first? Are you implying that there is no valid reason to prefer LibreSSL to OpenSSL given that LibreSSL clearly isn't perfect?

How about if you just come right out and say what you mean, instead of making me guess?

Looking at the history it's clear that LibreSSL has had fewer issues than OpenSSL, especially of severity "High". This looks to me like the OpenSSL guys are in fact doing some things right, and if I could choose one of the two projects to run on my systems I would choose LibreSSL. But I don't think either project can claim perfection... there were bugs in LibreSSL not in OpenSSL as well as the other way around.

P.S. Maybe you should just switch to using libTomCrypt? I've used it, it works, and the license is entertaining. (Yes, that is the license, yes, it is not a joke, yes, the one lawyer I talked to said it seemed to be a valid license.)

Post a short, general list of rules in several obvious places. Make them reasonable enough to cover most possible user needs but flexible enough to cover things that you haven't thought of yet. Any user who is stupid enough to break the rules by running fork bombs, torrents, mining, hiding stashes of lemur porn or anything else which a child of six could tell you was a bad idea, will have their accounts disabled as soon as they are discovered.

If they have a good excuse for abusing the systems then discuss it with them, suggest alternatives to running rendering jobs on the lab servers and keeping passwords on sticky notes or whatever else it is that they are doing wrong and then restore their access, trusting that they will know better. If you do it right, they may even decide that it is better to ask for permission than forgiveness next time.

If they don't, send a memo to their department head briefly outlining what they did, how it was detected, what action you have taken, and that you won't be reversing this decision until you see a presidential pardon come down from an appropriately high authority. It doesn't matter if they have Really Important Work which needs to be done by the end of the week or not, just cut them off until the proper User Apology and Restoration procedure has been completed.

There you go. This solution is licensed under the WTFPL which is compatible with the Open Source Definition and the Debian Free Software Guidelines so you can use it any way you want. You can even supply your own LART and display it prominently by the door of your office if that helps get the message across.

People often equate open source with GPL so one might also be quick to assume he's talking about developing proprietary software and profiteering off of open source but that is not always the case; GPL often presents itself as a pain for open source developers as well who may want to license their software under an even more liberal license such as BSD, MIT or even the WTFPL and wish not to taint their software with the ideological restrictions and burdens GPL places upon its users.

wtf is wrong with you guys? it has no official medical use before certification and he can't afford it. it has no implied warranty. there's no fucking way to sue 'em if you use it for something, if you want to use it for something go through certification first.

and as far as copyrights go yeah, it DOES have meaning: do what the fuck you want. besides, FSF agrees. it's as free as you can get. what the fuck is wrong with people who think it has no meaning in copyright? because it sure fucking does! why the fuck it wouldn't? because it has "fuck" in there in the name? it gives you explicit permission to do whatever the fuck you want with it.

you don't like it? well fuck, create your own fork and license it under gpl! or bsd! or apache!

(and I can think of a bunch of things more necessary to have warranty disclaimers like any heating system control systems like on every friggin 3d printer which may burn your house down)

http://www.wtfpl.net/about/

No, this is not a troll. And no, I am not. I am just crying out loud what I and many, many colleagues do on a regular basis. Let us look at this coolly. You browse some source on, say, github. By and by, you find a cool way to compute, say, Fibonacci( 1000000000 ), in Takahashi's paper. So you duly quote the paper in your source code, right ? You maybe even name your class TakahashiFibo, or something like that. But now, in order to make it work, you need a fast implementation of ( java ) BigInteger, especially for the "#.add( int )" and "#.multiply( BigInteger )" routines. You find these, somewhere. Dude, who is going to copy the license file for these two subroutines into his project files ? C'mon. You have done it, too. Copy, paste, compile, test, deliver, done. See the WTFPL license if you don't get what I mean.

If you don't want to use a real license, just use the DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE. It's one of the more permissive licenses...