356 karma · joined November 20, 2018
You started this page in 2017. The revenue has continued to increase at as steady a pace as expenses. And an argument along the exact same lines as yours could have been made in 2009 or 2010 or 2011. Actually, your argument has gotten weaker -- expenses used to be higher than the previous fiscal year's revenue, but in recent years the growth has been much flatter.
There's no compelling reason to think that now is the time to act to make sure that it's not too late to act at some vague future point in time. Sure, something can't grow forever. Granted. But are we at 127 grains of rice or 131,071? How can you tell?
I've been hesitant to commit myself and my collaborators to yet another DSL -- and that's part of why I haven't seen much to offer in snakemake and nextflow.
> After we burn through our reserves, it seems likely that the next step for the WMF will be going into debt to support continued runaway spending
Um, the graph shows that the reserves are increasing every year. Money in exceeds money out year after year.
As a grad student I made a total $1,300 per month, but ten years later I'm spending that on just housing costs. So what?
Exactly at the moment I read this, an auto-playing Volvo commercial started making noise just below that paragraph. Ugh. We're a long, long way from advertising putting "users" first.
Well, as far as I can tell, the reason is that
> Logo's turtle interface [...] is a convenient and intuitive way to describe graphics imperatively. It's great for kids.
:)
That said, high-performance Python does generally discourage the use of loops in favor of vectorised operations.
Instead, the next high-profile HN Haskell link will be the thousandth demo/intro/tutorial that yet again implements some core data structure.
Rather than showing how Haskell is great for working with databases.
Or working with Kafka.
Or integrating with AWS.
Or parsing text.
Or running microservices.
Or any of the other hundred things that I'm going to do a dozen times before I need to reimplement binary trees.
From that post: "I do not have any solutions to the systemic problems here, but improvements should be easy. Criminology as a field has to improve in terms of making data available with full documentation and reproducible code. That would make errors detectable sooner."
Anyone not agreeing with this needs the boot.
For reference, I was a philosophy major, and at no point would I have considered myself qualified to opine on the quality of current philosophy. Similarly, a close friend who was a physics major has now completed a postdoc in a subfield and still hesitates to make sweeping statements about the state of "physics."
And lest anyone is left with the wrong impression, criminologists are not running much of anything in the administration of criminal justice in the United States.
Shawn Bushway's take is probably most representative of the field. If we're going to be taken seriously (insert Arrested Development shot) we need to be able to deal with this.
Criminology has thus far mostly avoided the replication crisis, so there hasn't been much reckoning with sloppy research -- much less with a major figure in the field just making up data. And the co-author network here touches on several of the top programs, so there's plenty of drama.
That's not to say that the field is without problems, but what you're describing is not well representative of what we're taking about when we talk about the journal Criminology.