I would like to see your dream made a reality. The reason we build killing machines is so that we can protect ourselves from other peoples' killing machines. If you were to merely conquer the world and make yourself emperor, there would be nobody "else" to defend ourselves against.
So get right on that. Make your vision of peace a reality. You might want to start by building some killing machines.
Not really. Google lets me use my own domain with gmail.
as well as a huge database of Q&A.
What? Are you talking about Yahoo Answers, that game where somebody posts a fake question and people compete to see who can come up with the funniest fake answer? Could be useful if you want to find out "how is babby formed," I guess.
Every desktop email client from mutt to Outlook supports S/MIME. BlackBerry and Windows Mobile support S/MIME. The iPhone is the odd one out. This is just one of many reasons it's considered a toy by large enterprises.
It's key management and distribution, not cost. The costs are very low. Training everyone to exchange S/MIME keys, for example, is just too damn hard.
When email clients can automatically look up other peoples' certificates using DNS, then encryption will hit the main-stream.
(Oh, and bass-ackward companies like Apple are also holding back encryption. The iPhone can't do Secure Email after all this time? Really, Apple? Really?)
It is a serious flaw in FireFox that a crashign plug-in brings down the entire browser and all tabs. Yes, applications and plug-ins are going to have bugs. Software architects should take this into account when designing things. FireFox's architects seem not to have done so.
If the browser had a decent plug-in architecture, a crash of a plug-in would crash ONLY THE PLUG-IN. The rest of the browser would keep running.
It follows that FireFox does not have a decent plug-in architecture.
Furthermore, a good application design would allow a single page/tab to crash without bringing down all the other pages/tabs. Again, FireFox's architecture is lacking in this regard.
MegaCorps suck the souls out of employees, as they wither away doing the same thing day after day while being accosted constantly by wasteful internal politics. The best of the MegaCorps, like Google, will even give you "20% time" so that they can own the rights to your own best ideas.
...and those they hire at that rate will be less experienced than interns, while having "educations" from one of India's fine "engineer factories" (which lack even ITT's credibility)... often in unrelated fields.
The slowness in App Engine comes from when they load and unload your app. This does take a long time no matter how your code is written. If your app is already loaded because someone else has accessed within the past 60 seconds, it will respond in under two seconds, as you say.
If AppEngine were not oversold they would not have to load/unload apps constantly.
Having the government assist in connecting employers with employees is a public investment in economic infrastructure. It fits the very definition of capitalism as per Adam Smith.
Furthermore, it could allow them to better manage the unemployment benefit system to cut down on abuse of this social safety net.
I have friends in India. I discussed IT salary differences with them. I said "this web page says you can get software engineers for $5k/year in India. Is that for real?"
I was told that that's bullshit and that Indian professionals actually earn in excess of $20,000 per year. $5k/year would only buy interns with no education and no experience, from what my friends in Bangalore tell me.
An over-sold server cluster becomes slow, just like an over-sold network connection. Peak demand outstrips the "expected" number of apps running at any particular moment.
That's a bad analogy. A better one would be: Hosting in "the cloud" rather than in your own datacenter is like taking a taxi instead of buying a car and hiring a full-time driver.
Some part of "cloud computing" does involve over-selling of server resources. Google's App Engine is so over-sold it can take 20 seconds for a page to load. However, Amazon's service allows you to reserve dedicated hosts for a premium price.
And, really, being over-sold isn't a problem so long as things are managed right. A project on the scale of Amazon's should be able to afford the best engineers so that such things are managed properly.
OR we will have to build robots to tend to our old people. We will stick them in FEMA trailers and let the robots take care of them. Imagine roombas rolling around the trailer park carrying pill cups.
And if they don't like it, they should have balanced the fucking budget of our nation rather than dumping their debts on us.
Hey boys! This feller here is calling himself "IT Ninja" but he doesn't know the difference between java and javascript! I say we run him outa slashdot!
What jumped the shark is the idea of using a notebook keyboard regularly.
Notebooks are getting really small now. This is because smaller = better mobility. Mobility trumps everything when you're traveling. When you're not traveling and mobility is not important, plug in a REAL monitor and a REAL keyboard to your notebook.
If you do NOT want your notebook to be optimized for mobility, well... that's a PEBKAC problem, not a design flaw in the device.
Riiight... which "user error" are you proposing would cause choppy flash video in Firefox but not in Chrome or IE?
This is a common problem. It has been suggested that Firefox's "feature" to save state info to recover from crashes is to blame. No matter what, they should catch this stuff in QA.
Slashdot Mirror
Wait... don't blind people have big dogs? Why use guns when you could merely attach a frikin laser...
I would like to see your dream made a reality. The reason we build killing machines is so that we can protect ourselves from other peoples' killing machines. If you were to merely conquer the world and make yourself emperor, there would be nobody "else" to defend ourselves against.
So get right on that. Make your vision of peace a reality. You might want to start by building some killing machines.
OK, possibly.
Not really. Google lets me use my own domain with gmail.
What? Are you talking about Yahoo Answers, that game where somebody posts a fake question and people compete to see who can come up with the funniest fake answer? Could be useful if you want to find out "how is babby formed," I guess.
OK, now I know you're just fucking with us.
Every desktop email client from mutt to Outlook supports S/MIME. BlackBerry and Windows Mobile support S/MIME. The iPhone is the odd one out. This is just one of many reasons it's considered a toy by large enterprises.
SSL is not email encryption. S/MIME and PGP are email encryption. All business-class smartphones can do S/MIME.
That's not email encryption. That's network encryption. S/MIME, which BlackBerry and Windows Mobile support, is email encryption.
It's key management and distribution, not cost. The costs are very low. Training everyone to exchange S/MIME keys, for example, is just too damn hard.
When email clients can automatically look up other peoples' certificates using DNS, then encryption will hit the main-stream.
(Oh, and bass-ackward companies like Apple are also holding back encryption. The iPhone can't do Secure Email after all this time? Really, Apple? Really?)
It is a serious flaw in FireFox that a crashign plug-in brings down the entire browser and all tabs. Yes, applications and plug-ins are going to have bugs. Software architects should take this into account when designing things. FireFox's architects seem not to have done so.
If the browser had a decent plug-in architecture, a crash of a plug-in would crash ONLY THE PLUG-IN. The rest of the browser would keep running.
It follows that FireFox does not have a decent plug-in architecture.
Furthermore, a good application design would allow a single page/tab to crash without bringing down all the other pages/tabs. Again, FireFox's architecture is lacking in this regard.
MegaCorps suck the souls out of employees, as they wither away doing the same thing day after day while being accosted constantly by wasteful internal politics. The best of the MegaCorps, like Google, will even give you "20% time" so that they can own the rights to your own best ideas.
...and those they hire at that rate will be less experienced than interns, while having "educations" from one of India's fine "engineer factories" (which lack even ITT's credibility)... often in unrelated fields.
The slowness in App Engine comes from when they load and unload your app. This does take a long time no matter how your code is written. If your app is already loaded because someone else has accessed within the past 60 seconds, it will respond in under two seconds, as you say.
If AppEngine were not oversold they would not have to load/unload apps constantly.
Having the government assist in connecting employers with employees is a public investment in economic infrastructure. It fits the very definition of capitalism as per Adam Smith.
Furthermore, it could allow them to better manage the unemployment benefit system to cut down on abuse of this social safety net.
I have friends in India. I discussed IT salary differences with them. I said "this web page says you can get software engineers for $5k/year in India. Is that for real?"
I was told that that's bullshit and that Indian professionals actually earn in excess of $20,000 per year. $5k/year would only buy interns with no education and no experience, from what my friends in Bangalore tell me.
An over-sold server cluster becomes slow, just like an over-sold network connection. Peak demand outstrips the "expected" number of apps running at any particular moment.
That's a bad analogy. A better one would be: Hosting in "the cloud" rather than in your own datacenter is like taking a taxi instead of buying a car and hiring a full-time driver.
Some part of "cloud computing" does involve over-selling of server resources. Google's App Engine is so over-sold it can take 20 seconds for a page to load. However, Amazon's service allows you to reserve dedicated hosts for a premium price.
And, really, being over-sold isn't a problem so long as things are managed right. A project on the scale of Amazon's should be able to afford the best engineers so that such things are managed properly.
OR we will have to build robots to tend to our old people. We will stick them in FEMA trailers and let the robots take care of them. Imagine roombas rolling around the trailer park carrying pill cups.
And if they don't like it, they should have balanced the fucking budget of our nation rather than dumping their debts on us.
Hey boys! This feller here is calling himself "IT Ninja" but he doesn't know the difference between java and javascript! I say we run him outa slashdot!
And the overstatement-of-the-year award goes to...
What jumped the shark is the idea of using a notebook keyboard regularly.
Notebooks are getting really small now. This is because smaller = better mobility. Mobility trumps everything when you're traveling. When you're not traveling and mobility is not important, plug in a REAL monitor and a REAL keyboard to your notebook.
If you do NOT want your notebook to be optimized for mobility, well... that's a PEBKAC problem, not a design flaw in the device.
What? Are you trying to say you expect something to replace Rack as the standard for web app middleware?
It's such a simple protocol, and it has such widespread support, it's hard to imagine.
I can't imagine how you manage to live your life without SMTP. Or have you convinced everyone you correspond with to use S/MIME?
What you want is called Rack. Apache with mod_rack becomes just a simple request handler to interface with any Rack-able framework.
There are several other lighter-weight webservers which support Rack.
It's pretty clear that nearly all of Apache's features are becoming vestigial now that a simple, standardized interface to the web-app layer exists.
http://rack.rubyforge.org/
RIP, Apache. You were wonder in your time.
Riiight... which "user error" are you proposing would cause choppy flash video in Firefox but not in Chrome or IE?
This is a common problem. It has been suggested that Firefox's "feature" to save state info to recover from crashes is to blame. No matter what, they should catch this stuff in QA.