Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror
Check out the new SourceForge HTML5 internet speed test! No Flash necessary and runs on all devices. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. ×

Comment Re:Weak/nonexistent punishments for faulty notices (Score 1) 79

All patent applications are signed under penalty of perjury. However, the US Patent and Trademark office disbanded its enforcement department in 1974. So, you can perjure yourself on a patent application with impunity.

Unless it's testimony in a criminal case, or the perjury trap in front of a grand jury, or something they want to prosecute like lying on your tax form, the Federal government is in general lassiez faire about perjury, or even encouraging of it with their reluctance to prosecute, especially perjury committed by a so-called intellectual property holder.

Comment Re:Will it work in a Raspberry Pi? (Score 1) 48

It will work in a Raspberry Pi, but the Pi doesn't have the required contacts to support UHS-II, so it won't benefit from the extra bus bandwidth. And it doesn't even support UHS-I fully (max speed is 100 MHz instead of 200 MHz) because you apparently can't put the SoC into 1.8V signalling mode (or so I've read). So you'll presumably benefit from improvements to random access time from the faster microcontroller on the SD card, but you won't get the full speed benefit.

Comment Re:TechBros are the worst Consumers (Score 1) 126

The challenge, of course, is defining what "deprive others of that freedom" means. Does it mean you can't deprive other people of the freedom to have the source code to your work that extends the original work, or does it mean you can't deprive other people of the freedom to make private extensions to the original work? That's fundamentally the difference between the GPL and BSD licensees is what other group of people you want to deprive of freedom.

Arguably, the BSD license is more free because the existence of a private fork doesn't deprive anyone of anything; the original work is still freely available. But on the other hand, you could argue that some of those changes merely fix bugs, and thus are not rightfully new works, and should be available to anyone who has the original software. It's a fine line, and there's no absolute right answer.

The reason the public mocks nerds, of course, is that they argue vociferously over which license is correct, which takes time away from actually making the technology better, and is often seen as a waste of everyone's time. On the other hand, without those arguments (which expand the community's understanding of the licenses and their eccentricities), there's a possibility of critical projects choosing a license that is inappropriate and ending up stuck with it to the detriment of everyone.

For example, the FSF's decision to relicense GCC under GPLv3 created stagnation in its largest user base (the Mac community), with OS X users stuck at a much older version for years, until eventually Apple worked with the LLVM team to replace it with Clang. To be fair, in the end, everybody benefitted from a more modular compiler architecture that could better be integrated into things like IDEs, so the resulting platform is more capable than GCC ever was (or ever will be, in all likelihood), but the bad licensing decision meant that the teams couldn't take advantage of each other's work, which no doubt made that transition take much longer than it otherwise would have and resulted in a lot of duplication of work, ultimately culminating in GCC becoming an evolutionary dead end that's still a giant time sink to maintain (and that, no doubt, will continue to be maintained for many years, for no real reason other than because it exists and has to work).

So in spite of the public's belief that this is all a bunch of silly squabbles like Star Wars versus Star Trek, the reality is that there are real-world implications of these arguments, making them at least somewhat valuable (up to a point, anyway).

Comment Re:All you Apple Haters can bite my shiny metal SD (Score 1) 48

I seem to recall an awful lot of Apple Haters whining about a certain new MacBook Pro that had dropped the built in SD reader...

We were complaining about the lack of UHS-II support for about five years before they dropped it. Apple dropping it rather than updating it wasn't the first snub, but rather the last straw.

Comment Re:An allegation has been made. (Score 1) 904

I'm expecting that whoever does this investigation is going to act in the shareholders' best interest, which among other things means not exposing the company to massive liabilities in court. If the investigation supports the allegations, then those responsible are going to get canned.

-jcr

Comment Re:Prime is starting to suck (Score 1) 183

Actually, what I would do is check with the carrier, and if it claims to be delivered but isn't, contact Amazon and ask them to overnight a replacement. They'll usually overnight products at no charge if you're annoyed enough to write them to complain about shipping delays even if you're not a Prime member.

Slashdot Top Deals

No one gets sick on Wednesdays.

Working...