Better yet, have people bid for each file. Obviously, the highest bidder would be the one with most need for the information, presenting a free-market solution to computer security.
The Palm Folio is staring to look good in comparison.
Except that the Foleo got cancelled earlier this month. I'm starting to think that the entire subnotebook class of computers is just a cruel joke perpetrated on investors and early adopters.
Why on earth in OS X is the menu bar for any given application not attached to the application itself? Why is it fixed to the top of the screen, detached from the very thing it controls?
It's called "FItts' Law." The edge-of-screen menu is a much easier target to access.This isn't an either-or scenario, though. I use a tiling window manager (ratpoison), and that places the menus at the top of the screen, which just so happens to also be adjacent to where the window manager places the window's content. If I want to work in two windows simultaneously, each window's menubar takes up a fraction of the screen.
I honestly don't know why this hasn't caught on. It seems like more than the best of both worlds.
I'll keep using Flash, thank you very much, because then if whatever has been coded fucks my computer I might actually have a legal recourse other than "I just installed what this random guy coded, how was I to know it was bad!"
From the Flash EULA:
7. NO WARRANTY. The Software is being delivered to you "AS IS" and Adobe makes no warranty as to its use or performance. Adobe provides no technical support, warranties or remedies for the Software. ADOBE AND ITS SUPPLIERS DO NOT AND CANNOT WARRANT THE PERFORMANCE OR RESULTS YOU MAY OBTAIN BY USING THE SOFTWARE. EXCEPT FOR ANY WARRANTY, CONDITION, REPRESENTATION OR TERM TO THE EXTENT TO WHICH THE SAME CANNOT OR MAY NOT BE EXCLUDED OR LIMITED BY LAW APPLICABLE TO YOU IN YOUR JURISDICTION, ADOBE AND ITS SUPPLIERS MAKE NO WARRANTIES CONDITIONS, REPRESENTATIONS, OR TERMS (EXPRESS OR IMPLIED WHETHER BY STATUTE, COMMON LAW, CUSTOM, USAGE OR OTHERWISE) AS TO ANY MATTER INCLUDING WITHOUT LIMITATION NONINFRINGEMENT OF THIRD PARTY RIGHTS, MERCHANTABILITY, INTEGRATION, SATISFACTORY QUALITY, OR FITNESS FOR ANY PARTICULAR PURPOSE. The provisions of Section 7 and Section 8 shall survive the termination of this Agreement, howsoever caused, but this shall not imply or create any continued right to Use the Software after termination of this Agreement. 8. LIMITATION OF LIABILITY. IN NO EVENT WILL ADOBE OR ITS SUPPLIERS BE LIABLE TO YOU FOR ANY DAMAGES, CLAIMS OR COSTS WHATSOEVER OR ANY CONSEQUENTIAL, INDIRECT, INCIDENTAL DAMAGES, OR ANY LOST PROFITS OR LOST SAVINGS, EVEN IF AN ADOBE REPRESENTATIVE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH LOSS, DAMAGES, CLAIMS OR COSTS OR FOR ANY CLAIM BY ANY THIRD PARTY. THE FOREGOING LIMITATIONS AND EXCLUSIONS APPLY TO THE EXTENT PERMITTED BY APPLICABLE LAW IN YOUR JURISDICTION. ADOBE'S AGGREGATE LIABILITY AND THAT OF ITS SUPPLIERS UNDER OR IN CONNECTION WITH THIS AGREEMENT SHALL BE LIMITED TO THE AMOUNT PAID FOR THE SOFTWARE, IF ANY. Nothing contained in this Agreement limits Adobe's liability to you in the event of death or personal injury resulting from Adobe's negligence or for the tort of deceit (fraud). Adobe is acting on behalf of its suppliers for the purpose of disclaiming, excluding and/or limiting obligations, warranties and liability as provided in this Agreement, but in no other respects and for no other purpose. For further information, please see the jurisdiction specific information at the end of this Agreement, if any, or contact Adobe's Customer Support Department.
You'll be hard-pressed to find any software --- open-source, freeware, shareware, commercial, or otherwise --- that doesn't have you agree to something to that effect. I'm no zealot, but I think that one of the better points of FOSS is that while there may be the same legal accountability involved there as with any other software, if there are responsible people behind the project (and I'd think that there are, since they're donating their time and energy to this project without any profit involved) you'll be able to resolve your issues with them instead of having someone in an East Timor call-center tell you to clear your browser caches, turn off your firewall, and call again.
More people need to know about the plight of the modern Jewish man. The parent poster is a shining beacon of truth that illuminates the sea of prejudice before us.
The report back from the drop in holiday season '06 predicted a surge in Windows XP SP2 installations and slightly better security coming with it. However, at least the latter part of that doesn't appear to be the case.
...So, what happened? Was there, in fact, a sort of mass-migration afterward, which made the more homogeneous operating system landscape a more inviting target than before? Did the operating systems change, but not to XP SP2 --- and if that's the case, what operating systems are the new computers running?
Re:Saying what you see...
on
Define - /etc?
·
· Score: 1
The convention seems a lot more rational when you realize that an archaic way of writing etc is with an ampersand --- to wit, "&c." That style was popular and is still used today (albeit in a more limited fashion) in some circles, including mathematics. I think it's fairly safe to say that many old UNIX hacks were exposed to even older mathematics in their coursework, and thus encountered that convention.
If you came across "&c" in text you were reading aloud, how would you say it? "Ampersand-see" would sound simply ludicrous, but keeping in mind that the ampersand has evolved as simply being a ligature of the Latin "et," pronouncing it as "et-see" is entirely sensible.
In fact, it's quite catchy. After all, doesn't it make sense to logically separate the two words ("et" and "cetera") of the abbreviation instead of saying each letter out loud as if it were an acronym?
Consider that even if an artist was the last of his bloodline...
First, if she had no heirs at all (including parents, siblings, cousins, etc.) then her property would escheat to the State.
Did anyone else find it just slightly disturbing that the subject was given a postmortem sex-change operation? Please tell me the name of that mortician, so I can be sure to steer clear of him.
Slashdot Mirror
Is Windows really the target you want to shoot for when it comes to UI consistency?
Chinese anti-satellite missile deployment successful.
Better yet, have people bid for each file. Obviously, the highest bidder would be the one with most need for the information, presenting a free-market solution to computer security.
Why? It's a perfectly cromulent word!
Is it normal to be concerned that TFA doesn't appear to mention where the funding for this research came from?
I honestly don't know why this hasn't caught on. It seems like more than the best of both worlds.
7. NO WARRANTY. The Software is being delivered to you "AS IS" and Adobe makes no warranty as to its use or performance. Adobe provides no technical support, warranties or remedies for the Software. ADOBE AND ITS SUPPLIERS DO NOT AND CANNOT WARRANT THE PERFORMANCE OR RESULTS YOU MAY OBTAIN BY USING THE SOFTWARE. EXCEPT FOR ANY WARRANTY, CONDITION, REPRESENTATION OR TERM TO THE EXTENT TO WHICH THE SAME CANNOT OR MAY NOT BE EXCLUDED OR LIMITED BY LAW APPLICABLE TO YOU IN YOUR JURISDICTION, ADOBE AND ITS SUPPLIERS MAKE NO WARRANTIES CONDITIONS, REPRESENTATIONS, OR TERMS (EXPRESS OR IMPLIED WHETHER BY STATUTE, COMMON LAW, CUSTOM, USAGE OR OTHERWISE) AS TO ANY MATTER INCLUDING WITHOUT LIMITATION NONINFRINGEMENT OF THIRD PARTY RIGHTS, MERCHANTABILITY, INTEGRATION, SATISFACTORY QUALITY, OR FITNESS FOR ANY PARTICULAR PURPOSE. The provisions of Section 7 and Section 8 shall survive the termination of this Agreement, howsoever caused, but this shall not imply or create any continued right to Use the Software after termination of this Agreement.
8. LIMITATION OF LIABILITY. IN NO EVENT WILL ADOBE OR ITS SUPPLIERS BE LIABLE TO YOU FOR ANY DAMAGES, CLAIMS OR COSTS WHATSOEVER OR ANY CONSEQUENTIAL, INDIRECT, INCIDENTAL DAMAGES, OR ANY LOST PROFITS OR LOST SAVINGS, EVEN IF AN ADOBE REPRESENTATIVE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH LOSS, DAMAGES, CLAIMS OR COSTS OR FOR ANY CLAIM BY ANY THIRD PARTY. THE FOREGOING LIMITATIONS AND EXCLUSIONS APPLY TO THE EXTENT PERMITTED BY APPLICABLE LAW IN YOUR JURISDICTION. ADOBE'S AGGREGATE LIABILITY AND THAT OF ITS SUPPLIERS UNDER OR IN CONNECTION WITH THIS AGREEMENT SHALL BE LIMITED TO THE AMOUNT PAID FOR THE SOFTWARE, IF ANY. Nothing contained in this Agreement limits Adobe's liability to you in the event of death or personal injury resulting from Adobe's negligence or for the tort of deceit (fraud). Adobe is acting on behalf of its suppliers for the purpose of disclaiming, excluding and/or limiting obligations, warranties and liability as provided in this Agreement, but in no other respects and for no other purpose. For further information, please see the jurisdiction specific information at the end of this Agreement, if any, or contact Adobe's Customer Support Department.
You'll be hard-pressed to find any software --- open-source, freeware, shareware, commercial, or otherwise --- that doesn't have you agree to something to that effect. I'm no zealot, but I think that one of the better points of FOSS is that while there may be the same legal accountability involved there as with any other software, if there are responsible people behind the project (and I'd think that there are, since they're donating their time and energy to this project without any profit involved) you'll be able to resolve your issues with them instead of having someone in an East Timor call-center tell you to clear your browser caches, turn off your firewall, and call again.
More people need to know about the plight of the modern Jewish man. The parent poster is a shining beacon of truth that illuminates the sea of prejudice before us.
...So, what happened? Was there, in fact, a sort of mass-migration afterward, which made the more homogeneous operating system landscape a more inviting target than before? Did the operating systems change, but not to XP SP2 --- and if that's the case, what operating systems are the new computers running?
The convention seems a lot more rational when you realize that an archaic way of writing etc is with an ampersand --- to wit, "&c." That style was popular and is still used today (albeit in a more limited fashion) in some circles, including mathematics. I think it's fairly safe to say that many old UNIX hacks were exposed to even older mathematics in their coursework, and thus encountered that convention.
If you came across "&c" in text you were reading aloud, how would you say it? "Ampersand-see" would sound simply ludicrous, but keeping in mind that the ampersand has evolved as simply being a ligature of the Latin "et," pronouncing it as "et-see" is entirely sensible.
In fact, it's quite catchy. After all, doesn't it make sense to logically separate the two words ("et" and "cetera") of the abbreviation instead of saying each letter out loud as if it were an acronym?
I think you'll find that I'm much denser than this.
Did anyone else find it just slightly disturbing that the subject was given a postmortem sex-change operation? Please tell me the name of that mortician, so I can be sure to steer clear of him.