As I understand it, part of the point of Source-Level cores (eg. like OpenCores.org) is to be able to synthesize multiple cores into a single chip and have them talk amongst themselves via standard internal interfaces. Eg. a chip contains a microprocessor, an implicit USB interface, and maybe has some hardware-accelerated DES encryption included as well. And OpenCores brings this capability to the common person.
IE popped up a helpful page when a domain wasn't found; what's so bad about the actual domain registrar doing it?
How many times does this have to be said?
Implementing SiteFinder so it only works for the HTTP protocol is fine... implementing it in such a way that it affects every protocol on the internet is BAD and has unintended consequences. Implementing sitefinder in specific applications so that users have a choice about having it is even better is the best of all worlds.
As soon as they start helping with the International Space Station, then we can consider them one and the same. For now, they're being as secretive about their space program as possible (they had to tell the world that they were about to launch a manned space mission so we didn't mistake it for a nuke).
Who cares about the real world? Having robots capable of doing martial arts means we're much closer to having 5-story tall robots fighting over the future of Tokyo! (and various other classic anime scenarios)
It's clear that a lot of people, including geeks, will want 64-bit support. (as opposed to some non-geeks wanting a clock to take up 15% of their screen, non-geeks who don't code) As for "being a player" with respect to the kernel, you'll have to ask Linus about his particular motivations. Watch out though, he's always been pretty coy regarding competition with Microsoft.
If anything, I think it's possibly acceptable to have that stuff on a second monitor off to the side. I'm sure it will come down to personal preferences. But if it's anything like XP, techies will find 20% of the improvements to be useful and 80% of the improvements will be fluff that you half to spend two hours turning off every time your reinstall.
That's the thing about open source guys -- we scratch itches we see now, we don't come up with as many hypothetical itches 4 years from now just so we can convince users that the product is improved enough to shell out $150 more.
Given Microsoft's past behavior, I'm sure that the APIs will have at least some meaty improvement, and will convince many software developers that they want to write their programs on the improved APIs instead of the old ones, which will in turn encourage consumers to get the updated OS so they can run their software on it. The thing is, they don't have to bury these solid improvements in tons of extra fluff that eats up RAM and will be turned off by anyone who knows how.
Oh my god, it's moving in the same direction as XP did (greater percentage of the screen eaten up by default, more pixels taken up by round cute window dressings, and start menus / taskbars / sidebars that are more cluttered and complicated than useful). Great, just what I wanted... *grumble*
Jason Kottke links to suggestions that the Nokia phones detect batteries which aren't made by Nokia, and when it detects on, it puts the phone in maximum-current-draw mode to try to encourage the user to buy a Nokia battery, and this could be causing the exploding batteries.
Of course, this is an allegation that'd be hard to prove without insider verification. Or possibly, with some astute multimeter readings.
Microwave ovens 1) use the same frequency as WiFi networks, and 2) give off 10 times the radiation as a WiFi network. So schools should be sued for gross neglegence if they have microwaves too! Or plaintiffs who own microwave ovens should be shot.
I like wood. It can be used in innovative ways. Therefore, I believe everything (cars, spaceships, skyscrapers....) should be built with it. If I were a government-granted monopoly with the power to mandage use of wood, I'd do exactly that. Surethere'd be technical problems here and there, but as long as the engineers talked it out with me, everything would be fine.
First he continues the Web==Internet BS, then he strongly implies that Verision Sitefinder's drawbacks had a technical solution other than complete negation of what they'd done. If they think there's a technical alternative to making Sitefinder useful and only show up for WWW users, suggest it. I've heard of no such thing.
Unfortunately SGI is talking only about SGI submitted code:
The point of SGI's comparison was to search for any potential matches between Unix System V and any contributions that SGI made to the Linux kernel, not to vet the software for the entire community, Estes said in an interview. "We are not making any kind of representation at all about anybody else's contributed code," he said.
So SCO could still potentially be right in saying that IBM submitted a lot of Unix code into Linux.
Curiously, because SGI has access to both codebases, and know how to run the Comparator, SGI probably has a good idea how many non-SGI violations are in the code (eg. the details may be complicated, but surely they can guess within an order of magnitude). So for now, it's IBM and SGI knowing and not telling, SCO knowing and saying as many ludicrous things as possible, and the rest of us left to speculate until this thing goes to court.
Read this past slashdot story on the likely best workaround. Basically it blocks/undoes what verisign has done. Given how monopolistic their actions are though and how it benefits verisign 100 times more than it benefits anyone else, they should really take it down.
It was funny, the first couple times. I just don't like product placements in chatrooms that are made to look like they're by just another member of the community. He's actually been more on-topic than you'd expect from a PR person so I haven't complained until now, but given that this particular article been repeated at least once, I felt it was too much. The mod was more an idealogical stance on the more subversive of advertising.
And yes, see my sibling post about it being a mistake regarding autofilling forms. As I mentioned, it really doesn't change my idealogical stance.
1) The word "SGI" doesn't appear in your article at all, it's just a generic SCO piece.
2) The article is dated over a month ago, and there have been many many SCO articles on slashdot in that month, eg. many opportunities to post the story offtopic
3) You post bbspot articles all the time (which I think is fine as long as they're semi-ontopic and not repetitive), and I've seen you post this exact one in at least one previous SCO article.
Therefore: modded down offtopic. And every time you post this link in future SCO articles, I'll also mark them down offtopic (unless, of course, it's an story about SCO doing something with actual babies, in which case it would probably be hilarious).
Even played SimCity? Those are the main two influences... lower taxes leads less government revenue per tax payer... higher taxes leads to less taxpayers. If you're seeking to maximize government revenue, SOME taxpayers moving away is acceptable, as long as you're still on the left side of the curve heading up (or raising taxes briefly and then lowering them before taxpayers get motivated enough to move away).
-Dave
Are software-only VoIP providers required to pay also? The article is a little light on the details. This is clearly the first step for charging extra for specific kinds of data that differ by nothing other than what they're used for.
I have no intention of installing 4 different IM clients on my pc
Well, the funny thing with capitalism is that if you want genuine competition between companies, you're going to have to accept some overhead (eg. multiple design teams working completely independantly on the same problem, consumers having to spend extra time to intelligently choose their prefered supplier).
That is, the moment a closed-source multi-network IM client is released, slashdot is going to scream bloody murder about the anti-competitive opportunities, especially if the client is released by Microsoft.
Re:Wonder if they used this?
on
SCO's Plan Examined
·
· Score: 2, Informative
Yeah, he has it online here: http://www.levenez.com/unix/. Though obviously without the prominence of SCO and without the inference that SCO owns anything and everything Unix related.
Well, explain the differences then! Or post a link.
The Reuters translation post said that the laws specifies that simply implementing something in software that previously existed outside of software isn't patentable, which sounds tremendously good to me. Anything else that's good?
Slashdot Mirror
For lower-performance cores, they can put the synthesized cores on an FPGA, which is good enough in a lot of cases.
As I understand it, part of the point of Source-Level cores (eg. like OpenCores.org) is to be able to synthesize multiple cores into a single chip and have them talk amongst themselves via standard internal interfaces. Eg. a chip contains a microprocessor, an implicit USB interface, and maybe has some hardware-accelerated DES encryption included as well. And OpenCores brings this capability to the common person.
- IE popped up a helpful page when a domain wasn't found; what's so bad about the actual domain registrar doing it?
How many times does this have to be said?Implementing SiteFinder so it only works for the HTTP protocol is fine... implementing it in such a way that it affects every protocol on the internet is BAD and has unintended consequences. Implementing sitefinder in specific applications so that users have a choice about having it is even better is the best of all worlds.
As soon as they start helping with the International Space Station, then we can consider them one and the same. For now, they're being as secretive about their space program as possible (they had to tell the world that they were about to launch a manned space mission so we didn't mistake it for a nuke).
Who cares about the real world? Having robots capable of doing martial arts means we're much closer to having 5-story tall robots fighting over the future of Tokyo! (and various other classic anime scenarios)
It's clear that a lot of people, including geeks, will want 64-bit support. (as opposed to some non-geeks wanting a clock to take up 15% of their screen, non-geeks who don't code) As for "being a player" with respect to the kernel, you'll have to ask Linus about his particular motivations. Watch out though, he's always been pretty coy regarding competition with Microsoft.
That's the thing about open source guys -- we scratch itches we see now, we don't come up with as many hypothetical itches 4 years from now just so we can convince users that the product is improved enough to shell out $150 more.
Given Microsoft's past behavior, I'm sure that the APIs will have at least some meaty improvement, and will convince many software developers that they want to write their programs on the improved APIs instead of the old ones, which will in turn encourage consumers to get the updated OS so they can run their software on it. The thing is, they don't have to bury these solid improvements in tons of extra fluff that eats up RAM and will be turned off by anyone who knows how.
Oh my god, it's moving in the same direction as XP did (greater percentage of the screen eaten up by default, more pixels taken up by round cute window dressings, and start menus / taskbars / sidebars that are more cluttered and complicated than useful). Great, just what I wanted... *grumble*
What?? Isn't every interstate-commerce transaction a "double ended transaction", and clearly covered by federal (rather than state) law?
Hrm. I don't have a nokia battery with me, but a motorola battery here I guess seems to be microchip free (the lump felt turned out to be a diode).
Of course, this is an allegation that'd be hard to prove without insider verification. Or possibly, with some astute multimeter readings.
Microwave ovens 1) use the same frequency as WiFi networks, and 2) give off 10 times the radiation as a WiFi network. So schools should be sued for gross neglegence if they have microwaves too! Or plaintiffs who own microwave ovens should be shot.
-interiot@am4z0n.com
I like wood. It can be used in innovative ways. Therefore, I believe everything (cars, spaceships, skyscrapers....) should be built with it. If I were a government-granted monopoly with the power to mandage use of wood, I'd do exactly that. Surethere'd be technical problems here and there, but as long as the engineers talked it out with me, everything would be fine.
First he continues the Web==Internet BS, then he strongly implies that Verision Sitefinder's drawbacks had a technical solution other than complete negation of what they'd done. If they think there's a technical alternative to making Sitefinder useful and only show up for WWW users, suggest it. I've heard of no such thing.
- The point of SGI's comparison was to search for any potential matches between Unix System V and any contributions that SGI made to the Linux kernel, not to vet the software for the entire community, Estes said in an interview. "We are not making any kind of representation at all about anybody else's contributed code," he said.
So SCO could still potentially be right in saying that IBM submitted a lot of Unix code into Linux.Curiously, because SGI has access to both codebases, and know how to run the Comparator, SGI probably has a good idea how many non-SGI violations are in the code (eg. the details may be complicated, but surely they can guess within an order of magnitude). So for now, it's IBM and SGI knowing and not telling, SCO knowing and saying as many ludicrous things as possible, and the rest of us left to speculate until this thing goes to court.
Read this past slashdot story on the likely best workaround. Basically it blocks/undoes what verisign has done. Given how monopolistic their actions are though and how it benefits verisign 100 times more than it benefits anyone else, they should really take it down.
And yes, see my sibling post about it being a mistake regarding autofilling forms. As I mentioned, it really doesn't change my idealogical stance.
1) The word "SGI" doesn't appear in your article at all, it's just a generic SCO piece.
2) The article is dated over a month ago, and there have been many many SCO articles on slashdot in that month, eg. many opportunities to post the story offtopic
3) You post bbspot articles all the time (which I think is fine as long as they're semi-ontopic and not repetitive), and I've seen you post this exact one in at least one previous SCO article.
Therefore: modded down offtopic. And every time you post this link in future SCO articles, I'll also mark them down offtopic (unless, of course, it's an story about SCO doing something with actual babies, in which case it would probably be hilarious).
Even played SimCity? Those are the main two influences... lower taxes leads less government revenue per tax payer... higher taxes leads to less taxpayers. If you're seeking to maximize government revenue, SOME taxpayers moving away is acceptable, as long as you're still on the left side of the curve heading up (or raising taxes briefly and then lowering them before taxpayers get motivated enough to move away). -Dave
Are software-only VoIP providers required to pay also? The article is a little light on the details. This is clearly the first step for charging extra for specific kinds of data that differ by nothing other than what they're used for.
- I have no intention of installing 4 different IM clients on my pc
Well, the funny thing with capitalism is that if you want genuine competition between companies, you're going to have to accept some overhead (eg. multiple design teams working completely independantly on the same problem, consumers having to spend extra time to intelligently choose their prefered supplier).That is, the moment a closed-source multi-network IM client is released, slashdot is going to scream bloody murder about the anti-competitive opportunities, especially if the client is released by Microsoft.
Yeah, he has it online here: http://www.levenez.com/unix/. Though obviously without the prominence of SCO and without the inference that SCO owns anything and everything Unix related.
The Reuters translation post said that the laws specifies that simply implementing something in software that previously existed outside of software isn't patentable, which sounds tremendously good to me. Anything else that's good?