Perhaps not, but Gnumeric has a better reputation for accuracy than either of them. That's gotta count for something in an application designed to manipulate numbers.
(Heck, Windows has pretty much _always_ had one of the most responsive UIs.)
Bwahahahaha! Oh, you kill me! It might've been snappier than, say, GEOS, but Windows has always had a reputation for sluggish desktop response. Not that Linux is perfect by any means, but those of us who cut our teeth on AmigaOS or BeOS or older MacOS and were spoiled early on by actual responsive GUIs are having a hard time taking your claim seriously.
Because they're pathologically incapable of the job? As one who tried to make Palm Desktop work on OS X way back when, I'd like to say that it was better than nothing - except that it wasn't.
I've had a chiropractor tell me directly and seriously that he could have cured my appendicitis. I just smiled, backed away, and left ASAP. But as you described, I can at least imagine a physical mechanism by which manipulating joints and muscles can correct a mechanical problem in them. After all, doctors can set dislocated shoulders and other joints, right? It doesn't fly in the face of basic physics or common sense.
But I'm still glad that my parents took me to a surgeon to fix my appendix.
If you've spent some time working with photographers, you know that moving a light just a tiny bit can dramatically change how much someone appears to weigh. Changing the colour of light - or even the colour of other nearby objects that reflect some light - can change someone from vibrant to sickly. And don't even get started on makeup.
Those are bad examples, in that even if the result is a statistically improbable image, it is provably possible for that model to take on that appearance under those specific conditions. That's not in the same league image manipulations that give results that the model could never achieve without alterations to their anatomy.
I think it's a two-fold problem. One, the complexities of a GUI makes codes many times more intricate, making the job more difficult (and more error prone), but also, programmers today look at problems differently.
They sure do! Naive new programmers used to write programs that handled large amounts of data as batch jobs. Naive new programmers write programs that handled large amounts of data as event-driven GUI constructs. Hint: MVC. Second hint: MVC. Need another: MVC.
Even GUI code can be pretty simple when you enforce a strict separation between the interface and the backend. Write your underlying code first and get it perfected (or as perfect as your time and money budgets allow), and only then write a GUI to interact with it. It's OK to integrate the two if you're writing yet another paint program, but that isn't the kind of project you're dealing with here.
Pro tip: maintain a list of everything you do: bugs you've closed, features you've added, projects you've planned, servers you've upgraded, or whatever else you've worked on. The next time your boss asks if you've been busy, you'll be glad to have a precise and detailed answer.
But nobody seems to realize that for the same reason, it's equally misleading to compare it to "sharing" as we were taught to do as kids.
For most of us "sharing" means "here, take part of mine and we'll both have some". By contrast, you seem to have grown up "sharing" your lunch money with the school bully. You're looking for "giving".
Because I'm sure my Linux on [insert device here] port will look just fine on CodePlex.
Hmm. MS's recommended migration path from Visual FoxPro is to.NET and SQL Server. I wrote a tool to simplify migration of VFP databases to PostgreSQL instead. Wonder if they'd like to host it for me?
Would it be possible that all the four regular doctors you saw before the chiropractor were incompetent?
Not really, no. One of the advantages of being married to a doctor is that you can usually get in to see even the best, most heavily booked specialists. They all followed the standard treatment regimens, but in my case it was utterly ineffective.
I was helping a friend move, and wrenched my lower back carrying an old, heavy washing machine. I went through hell for about 3 months afterward. I'm not talking about "my back got stiff", or "I had to take 3 Advil instead of 2!" I'm talking about going to sleep at 10PM on a cocktail of naproxen, Flexeril, and codeine, then waking up at 2AM sobbing in agony as someone shoved a rusty icepick into my spine and pried it open.
I saw my family doctor, an osteopath, and two orthopedic surgeons. They were all very nice and sympathetic, but their treatments never got me more than 4 hours of sleep. By the end of the 3 months, I understood why people kill themselves to escape the pain.
My dad suggested that I go to his chiropractor. Dad was a healthy skeptic, but he'd had good luck with the guy and argued that in the worst case I'd be out $20. At that point, I'd have tried just about anything. I went to Dr. Palmer (coincidental; no relation to the quack) and he ran one of those debunked spinal alignment meter things up my back. I rolled my eyes when he told me he found the problem, then told me to relax so he could pop my back.
I don't remember if I screamed or not, but I might've.
Within 20 minutes, the rusty icepick had turned into a toothpick. That night, I got 12 hours of uninterrupted, drug-free sleep, and by the next morning I was completely pain free.
Go ahead and write that off with a smug "correlation isn't causation!" I know that. I also know that one nearly-retired chiropractor probably saved me from killing myself with one single $20 adjustment. Again, if I wasn't clear, this wasn't some subjective case of "it kind of hurts when I do this", but a grown man waking up crying tears of pain after a few hours of tortured sleep. Say what you will about chiropractors in general, but that one specific practitioner knew exactly how to fix what was wrong with me when a lot of other doctors had failed.
I love traditional medicine. I'm an ex-Navy surgery tech, and my wife's a surgeon. My college degrees are in science and I'm about as skeptical of pseudoscience as you can get. The scientist in me tells the naysayers to kiss my butt, because my empirical data from the outcome of that experiment holds more weight with me than the sophistic claims that it couldn't possibly have worked.
No, chiropractors can't cure deafness or appendicitis or pneumonia, and the practitioners who claim otherwise are unmitigated quacks. Still, I'd be the first to testify that at least some of them are very skilled in treating certain very specific musculoskeletal conditions.
Ron, first, thanks for commenting. Second, are you joking? Highlights:
The thing you have to remember, is that Touch, Multi-Touch, and Pen are all already supported in the core of the Windows 7 operating system. This isn't a small feat. No other OS has that today. The bigger fact is that we have had that for over a year now.
For the benefit of iPhone and iTouch owners, could you please explain what Win7 has that we haven't been using for a few decades? I ask because it's not at all obvious from the names that these are new technologies. I've used touch (non-TM), multi-touch (non-TM), and pen (non-TM) inputs from a light pen in the '70s to a Palm Pilot in the mid-'90s. What is it about those named systems that should make me, as a programmer or user, say "I've gotta get me some of that?"
I don't mean that trollishly. It's just that, once again, your employer picked horrible, non-descriptive product names, and they haven't gone out of their way to explain to users why we should want to use that. Links in journals don't count. Sell to me! Get me interested in this! As it stands, you can't be too surprised that people are unexcited when you say "we've got Touch and Pen now!" Reaction from the crowd: "welcome to the game!"
If you want to give credit where credit is due.... you should all say Wayne Westerman and not Apple. He is the genius that Apple bought and brought over to save their failing tablet and turn it into a phone.
Were I an ass, I'd say:
"If you want to give credit where credit is due.... you should all say Ron George and not Microsoft. He is the genius that Microsoft bought and brought over to save their failing input device R&D project and turn it into Windows 7 bullet point.
Maybe the genius part was that Apple and Microsoft recognized talented people, brought them in, and gave them free rein to develop their visions. By your standard, neither company is particularly good because all of their best work was developed by talented employees. That logic doesn't reduce very well.
Touchscreens are a fun idea but except for very specific cases (pocketable computers, public terminals a la ticket machines at train stations for instance) they're horrible in practice.
I freakin' hate them at credit card terminals. There are some nice keypad terminals with shields around the sides so that a touch typist can enter their PIN without looking and without anyone else being able to see. Then there are the giant touchscreen keypads where you're entering your PIN by tapping high contrast 2 inch square buttons so that the guy stocking eggs at the back of the store can watch you enter it. The idiot who designed those, and the managers that signed off on the project, should be summarily fired and executed - not necessarily in that order.
To expect anything one would need to know who Robert Mapplethorpe is. Not everyone is familiar with gay S&M art.
Everyone was a few years ago when public funding for his works was a big public debate. Even without that knowledge, astute younger readers might have picked up that he was being used as the counterexample: "his work was only rated PG, OMG WTF!"
Granted, but you don't expect to see goatse-like images linked directly from an article on Slashdot.
That's exactly what I expect to find linked directly from an article on Slashdot. Why do you think no one reads the articles?
Seriously, though, the subject at hand is the censorship of Robert Mapplethorpe. Were you expecting pink unicorns and daffodils? Well, the pink unicorns perhaps, but only in the context of gay S&M.
Don't be a dumbass. First, this is the Internet and there are unpleasant things here. Second, if your temperament or employer can't handle you looking at grownup stuff, then don't fucking click links labeled "not for the fainthearted". Take a little responsibility for yourself and quit blaming others when your common sense fails you.
Slashdot Mirror
OOo can't do as much as Excel can.
Perhaps not, but Gnumeric has a better reputation for accuracy than either of them. That's gotta count for something in an application designed to manipulate numbers.
(Heck, Windows has pretty much _always_ had one of the most responsive UIs.)
Bwahahahaha! Oh, you kill me! It might've been snappier than, say, GEOS, but Windows has always had a reputation for sluggish desktop response. Not that Linux is perfect by any means, but those of us who cut our teeth on AmigaOS or BeOS or older MacOS and were spoiled early on by actual responsive GUIs are having a hard time taking your claim seriously.
Yeah, actually including two wars in your budget will do that.
They weren't included in Bush's budget?
As you may know, Neodyne Inexpensive
Analogy fail.
(I keed, I keed.)
Why can't Palm write their own syncing program?
Because they're pathologically incapable of the job? As one who tried to make Palm Desktop work on OS X way back when, I'd like to say that it was better than nothing - except that it wasn't.
I've had a chiropractor tell me directly and seriously that he could have cured my appendicitis. I just smiled, backed away, and left ASAP. But as you described, I can at least imagine a physical mechanism by which manipulating joints and muscles can correct a mechanical problem in them. After all, doctors can set dislocated shoulders and other joints, right? It doesn't fly in the face of basic physics or common sense.
But I'm still glad that my parents took me to a surgeon to fix my appendix.
If you've spent some time working with photographers, you know that moving a light just a tiny bit can dramatically change how much someone appears to weigh. Changing the colour of light - or even the colour of other nearby objects that reflect some light - can change someone from vibrant to sickly. And don't even get started on makeup.
Those are bad examples, in that even if the result is a statistically improbable image, it is provably possible for that model to take on that appearance under those specific conditions. That's not in the same league image manipulations that give results that the model could never achieve without alterations to their anatomy.
Some people use Windows because they prefer it and it works better for them.
Extraordinary claims call for extraordinary evidence.
I think it's a two-fold problem. One, the complexities of a GUI makes codes many times more intricate, making the job more difficult (and more error prone), but also, programmers today look at problems differently.
They sure do! Naive new programmers used to write programs that handled large amounts of data as batch jobs. Naive new programmers write programs that handled large amounts of data as event-driven GUI constructs. Hint: MVC. Second hint: MVC. Need another: MVC.
Even GUI code can be pretty simple when you enforce a strict separation between the interface and the backend. Write your underlying code first and get it perfected (or as perfect as your time and money budgets allow), and only then write a GUI to interact with it. It's OK to integrate the two if you're writing yet another paint program, but that isn't the kind of project you're dealing with here.
Pro tip: maintain a list of everything you do: bugs you've closed, features you've added, projects you've planned, servers you've upgraded, or whatever else you've worked on. The next time your boss asks if you've been busy, you'll be glad to have a precise and detailed answer.
That being said, from what I hear the problem requires an 8+ CPU system and most/all of the CPUs under high load.
Our 8-core database server has been marching along happily under a heavy load for many months now.
Schools should focus on "The three Rs"
"Ritalin, Restraints, and Repetition"?
But nobody seems to realize that for the same reason, it's equally misleading to compare it to "sharing" as we were taught to do as kids.
For most of us "sharing" means "here, take part of mine and we'll both have some". By contrast, you seem to have grown up "sharing" your lunch money with the school bully. You're looking for "giving".
Actually, my project's under GPLv3 so they won't host it. I guess MS doesn't like the extra patent protections.
Because I'm sure my Linux on [insert device here] port will look just fine on CodePlex.
Hmm. MS's recommended migration path from Visual FoxPro is to .NET and SQL Server. I wrote a tool to simplify migration of VFP databases to PostgreSQL instead. Wonder if they'd like to host it for me?
The speed of a 15k drive means that the outer edge of the 3 1/2" drive is spinning pretty fast... getting close to the speed of sound
3.5in * 3.14 * 15000r/m * 60m/h * 1ft/12in * 1mi/5280ft = 156mi/h
That's still pretty fast, but not nearly the speed of sound at STP.
Would it be possible that all the four regular doctors you saw before the chiropractor were incompetent?
Not really, no. One of the advantages of being married to a doctor is that you can usually get in to see even the best, most heavily booked specialists. They all followed the standard treatment regimens, but in my case it was utterly ineffective.
My own anecdote:
I was helping a friend move, and wrenched my lower back carrying an old, heavy washing machine. I went through hell for about 3 months afterward. I'm not talking about "my back got stiff", or "I had to take 3 Advil instead of 2!" I'm talking about going to sleep at 10PM on a cocktail of naproxen, Flexeril, and codeine, then waking up at 2AM sobbing in agony as someone shoved a rusty icepick into my spine and pried it open.
I saw my family doctor, an osteopath, and two orthopedic surgeons. They were all very nice and sympathetic, but their treatments never got me more than 4 hours of sleep. By the end of the 3 months, I understood why people kill themselves to escape the pain.
My dad suggested that I go to his chiropractor. Dad was a healthy skeptic, but he'd had good luck with the guy and argued that in the worst case I'd be out $20. At that point, I'd have tried just about anything. I went to Dr. Palmer (coincidental; no relation to the quack) and he ran one of those debunked spinal alignment meter things up my back. I rolled my eyes when he told me he found the problem, then told me to relax so he could pop my back.
I don't remember if I screamed or not, but I might've.
Within 20 minutes, the rusty icepick had turned into a toothpick. That night, I got 12 hours of uninterrupted, drug-free sleep, and by the next morning I was completely pain free.
Go ahead and write that off with a smug "correlation isn't causation!" I know that. I also know that one nearly-retired chiropractor probably saved me from killing myself with one single $20 adjustment. Again, if I wasn't clear, this wasn't some subjective case of "it kind of hurts when I do this", but a grown man waking up crying tears of pain after a few hours of tortured sleep. Say what you will about chiropractors in general, but that one specific practitioner knew exactly how to fix what was wrong with me when a lot of other doctors had failed.
I love traditional medicine. I'm an ex-Navy surgery tech, and my wife's a surgeon. My college degrees are in science and I'm about as skeptical of pseudoscience as you can get. The scientist in me tells the naysayers to kiss my butt, because my empirical data from the outcome of that experiment holds more weight with me than the sophistic claims that it couldn't possibly have worked.
No, chiropractors can't cure deafness or appendicitis or pneumonia, and the practitioners who claim otherwise are unmitigated quacks. Still, I'd be the first to testify that at least some of them are very skilled in treating certain very specific musculoskeletal conditions.
Ron, first, thanks for commenting. Second, are you joking? Highlights:
The thing you have to remember, is that Touch, Multi-Touch, and Pen are all already supported in the core of the Windows 7 operating system. This isn't a small feat. No other OS has that today. The bigger fact is that we have had that for over a year now.
For the benefit of iPhone and iTouch owners, could you please explain what Win7 has that we haven't been using for a few decades? I ask because it's not at all obvious from the names that these are new technologies. I've used touch (non-TM), multi-touch (non-TM), and pen (non-TM) inputs from a light pen in the '70s to a Palm Pilot in the mid-'90s. What is it about those named systems that should make me, as a programmer or user, say "I've gotta get me some of that?"
I don't mean that trollishly. It's just that, once again, your employer picked horrible, non-descriptive product names, and they haven't gone out of their way to explain to users why we should want to use that. Links in journals don't count. Sell to me! Get me interested in this! As it stands, you can't be too surprised that people are unexcited when you say "we've got Touch and Pen now!" Reaction from the crowd: "welcome to the game!"
If you want to give credit where credit is due.... you should all say Wayne Westerman and not Apple. He is the genius that Apple bought and brought over to save their failing tablet and turn it into a phone.
Were I an ass, I'd say:
"If you want to give credit where credit is due.... you should all say Ron George and not Microsoft. He is the genius that Microsoft bought and brought over to save their failing input device R&D project and turn it into Windows 7 bullet point.
Maybe the genius part was that Apple and Microsoft recognized talented people, brought them in, and gave them free rein to develop their visions. By your standard, neither company is particularly good because all of their best work was developed by talented employees. That logic doesn't reduce very well.
Touchscreens are a fun idea but except for very specific cases (pocketable computers, public terminals a la ticket machines at train stations for instance) they're horrible in practice.
I freakin' hate them at credit card terminals. There are some nice keypad terminals with shields around the sides so that a touch typist can enter their PIN without looking and without anyone else being able to see. Then there are the giant touchscreen keypads where you're entering your PIN by tapping high contrast 2 inch square buttons so that the guy stocking eggs at the back of the store can watch you enter it. The idiot who designed those, and the managers that signed off on the project, should be summarily fired and executed - not necessarily in that order.
To expect anything one would need to know who Robert Mapplethorpe is. Not everyone is familiar with gay S&M art.
Everyone was a few years ago when public funding for his works was a big public debate. Even without that knowledge, astute younger readers might have picked up that he was being used as the counterexample: "his work was only rated PG, OMG WTF!"
Macbook, Starcraft, Peggle... Are those fair use applications?
More to the point: did he try to pass them off as his own? No.
Granted, but you don't expect to see goatse-like images linked directly from an article on Slashdot.
That's exactly what I expect to find linked directly from an article on Slashdot. Why do you think no one reads the articles?
Seriously, though, the subject at hand is the censorship of Robert Mapplethorpe. Were you expecting pink unicorns and daffodils? Well, the pink unicorns perhaps, but only in the context of gay S&M.
Don't be a dumbass. First, this is the Internet and there are unpleasant things here. Second, if your temperament or employer can't handle you looking at grownup stuff, then don't fucking click links labeled "not for the fainthearted". Take a little responsibility for yourself and quit blaming others when your common sense fails you.
Heaven forbid they try to make money off of it instead of offering insane 15 year + support.
FreeBSD started as a branch of BSD, which began around 1977. Somehow a group of volunteers manages to support 32 year old code.