Thanks to the EU, it's now an alliance with internal tradiing advantages and collective leadership. In English, we call this a confederacy (no necessary relation to the Confederate States of America).
More like the Articles of Confederation, yes? I wonder how long it'll take them to end up like us...
Think before you code. What are you doing? Why are you doing it? What rules are likely to change? What data structures best represent what whatever you're coding is/does?
Get familiar with data structures. What is a pointer? What is the difference between pass-by-value and pass-by-reference? What is a dictionary/map/associative array/indexed table? What's the difference between is-a and has-a? What is big-O notation?
Learn to map your assignments to data structures and algorithms, independent of your programming language. Then translate that into the language; if it doesn't translate cleanly, figure out why it doesn't translate, and try a different structure/algorithm. Being familiar with your language will help here, as it will be easier to see immediately what maps to the language well, or even when a somewhat suboptimal design (say, XML) may allow massively simpler code due to standard library support. Being somewhat familiar with other (completely different, say Ocaml vs. C) languages will help you see more alternatives that you can choose from.
If your application uses SQL to talk to a database (as opposed to being forced thru some abstraction layer), learn SQL beyond the minimum required. Pushing certain logic into the queries (with proper indexes) can be a massive speedup, pushing the wrong logic will cause problems. This is on the same order as choosing the right algorithm based on it's big-O speed, rather than silly little things like loop unrolling and hand-coding replacements for too-slow library functions.
The BSD license is from UC Berkeley, the MIT license is of course from MIT, llvm is from the University of Illinois / NCSA and uses a license almost identical to the BSD license, etc. For some reason, this sort of "free as in knowledge" type license seems to be rather popular among educational institutions.
My supervisor insists there should be a citation clause, requiring any published article that uses results of the software to cite our paper.
That is a restriction on how it can be used, and I seriously doubt it is at all compatible with Open Source. It certainly wouldn't be compatible with Free-as-in-FSF software.
Wait, so university is about credits and not about *learning*!?
I think it's more about verified learning. When they give you course credits or a degree, they're saying "we know that Anonymous Coward is at least somewhat competent at X". And while knowledge may be free, verifying someone's level of knowledge takes work (if done right), and is rather expensive (partly because they can, partly because they need money just like everyone else).
Mutation is a difficult thing to wrap your head around when you are starting out; functional programming is much easier when you have no other exposure to programming.
Sure, if you grew up with only pens, and no pencils/erasers or etch-a-sketch or MS Paint or legos or...
My current routers assign private IP addresses to my computers at home. My understanding is that with IPv6 this would not be allowed and that my router would have to assign real IPs.
NAT for IPv6 was implemented in Linux in 2004, so it's clearly possible. How would someone go about making it "not allowed"?
Moving to IPv6 means that I can't use NAT anymore for my home network.
I don't believe that's accurate. What's supposed to happen is that your ISP gives you a/64 block and you don't need NAT, but nothing says you can't use NAT if you want to (or if your ISP doesn't play nice).
This isn't hardware they licensed, it is in-house designed stuff. Are you trying to tell me that they built chips, yet have no documentation on pinouts, low-level register settings or functional hardware blocks? Exactly what did their in-house software team use to develop the reference drivers?
Hasn't MicroSoft had trouble complying with the EU rulings partly because they didn't have any real documentation, they could just look at the code when they needed to know something? I'd imagine the same situation would be possible here, although probably less likely unless everyone knows both C and VHDL/Verilog.
I fail to see how embedding such a scale in the protocol would help, and it's not unlikely that it would hurt the situation.
The idea here seems to be more of a "FooOrg TruthRank" that you could subcribe to, "He went on to say that he didn't think "a simple number like an IQ rating" is a good idea: "I'd be interested in different organisations labelling websites in different ways".". Isn't there a browser toolbar that will show the google pagerank of pages you visit? I think the idea is something like that.
Is it me or is all this legal crap on slashdot really f*cking boring?
What happened to "News for nerds stuff that matters"?:-/
It's turning into "News for lawyers, stuff no one gives a sh*t about..."
It can be rather useful to know that you can't link this library to that program and distribute the result. It can also be useful to know that if you cheese of the FSF they'll change their licenses to make their (future) code unusable in whatever field your products are in.
I was also a bit scared by the time I was done with it all. Lindberg cites not only the pitfalls that are out there, but backs it up with case history that illustrates his points.
I know case studies are important, but it would be nice to see more statisical evidence of the impact of bad IP policy in addition to anecdotal.
I don't think it's that kind of book. That would be more for a "what's good, what needs fixing" report, this book sounds more like "this is how things are, and this is how to deal with it".
Why? Anyone serious already knows, and trying to focus discussions doesn't seem to work here. Instead of keeping the discussion around whichever of what is / what should be the story is about, you'd probably just end up with more meta-arguments.
There is a general discussion that covers a wide array of licenses, and then a separate chapter just for working with the GPL.
[...] a list of the licenses used with Fedora on a grid that lists GPL compatibility, the full text for a number of licenses and a very nice GPL Compatibility Matrix. That matrix shows what versions of *GPL licenses can be used with one another from the perspective of adding code to an already licensed project or licensing a project that will include code already licensed under one of the *GPL licenses.
Wow, GPL by itself is as complicated and hard to explain as all other licenses put together?
When has this EVER been the case? Back in the days of the reel/reel tape drive?
Normal magnets could probably mess up a floppy disc. Also, really old computers supposedly used little magnets strung on a grid of wires as their RAM, perhaps getting other magnets too close would break this (not that anyone would be allowed to open the cabinet unsupervised...)?
Yeah, I can see the government not being particularly forgiving if that chunk of data on your harddrive happens to have childporn or something on it.
"No, really your honor, it wasn't my data. I was just sharing storage space with people online." Is not going to fly in court.
Even if you can point to the company's website "see, I was using this, ask them if I had any way to know what they put on my computer"? Especially since they must have some sort of index saying what they stored where, so you could ask for the relevant part of that.
The real issue isn't what would work in court, but what the media or HR people would do even without a conviction.
Slashdot Mirror
Being considered innocent until proven guilty is not a positive right it is a negative right.
But it is positive (good) news, right?
Thanks to the EU, it's now an alliance with internal tradiing advantages and collective leadership. In English, we call this a confederacy (no necessary relation to the Confederate States of America).
More like the Articles of Confederation, yes? I wonder how long it'll take them to end up like us...
It's not news about positive rights, it's positive news about rights.
Think before you code. What are you doing? Why are you doing it? What rules are likely to change? What data structures best represent what whatever you're coding is/does?
Get familiar with data structures. What is a pointer? What is the difference between pass-by-value and pass-by-reference? What is a dictionary/map/associative array/indexed table? What's the difference between is-a and has-a? What is big-O notation?
Learn to map your assignments to data structures and algorithms, independent of your programming language. Then translate that into the language; if it doesn't translate cleanly, figure out why it doesn't translate, and try a different structure/algorithm. Being familiar with your language will help here, as it will be easier to see immediately what maps to the language well, or even when a somewhat suboptimal design (say, XML) may allow massively simpler code due to standard library support. Being somewhat familiar with other (completely different, say Ocaml vs. C) languages will help you see more alternatives that you can choose from.
If your application uses SQL to talk to a database (as opposed to being forced thru some abstraction layer), learn SQL beyond the minimum required. Pushing certain logic into the queries (with proper indexes) can be a massive speedup, pushing the wrong logic will cause problems. This is on the same order as choosing the right algorithm based on it's big-O speed, rather than silly little things like loop unrolling and hand-coding replacements for too-slow library functions.
FBI agents want to do things that the FBI has been traditionally known for ( drugs, armed robbery, kidnapping, terrorism).
...I thought that was the CIA?
The BSD license is from UC Berkeley, the MIT license is of course from MIT, llvm is from the University of Illinois / NCSA and uses a license almost identical to the BSD license, etc. For some reason, this sort of "free as in knowledge" type license seems to be rather popular among educational institutions.
My supervisor insists there should be a citation clause, requiring any published article that uses results of the software to cite our paper.
That is a restriction on how it can be used, and I seriously doubt it is at all compatible with Open Source. It certainly wouldn't be compatible with Free-as-in-FSF software.
Wait, so university is about credits and not about *learning*!?
I think it's more about verified learning. When they give you course credits or a degree, they're saying "we know that Anonymous Coward is at least somewhat competent at X". And while knowledge may be free, verifying someone's level of knowledge takes work (if done right), and is rather expensive (partly because they can, partly because they need money just like everyone else).
Mutation is a difficult thing to wrap your head around when you are starting out; functional programming is much easier when you have no other exposure to programming.
Sure, if you grew up with only pens, and no pencils/erasers or etch-a-sketch or MS Paint or legos or ...
Yes, it's in the floppy drive.
[Warning: use IE to open, not firefox]
It seems to work just fine in Iceweasel (3.0.1, maybe old versions are broken?).
But everyone knows that the Sun and the planets orbit the earth.
Perhaps it's that that star isn't "sun-like"?
NAT for IPv6 was implemented in Linux in 2004, so it's clearly possible
Based on this message, but from further looking it appears that it was never merged.
My current routers assign private IP addresses to my computers at home. My understanding is that with IPv6 this would not be allowed and that my router would have to assign real IPs.
NAT for IPv6 was implemented in Linux in 2004, so it's clearly possible. How would someone go about making it "not allowed"?
Moving to IPv6 means that I can't use NAT anymore for my home network.
I don't believe that's accurate. What's supposed to happen is that your ISP gives you a /64 block and you don't need NAT, but nothing says you can't use NAT if you want to (or if your ISP doesn't play nice).
This isn't hardware they licensed, it is in-house designed stuff. Are you trying to tell me that they built chips, yet have no documentation on pinouts, low-level register settings or functional hardware blocks? Exactly what did their in-house software team use to develop the reference drivers?
Hasn't MicroSoft had trouble complying with the EU rulings partly because they didn't have any real documentation, they could just look at the code when they needed to know something? I'd imagine the same situation would be possible here, although probably less likely unless everyone knows both C and VHDL/Verilog.
I fail to see how embedding such a scale in the protocol would help, and it's not unlikely that it would hurt the situation.
The idea here seems to be more of a "FooOrg TruthRank" that you could subcribe to, "He went on to say that he didn't think "a simple number like an IQ rating" is a good idea: "I'd be interested in different organisations labelling websites in different ways".". Isn't there a browser toolbar that will show the google pagerank of pages you visit? I think the idea is something like that.
What about university real estate?
Is it me or is all this legal crap on slashdot really f*cking boring?
What happened to "News for nerds stuff that matters"? :-/
It's turning into "News for lawyers, stuff no one gives a sh*t about..."
It can be rather useful to know that you can't link this library to that program and distribute the result. It can also be useful to know that if you cheese of the FSF they'll change their licenses to make their (future) code unusable in whatever field your products are in.
I was also a bit scared by the time I was done with it all. Lindberg cites not only the pitfalls that are out there, but backs it up with case history that illustrates his points.
I know case studies are important, but it would be nice to see more statisical evidence of the impact of bad IP policy in addition to anecdotal.
I don't think it's that kind of book. That would be more for a "what's good, what needs fixing" report, this book sounds more like "this is how things are, and this is how to deal with it".
Why? Anyone serious already knows, and trying to focus discussions doesn't seem to work here. Instead of keeping the discussion around whichever of what is / what should be the story is about, you'd probably just end up with more meta-arguments.
There is a general discussion that covers a wide array of licenses, and then a separate chapter just for working with the GPL.
[...] a list of the licenses used with Fedora on a grid that lists GPL compatibility, the full text for a number of licenses and a very nice GPL Compatibility Matrix. That matrix shows what versions of *GPL licenses can be used with one another from the perspective of adding code to an already licensed project or licensing a project that will include code already licensed under one of the *GPL licenses.
Wow, GPL by itself is as complicated and hard to explain as all other licenses put together?
When has this EVER been the case? Back in the days of the reel/reel tape drive?
Normal magnets could probably mess up a floppy disc. Also, really old computers supposedly used little magnets strung on a grid of wires as their RAM, perhaps getting other magnets too close would break this (not that anyone would be allowed to open the cabinet unsupervised...)?
Um, yeah, that was kind of my point.
Yeah, I can see the government not being particularly forgiving if that chunk of data on your harddrive happens to have childporn or something on it. "No, really your honor, it wasn't my data. I was just sharing storage space with people online." Is not going to fly in court.
Even if you can point to the company's website "see, I was using this, ask them if I had any way to know what they put on my computer"? Especially since they must have some sort of index saying what they stored where, so you could ask for the relevant part of that.
The real issue isn't what would work in court, but what the media or HR people would do even without a conviction.