I agree completely. I used to have a bit of a chip on my shoulder about people with CS degrees, since I do programming with a math background, no formal CS. Since I discovered the number of people with masters degrees in CS who can't give reasonable answers to trivial CS interview questions I've chilled out.
I'd almost say anyone with a masters in CS is likely to not be much of a coder; if they were good at it, why did they stick around in school longer then they had to, when they could go get paid well to solve interesting problems?
Credentialist restrictions are much more common in science, so getting a post-graduate degree there might make slightly more sense, and thus have a more positive correlation with qualities you want in a scientist.
Are you kidding? The only Google services you mention I ever use are search and maps. Both have perfectly reasonable alternatives.
Do you actually click on google ads? Why?
Now, I'm not arguing Google isn't innovative. They innovate, they just don't ever finish anything (except search).
Success is 5% inspiriation, 95% perspiration. Google has clearly hired inspired developers, I've never been convinced they've figured out how to focus most of those developers on things that make money.
From a distant perspective, Chandler looks like it's trying to be an Outlook or Evolution clone. If you think that's what's being attempted, the progress certainly hasn't been exciting.
Innovation is very much in the eye of the beholder, but Chandler's main "new" feature is its repository. It's there, it works.
Fundamentally, Chandler isn't trying to copy Outlook. It's a lot easier to copy than to create something really new. No disrespect intended towards the Ximian folks, they've done great work. But developing new standards and new architectures is really, really hard work, no one appreciates it until it's too late to change anything.
It would be interesting to compare the first 3 years' budgets of Ximian and OSAF. I expect that while OSAF started with more money in the bank, it wasn't paying that many coders until the last year or two.
While I agree with you that the Chandler team's initial vision didn't start as focused as it needed to get, your examples are really odd.
A once sentence description of Chandler might be, "A PIM that shares data between users with very low barrier to entry and allows data to be any combination of notes, tasks, events, and messages".
My memory is that RDF got thrown out pretty much right away, which is why it seems like an odd example to me. Besides, RDF still makes sense as an export target for a lot of Chandler's data, Chandler and RDF both allow for arbitrarily linked trees of information.
Jabber (XMPP) was (and still is) on the table because it's an IETF standard for instant messaging. XMPP's a very appealing way to do application level message passing.
"Firefox... developed quite quickly" is true from a very narrow point of view. In the larger context of Mozilla's growth, it was a long time coming. Writing Gecko took a long time.
Chandler's vision is fairly difficult because it's trying to invent a new architecture, allowing email, tasks, notes, and calendar items to merge fluidly. On the surface, this looks like Chandler's just going to be an Outlook or Evolution clone. If you think that's what's being attempted, the progress certainly hasn't been exciting.
At this point, Chandler's main "new" feature is its repository. It's there, it works. Admittedly it's somewhat slow because OSAF hasn't invested a lot of effort into optimization yet.
Of course, having a very general repository isn't very exciting until you start building actual interesting functionality on top of it. That functionality should be coming along fairly soon (3-6 months). It won't be polished for quite a while yet, though.
Hmm. Seems to me you're arguing that spousal homicide is extremely uncommon. Sure, it's not like every 10th spouse is dying every year, but it's a big deal, heck, approximately a third of all women murdered are murdered by an intimate.
Sadly, I've known several women murdered by their husbands, and I'm in no way involved in the domestic violence support field.
Here is a summary of a report on domestic violence in the US. An excerpt from the end:
Fatal intimate partner violence, 1976-2000
The number of men murdered by intimates dropped 68% between 1976 and 2000, the year of the most recently available data.
In 1976, an intimate murdered 1,357 men; in 2000, 440.
The number of women killed by an intimate was stable for two decades but declined after 1993. Between 1976 and 2000 the number of women murdered by intimates fell 22% from 1,600 to 1,247.
In recent years, generally, about 33% of female murder victims but 4% of the males were killed by an intimate.
Getting even further off-topic, battered women's shelters are attributed with much of the decline in spousal homicide.
Well, to continue the nitpick, a megagram is EXACTLY a metric ton, not slightly more. It does happen to be slightly more than an imperial short ton (and less than a long ton), but really, what scientist worth their salt thinks in imperial units?
So if your going to use Moore's "Law" to predict when a desktop computer will be able to run this sort of job on its own, you have to multiply by 1.5, 18 months per doubling, or slightly under 28 years.
I'm pretty dubious about using Moore's Trend that far in the future, though...
Every natural number has a unique prime factorization. Right?
This is a pretty fundamental concept in number theory.
So 4's prime factorization is:
2*2
If 1 was a prime, 4 could be factored as:
2*2*1, 2*2*1*1*1, etc.
So we DON'T define 1 as a prime. The definition of a prime is a natural number which has EXACTLY TWO unique factors over the natural numbers, 1 and itself. 1 doesn't satisfy this condition, it has only one unique factor over the naturals.
You're right that LIGO is basically an enormous Michalson interferometer, but in order to increase its apparent length it measures the superposition of a laser beam that has bounced back and forth across its length many times. As you say, the longer the path used, the more sensitivity to displacements in length it has.
But it is NOT true that LIGO can detect the gravitational pull of a human walking by the end of it. A litte background: gravitational waves are created by changes in the gravitational quadrupole moment of a system. Electromagnetic waves, in contrast, are created by changes in the electrical dipole moment of a system.
Getting changes in the quadrupole moment of a system requires doing something funky with the angular momentum of the system. That can happen when black holes collide (they radiate a bunch of their angular momentum away), and I don't know when else it might happen. But it definitely DOESN'T happen (on any reasonable scale) in any terrestrial processes, or any that we know of in our solar system.
It is true that a passing truck, or even a passing person, can cause mechanical vibrations that will affect LIGO's measurements. LIGO is an incredibly accurate system for measuring differences in distances between its perpendicular lengths. Gravitational waves should, according to GR, cause a change of length in one axis and not the other. Mechanical vibrations will also cause a difference in position for the mirrors, so LIGO has a VERY complicated system of mechanical dampers to minimize this effect.
Finally, the last time I checked, most GR experts were of the opinion that gravity waves propagate at the speed of light, not at infinite speed.
Vector assets are already supported on OS X. Vector assets aren't supported on iOS for performance reasons, but the APIs are the same.
Ignoring everything else in your apples to oranges comparison, your math is off by an order of magnitude.
$.07/kWh * 32,000kWh = $2,240, not $225.
I agree completely. I used to have a bit of a chip on my shoulder about people with CS degrees, since I do programming with a math background, no formal CS. Since I discovered the number of people with masters degrees in CS who can't give reasonable answers to trivial CS interview questions I've chilled out.
I'd almost say anyone with a masters in CS is likely to not be much of a coder; if they were good at it, why did they stick around in school longer then they had to, when they could go get paid well to solve interesting problems?
Credentialist restrictions are much more common in science, so getting a post-graduate degree there might make slightly more sense, and thus have a more positive correlation with qualities you want in a scientist.
Are you kidding? The only Google services you mention I ever use are search and maps. Both have perfectly reasonable alternatives.
Do you actually click on google ads? Why?
Now, I'm not arguing Google isn't innovative. They innovate, they just don't ever finish anything (except search).
Success is 5% inspiriation, 95% perspiration. Google has clearly hired inspired developers, I've never been convinced they've figured out how to focus most of those developers on things that make money.
It's called purchasing power parity.
Why do you think you need a job to put money in a Roth?
From a distant perspective, Chandler looks like it's trying to be an Outlook or Evolution clone. If you think that's what's being attempted, the progress certainly hasn't been exciting.
Innovation is very much in the eye of the beholder, but Chandler's main "new" feature is its repository. It's there, it works.
Fundamentally, Chandler isn't trying to copy Outlook. It's a lot easier to copy than to create something really new. No disrespect intended towards the Ximian folks, they've done great work. But developing new standards and new architectures is really, really hard work, no one appreciates it until it's too late to change anything.
It would be interesting to compare the first 3 years' budgets of Ximian and OSAF. I expect that while OSAF started with more money in the bank, it wasn't paying that many coders until the last year or two.
While I agree with you that the Chandler team's initial vision didn't start as focused as it needed to get, your examples are really odd.
A once sentence description of Chandler might be, "A PIM that shares data between users with very low barrier to entry and allows data to be any combination of notes, tasks, events, and messages".
My memory is that RDF got thrown out pretty much right away, which is why it seems like an odd example to me. Besides, RDF still makes sense as an export target for a lot of Chandler's data, Chandler and RDF both allow for arbitrarily linked trees of information.
Jabber (XMPP) was (and still is) on the table because it's an IETF standard for instant messaging. XMPP's a very appealing way to do application level message passing.
Full disclosure: I do work for OSAF
"Firefox ... developed quite quickly" is true from a very narrow point of view. In the larger context of Mozilla's growth, it was a long time coming. Writing Gecko took a long time.
Chandler's vision is fairly difficult because it's trying to invent a new architecture, allowing email, tasks, notes, and calendar items to merge fluidly. On the surface, this looks like Chandler's just going to be an Outlook or Evolution clone. If you think that's what's being attempted, the progress certainly hasn't been exciting.
At this point, Chandler's main "new" feature is its repository. It's there, it works. Admittedly it's somewhat slow because OSAF hasn't invested a lot of effort into optimization yet.
Of course, having a very general repository isn't very exciting until you start building actual interesting functionality on top of it. That functionality should be coming along fairly soon (3-6 months). It won't be polished for quite a while yet, though.
Sadly, I've known several women murdered by their husbands, and I'm in no way involved in the domestic violence support field.
Here is a summary of a report on domestic violence in the US. An excerpt from the end:
Getting even further off-topic, battered women's shelters are attributed with much of the decline in spousal homicide.
Well, to continue the nitpick, a megagram is EXACTLY a metric ton, not slightly more. It does happen to be slightly more than an imperial short ton (and less than a long ton), but really, what scientist worth their salt thinks in imperial units?
Perhaps Vthornheart was thinking of Canada and Mexico? Not generally thought of as part of the United States, but sometimes folks do forget...
>10000/0.02 = 5000000
>log2 = just less than 19
So if your going to use Moore's "Law" to predict when a desktop computer will be able to run this sort of job on its own, you have to multiply by 1.5, 18 months per doubling, or slightly under 28 years.
I'm pretty dubious about using Moore's Trend that far in the future, though...
Every natural number has a unique prime factorization. Right?
This is a pretty fundamental concept in number theory.
So 4's prime factorization is:
2*2
If 1 was a prime, 4 could be factored as:
2*2*1, 2*2*1*1*1, etc.
So we DON'T define 1 as a prime. The definition of a prime is a natural number which has EXACTLY TWO unique factors over the natural numbers, 1 and itself. 1 doesn't satisfy this condition, it has only one unique factor over the naturals.
You're right that LIGO is basically an enormous Michalson interferometer, but in order to increase its apparent length it measures the superposition of a laser beam that has bounced back and forth across its length many times. As you say, the longer the path used, the more sensitivity to displacements in length it has.
But it is NOT true that LIGO can detect the gravitational pull of a human walking by the end of it. A litte background: gravitational waves are created by changes in the gravitational quadrupole moment of a system. Electromagnetic waves, in contrast, are created by changes in the electrical dipole moment of a system.
Getting changes in the quadrupole moment of a system requires doing something funky with the angular momentum of the system. That can happen when black holes collide (they radiate a bunch of their angular momentum away), and I don't know when else it might happen. But it definitely DOESN'T happen (on any reasonable scale) in any terrestrial processes, or any that we know of in our solar system.
It is true that a passing truck, or even a passing person, can cause mechanical vibrations that will affect LIGO's measurements. LIGO is an incredibly accurate system for measuring differences in distances between its perpendicular lengths. Gravitational waves should, according to GR, cause a change of length in one axis and not the other. Mechanical vibrations will also cause a difference in position for the mirrors, so LIGO has a VERY complicated system of mechanical dampers to minimize this effect.
Finally, the last time I checked, most GR experts were of the opinion that gravity waves propagate at the speed of light, not at infinite speed.