Are you referring to the work or Perl? Most programmers I know working in a scientific area switched to Python years ago and run away screaming when they hear the work "Perl".
Well I guess it is "unnecessary" to the extent it is unnecessary to be able to Control-C your programs. Personally I like my programs to respond to signals.
Same here. As a nice side effect, QThread somehow makes signals work again, so you can Ctrl-C a MT Python program (you still have to set a handler for SIGINT but at least it works).
For this reason, I actually use QThread in console apps aswell.
So if mass and charge are both just attributes of particles, what is the "charge equivalent" of the Higgs boson? And if there isn't one, then why is it assumed the HB exists? Why cant particles have a innate "mass charge" in the same way they have an "electric charge"?
If it were simple why aren't these lawsuits being thrown out the front door? Why isn't FRAND turning out to be the watertight defence it ought to be? (serious question I would love to know the answer to, as these FRAND related lawsuits seem to keep coming up over and over again).
I look forward to the day PyPy is considered the real Python. Look at PyPy's homepage (http://pypy.org/), doesn't even mention Unicode as a significant feature. Instead it talks about speed, security, concurrency, and compatibility with the current real Python (2.7.2) - all the things real Python programmers care about and expect the Python developers to focus on.
PyPy may be some way off but I want to find the developers and hug them for setting the right vision and trying.
I just donated $50 and if you hate Python3 you should too.
>Google's is worse because it takes all rights to use your work however it likes, and then states in its Privacy Ppolicy that it won't use it for anything other than to provide the service.
Please point to the part of the Privacy Policy that deal with "my works" or "works that I create and own". I think if you look closely, the PP only deal with information Google collects about your usage of the service, which is quite different to works you upload to Drive.
> Well, first off, Google has a privacy policy [1] where they commit to not publishing my entire works without my consent.
It doesn't say that anywhere. The Privacy Policy covers "What information we collect and why we collect it.". In other words, the PP is about information they collect about you using the service, not stuff you upload to Drive. Think IP addresses, cookies, log-on times etc.
> Even without that, though -- what do you think would happen if they did what you're suggesting? I think the public punishment would be worse than any legal repercussions.
So your saying that TOS don't matter and we shouldn't read or analyse them because we trust Google wont do anything untoward? So we are we even having this discussion in the first place then?
>Google specifically enumerates the rights that you're granting them
They sure do. It just turns out one of these rights is that they can use your content for promotional purposes (advertising?).
Dropbox may not have such a detailed TOS, but they are clear on one thing: whatever rights you do grant them are solely for the provision of the service to you.
Well given that the current runtime (written in C) doesn't have a runtime, I would assume there wouldn't be one, as Go compiles down to native code just like C does, using the same toolchain (6c/g -> 6a -> 6l).
My current guesses are:
1) Performance
2) The need to call assembly code easily
Does anyone know why the Go runtime is written in C? The FAQ says it is to get around bootstrapping, but that does not seem obvious, as the Go compiler (6g) is written in C, so why cant the runtime be written in Go and compiled with the rest of the Go library?
Also, is the incompatibility between Go and C just due to the segmented stacks in Go? What about function call conventions? Anything else?
"You are saying that Agile is supposed to mean programming in Ruby instead of Java?"
Of course not. But in my experience and observations, corporate IT programmers, especially those with a Java background, are the worst offenders when it comes to abusing the Agile concept and failing to get the basics anywhere near right.
"And only small teams can be Agile? Amazon.com would disagree with you, for one."
I am not saying that, but I think it is a good question. I have never seen a team of hundreds coordinated to an outcome using an Agile approach. I have been involved in large projects with up to 300 people (think multiple, large teams of business analysts, developers, database designers, architects and testers and a little hierarchy of IT project management) work towards a single outcome using a highly managed, strict waterfall approach over several years. It wasn't pretty, but we got there in the end, and I would not swear on the Bible that we could have done the same using Agile.
If Amazon is really using an Agile approach to coordinate hundreds of people working on a single project, I would love to read about it.