Developers don't find business cards useful because they're not doing business (meeting customers, drumming up new ones, negotiating contracts, meeting with zoning, local, or state officials, etc.). Developers, on the other hand, develop.
Did you see the video of them dropping water on the reactor? What a joke.
They said it was 7 tons. 1 ton == 1000 L. That's like 50 or so of those office water things. Multiply by 7.
Did they seriously expect some serious cooling with that? Anybody with any smarts is going to go far away before the authorities fess up to the extent of the problem.
I'm looking for some basic information. Basic as in "at the base". Like if you know the ASM or C pointer background of what a variable and function call really are, you more easily understand any language.
So stuff like, what's DVB? Symbol rate? How are channels established? Etc.
Wait, maybe I don't understand correctly, but are you saying that some disability "advocates" are saying that schools can't use headphones because that would mean fully-abled students can experience something that the disabled (deaf) can't?
While I support disability access where that wouldn't cost much more than standard access, it's not possible to provide the range of sensory experience to a disabled student that's available to a fully-abled student.
The funny thing is, because I guess schoolmarms aren't teaching these handy rules anymore, people are hypercorrecting themselves where they don't even need to:
"me" is seen as a indicator of lower status, like "ain't", so people just use I where it doesn't fit:
"They gave my wife and I a gift." Wrong.
Split them up, and then see if it works: "They gave my wife a gift." OK.
In what category of animal does ExtJs fit vs. jQuery combined with jQuery UI?
jQuery has basically broken away from the pack from other Javascript toolkits/frameworks/libraries. (Which is not to say they all have the same purpose.)
When you've got a lot of players in the field, and have to decide what to use, and are also thinking about new devs already being familiar with a package, going with the market leader seems to be what most people will do.
The $ and css-based selector syntax of jQuery makes it highly welcoming for devs that have to learn Yet Another Library. See also.
Wow, a 10:1 ratio, much more than the 2:1 (with caching) using a simple ab test from the serverfault link.
Reading the responses above, I'm thinking that a happy medium is:
-HTTPS for login for free users. Has the risk of sessionjacking -Ask for old password before changing password or major actions like "delete all" -HTTPS by default or by option for paid users.
Interesting. I'll bet you you had some kind of time convincing the client that hours billed for that research were worth it. ("If you're such a great developer, you should already know that")
Thinking out loud: I'd think a way to prevent password changes would be to require you to enter the old password in order to change the password, like passwd does.
Apologies in advance, but in the great Slashdot tradition of going off on a grammer* tangent:
It is'nt "whomever" would pay, it's "whoever". Whom would be used if it were the object of the verb, which it's not. It's the subject. You can tell by substituting "he/him" for "who/whom": "Him would pay" doesn't make sense. "He would pay" does, and he is nominative.
An example of a subject would be: To "whom" should this prize be given? Give "him" this prize. Whom and him are both objects of the verb give.
* Yes, grammer (and another word) is misspelt on purpose to attract the inevitable "you misspelled grammar" response, also a hallmark of grammar Nazi posts.
Would you rather lose a few years off your old age (after having retired from a career and seen and played with your grandkids), or face a very small chance of dying soon after a devastating nuclear disaster?
Joe Schmoe has chosen the former, and it's entirely logical. Known risk vs. small chance of catastrophe.
>Yes, accidents will, from time to time, occur that you *cannot* plan for.
Well, that's actually the point antis are trying to make. What'll happen if a bomb detonates at a solar thermal plant? A big mess, but not much more. Compare to nuclear.
The problem with that is nuke plants generate huge amounts of waste heat. And oceans are great for dissipating heat. And many faultlines are near coasts.
All throughout this thread, posters have been making fun of "Joe Sixpack", so forgive me if I balance things out:
There are certain kinds of visceral things that normal people get, but which geeks struggle with. However, just because geeks don't understand a particular argument doesn't make it any less valid.
I think the infatuation with nuclear power is, in part, motivated by the amazing power of the atom, the nuclear forces, and the importance of nuclear research for the advancement of science and technology.
Oh, and preferring the certainty of having a year or so lopped off your life (coal) vs. the improbable chance of a nuclear disaster is entirely rational. That's the reason why farmers use futures, and other risk-reduction measures which also entail a fixed cost.
By the way, the latest headline: Japanese authorities drop plans to dump water by helicopter (called a "desperate attempt" by NHK) was called off because of the risk.
Thing is, at every stage of this thing the Japanese authorities, nuclear industry experts, and the resident Slashdot advocates have been saying "move along, nothing to see here", and at every stage, there has been another development proving them wrong. I would have thought there would have been some rethinking, but apparently not.
Sorry, but I think you naively think that nuclear power is run by altruistic scientists.
They're not. They're run by corporations who want to privatize profits and socialize risks. Far, far from any kind of free market. And within those corps are the same kind of MBA/marketing types that geeks detest otherwise. These are the same kinds of people who spread light and goodness in the financial markets.
What RMS is warning about is a future in which there are (practically) no normal books.
We've seen how much competition there is in broadband Internet in the US: usually a choice between tweedledee and tweedledum, both with onerous restrictions.
Let's say a tsunami warning goes off, people heed the warning and head to high ground. The disaster averted, but it wouldn't make any sense to say that the warning itself was useless because the disaster didn't come to pass.
Similarly, we're not quite at a disaster situation with ebooks, but we could be at some point. If the disaster is avoided, it'll be because of clarions like RMS sounding. And it'll be avoided because of people applying pressure (consumer or governmental) because they've been influenced by ideas similar to those in The Right to Read.
Slashdot Mirror
Developers don't find business cards useful because they're not doing business (meeting customers, drumming up new ones, negotiating contracts, meeting with zoning, local, or state officials, etc.). Developers, on the other hand, develop.
Not to Wiki you, but do you have a few links for that (genuinely interested).
Also, did people donate via Paypal, or other means?
>Because the US has handled all their disasters with flying colors....just shut up already USA.
How about, instead of making this about a jingoistic Japan vs. US thing, making it about people vs. politicians generally?
Did you see the video of them dropping water on the reactor? What a joke.
They said it was 7 tons. 1 ton == 1000 L. That's like 50 or so of those office water things. Multiply by 7.
Did they seriously expect some serious cooling with that? Anybody with any smarts is going to go far away before the authorities fess up to the extent of the problem.
Seems like a good geeky hobby.
Any links to good information?
I'm looking for some basic information. Basic as in "at the base". Like if you know the ASM or C pointer background of what a variable and function call really are, you more easily understand any language.
So stuff like, what's DVB? Symbol rate? How are channels established? Etc.
Somebody mod the parent up, he posted as Anonymous.
Amazing how the NATsi's modded him to -1 for bringing up the idea. Just goes to prove his point.
Wait, maybe I don't understand correctly, but are you saying that some disability "advocates" are saying that schools can't use headphones because that would mean fully-abled students can experience something that the disabled (deaf) can't?
While I support disability access where that wouldn't cost much more than standard access, it's not possible to provide the range of sensory experience to a disabled student that's available to a fully-abled student.
What distros have an espeak device? Or is it set up when you install festival?
Good that ExtJS is working for you.
Back a while ago (few years ago), I would go to dojotoolkit.org, check out the demo, and wonder if Dojo was slow for everybody, or was it just me?
The funny thing is, because I guess schoolmarms aren't teaching these handy rules anymore, people are hypercorrecting themselves where they don't even need to:
"me" is seen as a indicator of lower status, like "ain't", so people just use I where it doesn't fit:
"They gave my wife and I a gift." Wrong.
Split them up, and then see if it works:
"They gave my wife a gift." OK.
"They gave I a gift." ??
Should be:
"They gave me a gift."
Together:
"They gave me and my wife a gift."
tl;dr (but bookmarked). You win.
In what category of animal does ExtJs fit vs. jQuery combined with jQuery UI?
jQuery has basically broken away from the pack from other Javascript toolkits/frameworks/libraries. (Which is not to say they all have the same purpose.)
When you've got a lot of players in the field, and have to decide what to use, and are also thinking about new devs already being familiar with a package, going with the market leader seems to be what most people will do.
The $ and css-based selector syntax of jQuery makes it highly welcoming for devs that have to learn Yet Another Library. See also.
Wow, a 10:1 ratio, much more than the 2:1 (with caching) using a simple ab test from the serverfault link.
Reading the responses above, I'm thinking that a happy medium is:
-HTTPS for login for free users. Has the risk of sessionjacking
-Ask for old password before changing password or major actions like "delete all"
-HTTPS by default or by option for paid users.
Interesting. I'll bet you you had some kind of time convincing the client that hours billed for that research were worth it. ("If you're such a great developer, you should already know that")
Good point. Are browsers still putting out the notorious "not all elements on this page are SSL" errors they used to?
True for the sessionjacking.
Thinking out loud: I'd think a way to prevent password changes would be to require you to enter the old password in order to change the password, like passwd does.
>Whomever would pay
Apologies in advance, but in the great Slashdot tradition of going off on a grammer* tangent:
It is'nt "whomever" would pay, it's "whoever". Whom would be used if it were the object of the verb, which it's not. It's the subject. You can tell by substituting "he/him" for "who/whom": "Him would pay" doesn't make sense. "He would pay" does, and he is nominative.
An example of a subject would be:
To "whom" should this prize be given?
Give "him" this prize.
Whom and him are both objects of the verb give.
* Yes, grammer (and another word) is misspelt on purpose to attract the inevitable "you misspelled grammar" response, also a hallmark of grammar Nazi posts.
Back some years ago, there was talk about dedicated SSL hardware. What's the performance penalty for HTTPS anymore?
Say you're a small startup running your "the next Twitter" app on a Xen or OpenVZ VPS instance.
What's the hit for HTTPS?
Any thoughts on HTTPS only for the login page, or for all pages?
Would you rather lose a few years off your old age (after having retired from a career and seen and played with your grandkids), or face a very small chance of dying soon after a devastating nuclear disaster?
Joe Schmoe has chosen the former, and it's entirely logical. Known risk vs. small chance of catastrophe.
>Yes, accidents will, from time to time, occur that you *cannot* plan for.
Well, that's actually the point antis are trying to make. What'll happen if a bomb detonates at a solar thermal plant? A big mess, but not much more. Compare to nuclear.
The problem with that is nuke plants generate huge amounts of waste heat. And oceans are great for dissipating heat. And many faultlines are near coasts.
All throughout this thread, posters have been making fun of "Joe Sixpack", so forgive me if I balance things out:
There are certain kinds of visceral things that normal people get, but which geeks struggle with. However, just because geeks don't understand a particular argument doesn't make it any less valid.
I think the infatuation with nuclear power is, in part, motivated by the amazing power of the atom, the nuclear forces, and the importance of nuclear research for the advancement of science and technology.
Oh, and preferring the certainty of having a year or so lopped off your life (coal) vs. the improbable chance of a nuclear disaster is entirely rational. That's the reason why farmers use futures, and other risk-reduction measures which also entail a fixed cost.
By the way, the latest headline: Japanese authorities drop plans to dump water by helicopter (called a "desperate attempt" by NHK) was called off because of the risk.
Thing is, at every stage of this thing the Japanese authorities, nuclear industry experts, and the resident Slashdot advocates have been saying "move along, nothing to see here", and at every stage, there has been another development proving them wrong. I would have thought there would have been some rethinking, but apparently not.
Sorry, but I think you naively think that nuclear power is run by altruistic scientists.
They're not. They're run by corporations who want to privatize profits and socialize risks. Far, far from any kind of free market. And within those corps are the same kind of MBA/marketing types that geeks detest otherwise. These are the same kinds of people who spread light and goodness in the financial markets.
What RMS is warning about is a future in which there are (practically) no normal books.
We've seen how much competition there is in broadband Internet in the US: usually a choice between tweedledee and tweedledum, both with onerous restrictions.
Let's say a tsunami warning goes off, people heed the warning and head to high ground. The disaster averted, but it wouldn't make any sense to say that the warning itself was useless because the disaster didn't come to pass.
Similarly, we're not quite at a disaster situation with ebooks, but we could be at some point. If the disaster is avoided, it'll be because of clarions like RMS sounding. And it'll be avoided because of people applying pressure (consumer or governmental) because they've been influenced by ideas similar to those in The Right to Read.