It's not bullshit, it's straight up harder on your eyes if you're doing a lot of scanning. If you're spending a long time concentrating on the various parts of the line (like in code) ymmv, but in general, your eyes scan like shit if the text is too wide. However, it's not a number of characters, it's a certain angular width... so distance to the monitor and dpi matter just as much. I also expect the angle differs for everyone.
Personally, I use a 4:3 section of the screen for code... and maximize (16:9) if I'm working with really long lines. I also use a pretty big font these days... other words... blah.
But his point was that, for text tracking, your eyes do best in a narrower area. I bet you read web pages more than you write code.
You can probably get some or all of the papers on loan at libraries... My university library does this for journals to which I do have access through my university account. I'm sure public libraries can do it also.
I can't help but feeling like this has already been done. Seems to me it was a couple hundred years before computers, but the meaning was clear enough.
The dictionary shows common usage, not correct usage. This usage was clearly based on a mistake. They mean devastate and it caught on because people didn't know better. The educated should defend the word imo.
Oh, well, I guess when I compiled that netcat binary I was using the NDK. Honestly, I had no idea. Now I have even less interest into writing apps for Android. Thanks.
The hardware dongle might help for a while, but I'm willing to bet even that doesn't work for very long. make your extra money on support. Make sure the software is so customized to a single business (hey, $10k) that it wouldn't do anyone else any good, or would be so obvious they wouldn't try. If the software isn't custom and would potentially be useful to people who can't (or wont') pay, then your copy protection won't work. Doesn't really matter what you pick. Paying customers will pay either way, don't punish them.
People said this about nokia and blackberry before iphone came up, and they said the exact same thing before android came up. So the comments about too many strong players are clearly wrong, you just push a strong player out of the way when you come up. But you're also right. It'll never get that point. It's lacking two rather important things... What WebOS needs is a strong partner that actually gives a shit and an actual device that ships with it. Last time I checked people rooting their phones to run other shit "voids your warranty" and shit like that, so you're never going to see more than like 0.05% of device owners ever installing something else, and of those only a small portion will try WebOS.
I'd probably try it. I loved it. One really nice thing on that platform was that rooting and installing shit was *SUPPORTED*. They had an app to fix it when you fucked it up, and if you bricked it (the guys on #webos-internals knew of a way, but they wouldn't say); they'd replace it.
I like that it's not illegal to root phones, finally, but we need legislation that says: if your device can't support rooting, then you need to replace it, sorry. I have different feelings about overclocking. Clearly overclocking can't be supported. Palm wouldn't replace them if you fried them from overclocking, but they had to kinda take your word on it too.
AIR would be fine by me (who cares what it runs imo, even if a slow crappy platform), but they dropped linux support, making Pandora One a PITA to run.
Ooops, ranted about the filesystems, I didn't realize they were talking about the layout of the distribution and the well organized directories full of useful information. I unloaded my rant too early. It still applies, but it's aimed at slightly the wrong things.
When linux gets so simple my mom can sysadmin it with no worries, but I can't get anything done... wtf do I switch to? Corollary: why do we keep fixing things in linux kerneled operating systems that aren't even broken. Just leave the file system alone or you'll end up with Ext5: Unity Disaster.
Ahh, that was my point. They're not at all equipped to tell what's obvious and what's an invention. They should be leaning toward unobvious, rather than obvious. If they're wrong and it was unobvious, it damages society, innovation, and the economy -- in addition to making them look like unequipped idiots. If they're wrong and it's obvious, then at worst the applicant has to refile with more evidence of obviousness.
... apparently circuits should not be patentable. Basically anything that's obvious or just the next logical step (even if clever) should not be patentable. So if he's right then we should see circuit design as just another program and get rid of those patents too.
I agree on all counts except for one thing... If you click through to the article (Vinge had it right), she's talking about his idea that it rises slowly without any disaster to get people to go for it. Surely Vinge built on ideas from others, everyone does. But they're specifically talking about how accepting we all are (will be?) toward it. In his Rainbows End, a character specifically says that we traded freedom for safety, implying that it was a willing transition.
Slashdot Mirror
If it's android, then yes. Probably iOS too. Or a PC, yes, absolutely. The only real question is what happens when amazon folds.
It's not bullshit, it's straight up harder on your eyes if you're doing a lot of scanning. If you're spending a long time concentrating on the various parts of the line (like in code) ymmv, but in general, your eyes scan like shit if the text is too wide. However, it's not a number of characters, it's a certain angular width... so distance to the monitor and dpi matter just as much. I also expect the angle differs for everyone.
Personally, I use a 4:3 section of the screen for code ... and maximize (16:9) if I'm working with really long lines. I also use a pretty big font these days... other words ... blah.
But his point was that, for text tracking, your eyes do best in a narrower area. I bet you read web pages more than you write code.
That seems like a reasonable fee to me. the delay is annoying, but I believe you *can* get most of this information.
You can probably get some or all of the papers on loan at libraries... My university library does this for journals to which I do have access through my university account. I'm sure public libraries can do it also.
I can't help but feeling like this has already been done. Seems to me it was a couple hundred years before computers, but the meaning was clear enough.
The dictionary shows common usage, not correct usage. This usage was clearly based on a mistake. They mean devastate and it caught on because people didn't know better. The educated should defend the word imo.
He split the bank into 10 parts? Or did he apply a 10% tax maybe? ...
Maybe the author means devastate?
Oh, well, I guess when I compiled that netcat binary I was using the NDK. Honestly, I had no idea. Now I have even less interest into writing apps for Android. Thanks.
I'm honestly surprised Java is even a choice for Android. Most people write in C++ afaik. http://developer.android.com/guide/basics/what-is-android.html
But the crime is a result of the prohibition.
Seriously. You'll only annoy the people that pay.
The hardware dongle might help for a while, but I'm willing to bet even that doesn't work for very long. make your extra money on support. Make sure the software is so customized to a single business (hey, $10k) that it wouldn't do anyone else any good, or would be so obvious they wouldn't try. If the software isn't custom and would potentially be useful to people who can't (or wont') pay, then your copy protection won't work. Doesn't really matter what you pick. Paying customers will pay either way, don't punish them.
Their point is that he didn't use it correctly in the hundreds years old sense: http://en.wikipedia.org/wiki/Begs_the_question
People said this about nokia and blackberry before iphone came up, and they said the exact same thing before android came up. So the comments about too many strong players are clearly wrong, you just push a strong player out of the way when you come up. But you're also right. It'll never get that point. It's lacking two rather important things ... What WebOS needs is a strong partner that actually gives a shit and an actual device that ships with it. Last time I checked people rooting their phones to run other shit "voids your warranty" and shit like that, so you're never going to see more than like 0.05% of device owners ever installing something else, and of those only a small portion will try WebOS.
I'd probably try it. I loved it. One really nice thing on that platform was that rooting and installing shit was *SUPPORTED*. They had an app to fix it when you fucked it up, and if you bricked it (the guys on #webos-internals knew of a way, but they wouldn't say); they'd replace it.
I like that it's not illegal to root phones, finally, but we need legislation that says: if your device can't support rooting, then you need to replace it, sorry. I have different feelings about overclocking. Clearly overclocking can't be supported. Palm wouldn't replace them if you fried them from overclocking, but they had to kinda take your word on it too.
AIR would be fine by me (who cares what it runs imo, even if a slow crappy platform), but they dropped linux support, making Pandora One a PITA to run.
The Department of Freedom and Privacy Why do the names of these things frequently say backwards of what they do (eg, DRM)?
thanks
Ooops, ranted about the filesystems, I didn't realize they were talking about the layout of the distribution and the well organized directories full of useful information. I unloaded my rant too early. It still applies, but it's aimed at slightly the wrong things.
When linux gets so simple my mom can sysadmin it with no worries, but I can't get anything done... wtf do I switch to? Corollary: why do we keep fixing things in linux kerneled operating systems that aren't even broken. Just leave the file system alone or you'll end up with Ext5: Unity Disaster.
Ahh, that was my point. They're not at all equipped to tell what's obvious and what's an invention. They should be leaning toward unobvious, rather than obvious. If they're wrong and it was unobvious, it damages society, innovation, and the economy -- in addition to making them look like unequipped idiots. If they're wrong and it's obvious, then at worst the applicant has to refile with more evidence of obviousness.
... apparently circuits should not be patentable. Basically anything that's obvious or just the next logical step (even if clever) should not be patentable. So if he's right then we should see circuit design as just another program and get rid of those patents too.
I have to admit, I thought he was an asshole before I read that...
I'm very surprised by this new information.
I agree on all counts except for one thing ... If you click through to the article (Vinge had it right), she's talking about his idea that it rises slowly without any disaster to get people to go for it. Surely Vinge built on ideas from others, everyone does. But they're specifically talking about how accepting we all are (will be?) toward it. In his Rainbows End, a character specifically says that we traded freedom for safety, implying that it was a willing transition.
Tell them it's math. Everything else is programming, sysadmining, networking, or otherwise not computer science (which is math).
Sugar also cuts the pain like instantly. I usually use a nice glass of ginger ale with too much ice. It's delicious even if you're not in pain.