The reason it's in such a state is because PalmSource needs to support their legacy m68000 processor because that's what their developers are still using, and it's a vicious cycle. In contrast, BlackBerry has gone from Intel 80386 to ARM 7/9 to Intel PXA901. Why aren't BB developers lamenting their lot? Because, due to Java, all they've seen are faster speeds and better APIs.
Uhhh, if the constant cost of a method call is the limiting factor, why not just get a processor with a higher clock frequency? I mean, would you trust your money on hand-written assembler in a world where regulations can change yearly and in a company which wants to skimp on the hardware?
We're not evolved for space flight either. Yet millions of people go to space everyday? Or perhaps a space flight to the ISS requires months of preparation precisely because we truly aren't evolved for space flight.
All it would is one person with "Public Domain" in their Google Alerts who uploads all new projects to SourceForge and the code would be available for perpetuity. Hell, Google has a source code repository of their own, they could automate the whole process!
Granted, it's pretty clean, but Are you new to Usenet? contains this gem: "Usenet contains millions of mp3s, videos, software, movies, videos, games, and much more you can download for free! We also have all the text groups for those of you who like to engage in deep discussions."
The point of dual-licensing is that you get to choose either of the licenses. If both licenses had to be in effect at the same time then there would effectively be a single license, a combination of the two.
BSD and GPL take effect when the code is distributed. If you receive dual-licensed code under BSD in binary format, you get to choose GPL only when you distribute it, allowing those receiving the code from you to request the source from you.
Nevertheless, the BSD license only applies to the original BSD code, not to any modifications. That's not what the BSD says: Redistribution and use in source and binary forms, with or without modification, are permitted...
Only the original code remains licensed under the BSD license. The new code is licensed under the GPL, which means that you can redistribute the entire file only if you meet the conditions of both the BSD and the GPL license. The BSD applies to the code, with or without modifications. So any modifications must be also licensed under BSD if they are distributed with the unmodified parts. Or at least that's what
Groklaw says.
If your players want to be at the same place at the same time, your content solution has already failed. If your players want the option of being at the same place at the same time, your content solution can only delay the inevitable.
If some slighted player organizes a mass protest, how is your content solution going to help with that?
I see this kind of thing pop up on a regular basis, and it always missed the point. This isn't a technology problem! Speaking as someone who's actually worked on multiple massively-multiplayer games, once you've got the server tech to support 10,000 people on a server cluster, there aren't a lot of technical obstacles to scaling that up to 8,000,000 people. Every part of the server cluster can be scaled out more or less infinitely if you apply the correct (and already well-known) engineering solutions. And money, of course. Really? Because as I understand it, EvE Online does 40 vs. 40 battles fine but starts to struggle with 400 vs. 400 battles. With your technical expertise, they should be able to scale to 4000000 vs. 4000000 battles easily, right?
What you are describing is chopping a one-world up to many-worlds, but you can't call the result a one-world. The one-world problem is very much a technology problem.
This leads to an absurd situation - both license, which are incompatible with one another, are simultaneously in effect. No, they aren't. Every user gets to choose which license that particular code is under, as long as they aren't redistributing. A user could probably (IANAL) remove all GPL-only parts and redistribute the dual-licensed code under both licenses again.
What is absurd (absurdly ironic) is a GPL-proponent trying to use that freedom of choice to deny other users the same freedom of choice.
You are missing the distinction between distributing and licensing. You are not the copyright holder of the code, so you can't revoke its BSD license because BSD doesn't allow you to.
The issue has to do with the way spreadsheets have historically represented dates. They do not represent dates in a special format, but instead as a floating point which can be interpreted by a special format. So "N.M" becomes day N hour M (where M is some fraction of the day, I cant remember now exactly the mapping). So, one could create a spreadsheet to show the amount of time remaining after various number of 1-hour tasks and conceivably have it say that after completing 24 1-hours tasks there's still say 0.001 seconds left of a day?
And that stupidity is supposed to become an international standard?
1) The fact that the iPhone has a sleep/wake button is unacceptable, because it "should" be an on/off button (ignoring the fact that every other smartphone, hell, and every TV & A/V component made in the last 15 years, operates EXACTLY the same way). Yes, when I press the power switch on my remote my TV keeps checking my email every 15 minutes.
2) Users should NOT have to read the manual to fully understand how the iPhone works (despite the fact that "RTFM" would be tossed around with alarming regularity in almost all other situations). Don't feel bad, users shouldn't have to RTFM to use Linux, either.
3) The iPhone continues to check e-mail while asleep (does any smartphone NOT check e-mail while asleep, when it is still receptive to incoming calls/text messages?). Sleep == fully-on-but-screen-off is a good start, but we can improve usability further: snoring == fully-on-but-screen-off-with-single-flashing-light, deep sleep == fully-on-but-screen-off-doesn't-wake-even-if-called. I'm sure more can be invented. Get cracking, Apple!
4) The fact that the iPhone has a sleep mode that is different than "fully off" is a major design flaw, and its existence is simply unconscionable (as mentioned earlier in this list, sleep mode is pretty standard on electronic devices these days). What you call your TV sleeping other people call the TV being off, as in not operating until turned on again. Replacing an industry standard labeled power switch with an unlabeled "Sleep/Wake" button is of course innovation when Apple is doing it.
Here's several phones and their indicators in stand-by mode:
Motorola V220: has a small screen on the cover which stays on.
Samsung SGH E730: has a small screen on the cover which stays on.
Siemens S65: shows a clock on the screen.
Nokia E50, E61, 7650, 3100, etc: shows date and/or time on screen.
There are no absolute freedoms. Sure there are, if you just define them. For example: Actor A has an absolute freedom to do action X wrt. actor B iff doing action X and not doing action X result in actor B receiving the same information.
Also, Art has a very specific purpose in mind. It can't be reused easily. Where else are the 7 dwarves going to be used other than Snow White? Slap some beards on them and change the color of their clothes to green and you've got yourself a leprechaun movie.
Art isn't reused because it can't be, it isn't reused because doing so cheapens its value in the viewer's eyes.
Slashdot Mirror
Let me guess, that month was December, the next year you changed your business model to pay-what-you-like and made multi-millions?
Or you discovered a thing called promotion.
Are you sure you're not breaking an EULA somewhere by alluding to benchmarks comparing .NET to other languages?
The reason it's in such a state is because PalmSource needs to support their legacy m68000 processor because that's what their developers are still using, and it's a vicious cycle. In contrast, BlackBerry has gone from Intel 80386 to ARM 7/9 to Intel PXA901. Why aren't BB developers lamenting their lot? Because, due to Java, all they've seen are faster speeds and better APIs.
Uhhh, if the constant cost of a method call is the limiting factor, why not just get a processor with a higher clock frequency? I mean, would you trust your money on hand-written assembler in a world where regulations can change yearly and in a company which wants to skimp on the hardware?
All it would is one person with "Public Domain" in their Google Alerts who uploads all new projects to SourceForge and the code would be available for perpetuity. Hell, Google has a source code repository of their own, they could automate the whole process!
Granted, it's pretty clean, but Are you new to Usenet? contains this gem: "Usenet contains millions of mp3s, videos, software, movies, videos, games, and much more you can download for free! We also have all the text groups for those of you who like to engage in deep discussions."
Pretty blatant, if you ask me.
Source?
I believe in God the same way I believe in the mathematical infinity.
Surely not every country. Only the ones it wants to do business in.
The point of dual-licensing is that you get to choose either of the licenses. If both licenses had to be in effect at the same time then there would effectively be a single license, a combination of the two.
BSD and GPL take effect when the code is distributed. If you receive dual-licensed code under BSD in binary format, you get to choose GPL only when you distribute it, allowing those receiving the code from you to request the source from you.
If your players want to be at the same place at the same time, your content solution has already failed. If your players want the option of being at the same place at the same time, your content solution can only delay the inevitable.
If some slighted player organizes a mass protest, how is your content solution going to help with that?
What you are describing is chopping a one-world up to many-worlds, but you can't call the result a one-world. The one-world problem is very much a technology problem.
What is absurd (absurdly ironic) is a GPL-proponent trying to use that freedom of choice to deny other users the same freedom of choice.
You are missing the distinction between distributing and licensing. You are not the copyright holder of the code, so you can't revoke its BSD license because BSD doesn't allow you to.
So, one could create a spreadsheet to show the amount of time remaining after various number of 1-hour tasks and conceivably have it say that after completing 24 1-hours tasks there's still say 0.001 seconds left of a day?
And that stupidity is supposed to become an international standard?
Here's several phones and their indicators in stand-by mode:
Motorola V220: has a small screen on the cover which stays on.
Samsung SGH E730: has a small screen on the cover which stays on.
Siemens S65: shows a clock on the screen.
Nokia E50, E61, 7650, 3100, etc: shows date and/or time on screen.
No.
FUD, anyone?
Slap some beards on them and change the color of their clothes to green and you've got yourself a leprechaun movie.
Art isn't reused because it can't be, it isn't reused because doing so cheapens its value in the viewer's eyes.
Sounds like your drive is going bad. Convert the ReiserFS partition to NTFS and vice versa to see if it "fixes" the problem.