Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror
×

Comment Re:Tivoization (Score 1) 117

RHEL is not dual licensed and Red Hat makes quite a lot of money on it by selling services around it. They even sell self supported versions where all you get is the software, but having a trusted party make the binaries for you can also be seen as a service.

Comment Re:What about OSS license that respects other righ (Score 1) 117

I'm on board with OSS. But I don't think it goes far enough. The right to modify the code you run is a good one. But I am calling for OSS licenses to pick up another clause, the Zero-Kill clause, where in using the software in any weapons platform (be it sniper rifles or predator drones) is forbidden. People should have the right to not fear being killed by open source software.

Additionally, I am calling for another clause to protect human rights. People should be free from fear that OSS will be used to restrict their freedoms in other ways. This includes forbidding use of the software for censorship or oppression.

Both of those clauses would be incompatible with the definition of open source, especially regarding no discrimination against fields of endeavor. You're of course free to create and use such license, but keep in mind that it won't be considered open source and that a lot of people won't be able to use it.

Comment C++ without the C (Score 4, Interesting) 427

Apple recently introduced a language they call Swift or Objective-C without the C. It is technically a completely different language from Objective-C though. When C++ started out it had the major benefit that it was (mostly) compatible with C which at the time was immensely popular, making it trivial to mix new C++ code with existing C code. Today C is still a popular language but not as widely used as it once was. Assuming that C++ could drop C compatibility, how would you take that opportunity to improve C++?

Comment Re:The product owner and legal review? (Score 1) 57

Not sure why this is considered FUD. The thing about any DVCS is that once it is in the repo it stays in the repo.

That's true for non-DVCS too. If it's out, it's out. Doesn't matter if you distributed tarballs or Visual SourceSafe. If it's out, it out.

You have to be very careful about what is put out there in public. Given that this is git, though, I am not sure why the company does not use two repos. A private one for internal development, and a public one which has the merges from the private repo once a point in the graph clears any potential legal issues. This feature is one of the great strengths about git and github.

Well, it's going to have a social impact. There won't be much collaboration when all the company does publicly is basically code dumps.

Slashdot Top Deals

What the gods would destroy they first submit to an IEEE standards committee.

Working...