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

 



Forgot your password?
typodupeerror
×
Programming

Submission + - 'The Code Has Already Been Written'

theodp writes: John D. Cook points out there's a major divide between the way scientists and programmers view the software they write. Scientists see their software as a kind of exoskeleton, an extension of themselves. Programmers, on the other hand, see their software as something they will hand over to someone else, more like building a robot. To a scientist, the software soup's done when they get what they want out of it, while professional programmers give more thought to reproducibility, maintainability, and correctness. So what happens when the twain meet? 'The real tension,' says Cook, 'comes when a piece of research software is suddenly expected to be ready for production. The scientist will say 'the code has already been written' and can't imagine it would take much work, if any, to prepare the software for its new responsibilities. They don't understand how hard it is for an engineer to turn an exoskeleton into a self-sufficient robot.'

Comment Re:There is a much bigger problem than "0" and "O" (Score 1) 100

Thank you, I now understand where the problem is. Still, I'm not so sure this would be so easy to fix.

They could have given permission to distribute a document without restriction when the fonts are embedded in it, and everything would have been OK.

What if I want to distribute a document containing the embedded fonts while imposing some restrictions on the document itself? Would I be able to do that if you only give me permissions to distribute the document without restriction? But maybe I'm mixing up without restriction and without restrictions :)

In the end, you are right, this is indeed a perfect example why it should be the lawyers who do the wording of licenses.

Comment Re:There is a much bigger problem than "0" and "O" (Score 1) 100

The license only says that the license "does not apply to any document created using the Font Software", not that the license does not apply *at all* once the font is embedded.

A little clarification, it's not the license that does not apply to documents created with the font, but the requirement that the font can only be distributed under the same license. Here is the precise text about this exception:

5) The Font Software, modified or unmodified, in part or in whole, must be distributed entirely under this license, and must not be distributed under any other license. The requirement for fonts to remain under this license does not apply to any document created using the Font Software.

Comment Re:There is a much bigger problem than "0" and "O" (Score 1) 100

The problem in this case is that the license allows conversion of the font to any other license or public domain once it is embedded in a document. The license explicitly says that it no longer applies once the font's embedded. And the authors didn't realize that if you extract the font from the document, the license doesn't come back!

I find your interpretation of the license quite strange (but, well, I am not a lawyer). The license only says that the license "does not apply to any document created using the Font Software", not that the license does not apply *at all* once the font is embedded. If you extract a font out of the document, I suppose you obtain a copy of the original font, or at least a modified version of the original font, and the license does explicitly cover copies and modified versions. I would expect this holds for any copy or modified version, no matter by which process they were obtained.

I think that for free font licenses allowing the fonts to be embedded without posing restrictions on the license of the document is of paramount importance. Do you know any other font license that allows this form of embedding and is for sure lawyer-proof?

Comment Re:Slow news day... (Score 1) 100

I'm very happy they pulled it through in the end! I also agree that this is a very significant contribution to open source, and we must be grateful to the people who designed these fonts. I'm also very happy that in the end they chose an OSI-approved license, which will allow this font to be part of all Linux distributions. At the same time, it's hard not to notice not only the "schedule slippage" of 10 years or so, but also the fact that although they clearly had no clue how long this was going to take, they were always giving people false hope, by making very precise (but completely, completely off) "estimations" about when the project was going to be finished. By doing so, they just made idiots out of themselves, and gave the impression that the whole project is just vaporware. Should they have refrained from making such stupid predictions, and just informed the public about the progress they are making, there would be a lot less people feeling (rightfully!) deceived. And do you think whoever manages this project has learned anything out of this? I don't think so! They are already giving "estimations" about when versions 1.1 and 1.2 will be out. Why on earth do they insist in trying to deceive everyone with their "estimations"? They already showed how terrible they are at estimating how long their work takes.
Microsoft

Journal Journal: MS copies feature, then patents it

Michael Kölling, a senior lecturer at the University of Kent and one of the developers of BlueJ, an educational development environment, realized last year that Microsoft had copied one of the BlueJ features into Visual Studio. Flattery, right? Well, recently he was informed that Microsoft has filed a patent describing the very same feature.

Michael's blog entry describing this here

Slashdot Top Deals

Their idea of an offer you can't refuse is an offer... and you'd better not refuse.

Working...