Because somebody on Slashdot told them?
That would be a valid point if the two orbiters were exactly the same. They're not. India is much closer to the equator than Florida, so launch costs are significantly reduced.
That is nonsense. You want to launch as far away from Earth's axis that is true, but Earth is a sphere and therefore it doesn't make much of a difference once you get away from the poles. Florida is already at 88% of the distance from the axis compared to the equator, that is not that much of a difference.
The problem is that NASA is not allowed to pay too much for an engineer and have to hire scores of affirmative action candidates instead: http://odeo.hq.nasa.gov/
Especially in an environment like NASA one single capable engineer can easily outperform ten mediocre hires. Of course NASA would have to do strict qualification tests to get these engineers - and those tests are illegal in the US.
India may be corrupt and all, but after you pay the bribe at least you can do the job. You are not forced to hire deadwood in India.
There is no ODEO in the Indian space program.
Since when has failure been an argument against government layouts?
The US had the best (or maybe second-best after England) education system in the world before the government got involved. Now it is the laughing-stock of the world.
The solution? More government involvement, of course! Let's implement Common Core and see how low we can go.
You should research on "common core" which was pushed by Bill Gates.
It is pure evil:
- dumbs down everything and doesn't let anybody ahead
- goes back to roman math (seriously, according to common core, the way to add 62 + 36 is to draw 9 squares and 8 lines and then add them. If you don't draw your squares you fail, BTW)
- introduces political propaganda into the curriculum
- introduces spying and questions like "do you like your parents"?
- establishes a monopoly for textbooks
Good starting point:
In fact I had to deinstall pulseaudio to make Skype work - on several different distributions. That was the only way because pulseaudio just didn't work. For a long time the audio-quality was also bad (had a lot of hickups and cracks). I also know (you obviously don't) that the pulseaudio-team refused to work on many problems because the drivers (which worked perfectly with ALSA) were somehow flawed. Now maybe they were flawed, but they worked with ALSA and if they don't work with pulseaudio then ALSA is still better no matter how many features pulseaudio may offer.
The distributions *should* be the advocates of the users. But they are not. They are advocates of the developers who obviously always want the latest/greatest.
When your mother tells you that she has cracking in the sound that makes it unusable, do you tell her "hey, just uninstall pulseaudio and enable ALSA"? Is that user-friendly? Or do you tell her "You are the reason that there will never be the year of the Linux desktop, the cracks are a product of your imagination"?
You quite obviously have no idea what you are talking about. Especially about Skype which took forever to work with pulseaudio. Especially Skype. God I remember hours of getting Skype to work with (or in fact without because uninstalling did the job) pulseaudio.
As I said, the way to go would have been to include pulseaudio and let those that need the advanced features use it. And then, after it became stable, then make it the default.
But that didn't happen. They just jumped on pulseaudio years before it was ready.
And that is the problem: You and all the other upgrade-fanatics consider the users just worthless beta-testers without any rights whatsoever.
In your scenario you are positing that you have the ability to run binaries (like cat or vim or nano)-- the tools required to successfully read and parse ASCII files. Why are you assuming you would be unable to use another binary dedicated to reading and parsing a binary log file?
Because Linux distributions always screw it up at their first try?
Because nobody can know everything and the obscure systemd tool may be there but not be found?
Also systemd is by itself much more complicated than simple ASCII files.
There is NOTHING magical about ASCII except that its an old standard.
Exactly! And that means that it is:
- understood (hey I know cat and grep by heart, I don't even know any systemd commands)
Which means that the chances are very high that at least that will work when something breaks. And by that statement I include the human factor: The admin who has worked with ASCII files for the last 30 years will be able to work with them in an emergency. Especially in an emergency I don't want to be forced to learn the "new paradigma".
It makes NO DIFFERENCE.
You are contradicting yourself.
When you said that ASCII is an old standard I thought that you got it, but you didn't.
Being old, stable and tested makes ALL THE DIFFERENCE.
Systemd may be great and maybe it is - but please let it mature first, let the bugs get worked out first. In other words: Let it become a "old standard" before forcing it down the user's throats.
You are using a "special tool" when you use vim or cat to parse a log file.
No, because something similar is available on pretty much every desktop computer system for the last 20 years. I'm pretty sure that I can read ASCII files on an Amiga, MacOS9 or BeOS or any other exotic system.
With systemd, I don't expect any support from even the latest/greatest MacOSX or Windows variants.
How many other audio systems can you mention in Linux which seamlessly allowed you to add devices to an audio stream, hot plug blue-tooth headsets, or change destinations of streams without interrupting them?
None, but nobody except a tiny group of people ever needed anything like that. There would have been nothing wrong in just supporting pulseaudio for those that need it and keep the working ALSA for the default until pulseaudio is debugged. And only when you have a couple of years of stability make it the default. But no, we can't have that. No, everybody had to make it the default as soon as they could - and of course I was also bitten (several times) by pulseaudio. And I had no alternative because all wanted to be part of the herd.
This herd-mentality is really the problem with Linux nowadays. In *theory* we could have many different distributions - from cutting-edge to conservative. But in the real world we have a group of lemmings that compete on who is the first to jump on the latest untested feature.
For example: On one computer I used debian lenny for many years and now I wanted to upgrade. Tried the new debian - hangs on shut-down. Tried SuSE - hangs on shut-down. Tried Mint - hangs on shut-down.
You see what I mean? They are all the same - and that sucks.
Why would you suppose systemd logging to be any different?
Because it is new and untested.
Just like pulseaudio.
In principle I agree with you, but I disagree with the hurry. There is no need to hurry at all. We have working solutions right now, there is no sense that ALL distributions jump on systemd like a herd of lemmings.
I had a lot of broken scripts in the bash to dash transition. But that is also a reason NOT to change too much and NOT to switch to systemd any time soon.
Exactly. Linux would need stability and not this constant change for change's sake.
If you want systemd - great, make it an option. After a couple of versions, when the bugs have been worked out, make it the default if it really offers an advantage, but not before.
Everybody is pretending as if Microsoft didn't know that Metro sucks. Of course they know, they had the response from the betatests. But they did it anyway to push their appstore.
Do you realize that we have that large criminal class right now? And that it did not exist before the welfare-state?
Why do some people who are intelligent enough to realize that higher taxes get passed to the consumer too dumb to realize that (in a free market) lower taxes get passed to the consumer as well?