Fish in a Barrel Principal and co-founder. Core developer of Django, PyPy, CPython, PyCA Cryptography. US Digital Service alumni. Former Firefox Security. Retired Python Software Foundation board member.
We have jobs right now, it's not like we're hobos. But if you ask any open source developer what's stopping them from adding cool new feature X, fixing bug Y, or starting project Z that they're excited about the answer distribution will look like:
25% - I haven't needed that yet
75% - I don't have the time
.00001 % - That is completely technically infeasaible
(Numbers may not add up to 100 after rounding).
I'll write on my personal blog later today why you should care about all of that, but that's the view from 10,000 feet.
Yes, that could be related to the fact that bitcoin isn't something anyone with any familiarity with economics should take seriously. (For the purposes of this comment "familiarity with economics" should be understood to mean: has so much as shopped in a grocery store).
I'd say the biggest difference between Python and Ruby's is that Python's has a syntax, whereas Ruby's is a function call, this makes Ruby's more flexible since you can always replace it, add new arguments, or in other ways manipulate it. I'm not sure if that's what Armin is referring to though.
It's not unreasonable, it only seems unreasonable because of the context. I've seen several really good programmers (and overall bright people) mix the implementation of the two up.
I don't have a response to that, other than to say, now you know why I decided to write compilers instead of pursue a graduate degree in computer science.
a) If you aren't touching that land mine you're missing the point. You can't say that one is free (except maybe it has a cost), and the other has a cost. That's just nonsensical.
b) Second, I'm going to argue that tests are actually free. And I think this because I don't care how good static type proponents think they are, I know they don't wait until it compiles and SHIP SHIP SHIP, they actually run their damned program. The alternative to automated testing is manual testing, not no testing.
I wasn't trying to catch the error of "program author is a moron who doesn't know the difference between Fibonacci and factorial". Were I trying to catch that error I would have been aware of it, and then much less likely to write the bug in the first place. This is a truism that is well accepted by testing proponents: which tests you write are incredibly important, and you need to write your tests first in order to avoid a curve fitting problem (so to speak). Any non-trivial test would have shown my function to be very broken, what type would you have used to represent that so it wouldn't compile?
The author doesn't really respond to the point, he simply says they were non-trivial in complexity, which may be true, but that doesn't mean they're non-trivial in their dynamacism (is that a word?). Moreover it in no way responds to the claim that these codebases aren't very good.
If you can convert a program from one language to another (which is non-trivially different), in the time it takes to complete your masters, I'm pretty sure it wasn't a very interesting program. Further, the quality of the developers is going to play a large role in how effective any tool (and make no mistake, static typing is a tool) is. This is not intended as a disparaging remark to the authors, but in the 30 seconds I spent reviewing each of these code bases, I was totally unimpressed: none of them seemed to follow PEP8, and several of their test files weren't even unit tests, they were just a random scrip that appeared to exercise a tiny part of the codebase. I therefore conclude that the methodology used in operating this experiment was flawed and, consequently the conclusion cannot be taken as scientifically valid.
I had a laptop hard lock in the middle of a talk once. That was fun. For the record, I handled it by immediately swapping out my laptop for the session runner's (can't risk it happening 2x during the talk), my slides were online and I just re-downloaded them and tried to go forward losing as little time as possible.
Failure also produces a lot of false negatives though, I've failed at a lot of things not because I was bad at them (though, lord knows I have enough failures because of that), but because of bad luck, or bad instruction, or what have you.
You may not need to be smart, but you for damn sure need to be good at what you. And I know this because I've seen the range of quality in pizza, and I've seen pizza places shut down. Can we find something more interesting to do than try to trivialize other people's professions? "It's possible to build a successful business by being able to bash buttons on a keyboard."
Was the show you were wathching "Australia's Naughties Home Videos"? I know that was cancelled half way through it's first episode by the network owner.
I accidentally upvoted you, so I figured I should leave a comment explaining why I intended to downvote you: you either failed to understand the question, or chose to intentionally provide a useless and snarky answer. The GP was asking a social question about how the HN userbase had changed such that a rumor like this made the site.
I wasn't suggesting have a generic queue API in Django, I was suggesting any APIs needed to enable that to live outside Django entirely, whether that's better hooks into transactions (e.g. so I can wait until a DB transaction is committed to fire the task item) or something else.
Let's not, Celery is doing an absolutely fantastic job in this space, let's just stay out of their way and do what we can in terms of exposing APIs to make their job easier. There's a reason django-core didn't write celery in the first place, we didn't have the need or the expertise; there are other people with both, let's let them do it.