"Faced with this piece of information, someone thought the logical thing to do was to, er, write an entirely new language?"
by my understanding, the whole new language slant is because of the nightmare of c++ code out there to reuse, with unintended consequences. php is very web centric and java the last attempt at a 'universal' coding setup. python is an example of new language and how more complicated new language implementation is.
Are you suggesting that they wrote PHP to avoid code reuse, that there hasn't been an attempt at a cross-platform language since Java, and that Python is complicated, all in the same paragraph?
The question is whether we are getting the right responses in this respect from the right set of neurons in reaction to the corresponding trigger.
As I see it, there's several problems here.
The first is that we don't really understand neurology all that well- higher level thought is, for the most part, a mystery to us, so identifying the "right set" isn't really possible for us at this point.
The second is that even if we were able to select the "right set", I don't think we have the imaging technology necessary to distinguish between correct and incorrect states without inducing a margin of error that would qualify our hypothesis out of existence. I may be wrong about that- it's been known to happen, and I'm not an expert.
The third is that because many different regions of the brain are involved in high level thought, the degree of confidence you can gain from any one observation matching the model is relatively low, even if you could have confidence that you're measuring the right thing and that your measurements are accurate.
Putting all of this together, the only way I can see to verify correctness would be to ensure a very tight correlation between total model state and total simulation state. AFAICT, that will require incredibly good nondestructive resolution to be practical. I don't know for sure, but as far as I do know we aren't there yet- which brings me back to the question of why they said anything if they weren't sure.
One of the ways of introducing people to alternative software is to install it and have in sitting there on the menu. By removing the GIMP, they're just encouraging people to think that linux is "not ready for serious users."
The plural of anecdote obviously isn't data, but most of the people who do image editing that I know are already aware that gimp exists, and the expectations as to what programs are installed are different coming from windows. I just don't see this as a valid point.
Between the fugly colour schemes, the stupid naming schemes, the artificial restrictions on root (hey - it's MY computer, not yours), not including the toolchain for building the system by default - even on xubuntu, etc., I'm glad I stuck with opensuse.
1) Color schemes are a matter of personal preference.
2) Nobody cares about the name.
3) Its called 'sudo', and its a good idea. Barring that, there's only about a million ways to get actual root if you neeeeeeed it, which I doubt you do.
4) sudo apt-get install build-essential
If you found any of that difficult to grasp, I'm glad you stuck with opensuse too.
Yes, it's a flame, but ubuntu sucks for development. And now it's going to suck for users who want a bit more than average / mediocre.
I've been developing for years on Ubuntu, and find it quite comparable to the experience of developing on other
The one day you'd sell your soul for something, souls are a glut.