caseydurfee

Getting rid of government doesn't change the ability for the powerful to use money to apply coercive force against the powerless. You know that, right? It just means they have to do it themselves. Would you rather $EVIL_CORP own a Senator or own weapons of mass destruction?

I have no idea what you mean by this. Could you elaborate?

The vast majority of custodial arrangements are not decided by the courts, but between the parents, so I'm not sure how you can blame this ratio on our legal system.

Only 4% of fathers seek custody of their children through the courts, but when they do, they win the majority of the time. Men who actually bother to fight for custody usually win. So how is this a civil rights issue?

Regardless of your thoughts on feminism, describing the content on avoiceformen as being 'very reasonable' is absurd.

I'm respectful of other people out of a desire to be a decent human being rather than because I have "a loathing for common people" or wish to gain some sort of social currency.

I'm having a hard time formulating reasons why people would get so psychotically upset about what used to be considered just good manners unless they're both entirely devoid of empathy themselves, and threatened by people who do experience empathy.

Try and identify plants/stars/places in the text by their real names, work backwards from those names, find some other semi-intelligible parts of the manuscript based on that, then handwave away the 80% of the manuscript that has to be gibberish because the information density is too low to be some kind of natural language... why is another attempt along these lines interesting?

Fat models are already a code smell, but passing the request object to your model should really set off alarm bells. You've now made it extremely messy to use your models outside of a web context, making it impossible to unit test them, and pretty much wiped out the purpose of the controller as an encapsulation layer.

Domain-driven design (DDD) provides a lot of patterns that help to keep from either having model code in your views, or these types of junk drawer models.

Basically, DDD as it applies to MVC webapps is: If it's a complex query of some sort, create a query repository that returns model objects rather than a "fat" static method on the model itself. If it's a business transaction, create logic objects that encapsulate the biz logic, and service objects that applies the logic to the models. The controller serves as the broker between requests, services, and entities. You end up with much more testable and reusable code this way.

You say you don't donate because you don't feel rich, but maybe you don't feel rich precisely because you don't donate.

If you don't feel rich, you're probably doing all kinds of other things to sabotage your financial success that are more than canceling out the cost of a little charity here and there.

The fundamental problem is that glucose levels in non-blood fluids do not exactly match blood glucose. The current monitor solutions use interstitial fluid in the skin. They still require the user to test themselves several times a day and recalibrate the monitor based on blood glucose, and they can't alert the user if their blood sugar is low until it's already a serious situation. They also frequently give false positives.

This is a new (but very clever!) way to do something that has been around for a while, not a revolution, unless tears track blood glucose much closer than interstitial fluid does. Simply based on first principles, that seems unlikely.

And there are basic hygiene problems wearing contacts while you're asleep, which is when monitoring would be most useful. If google has the technology to make contact lenses that you can wear 24*7 without getting ulcerative keratitis, that's more revolutionary than another way to monitor blood sugar.

I think there's a great book to be written about scaling codebases that started out as monolithic MVC frameworks (Django, Rails, Struts, etc.) I find Flask's design is heavily informed by the problems that monolithic frameworks create, so it would be a great case study, but it's totally out of scope for an intro to flask, though.

http://en.wikipedia.org/wiki/Commodity_Futures_Modernization...

Since the bubble burst, what corrections has the free market made to prevent there isn't another one?

So much of the rhetoric about "free markets" seems to come from looters who resent the government eliminating ways to make money by rent-seeking, collusion and fraud rather than producing useful goods.

(edit: fixed link)

Given that geeks are more likely to fix this stuff, why not talk about blocking hacker news, twitch.tv and reddit? What about political sites Politico, Huffington Post, Slate, that treat politics like sports -- who "won the morning", who's going to win Iowa in 2016, etc., deserve a lot more blame for peoples' political ignorance and apathy than a site that treats sports like sports.

It's a quintessentially American view, though -- my pleasures are above reproach, while yours mark you as a cretin. Nobody who likes things you don't like could be smart!

I guarantee that would spark some interesting debate!

A JS module or HTML widget should be able to declare what it needs without hardcoding how that dependency gets fulfilled. (eg. if it's loading on a local dev box, do this, in production, do that, running server-side in a Node.JS setting or in a test suite, do this other thing.)

So the system I built allows devs to declare the resources needed by a feature, then the asset management system converts those requirements into LABjs script loader code that gets output -- more of a makefile sort of approach. That means devs can write more general, reusable, testable JS modules (and corresponding HTML templates) that can load through a script loader for better performance, but aren't tied to a particular deployment environment or how the script loader works under the hood.

I wish there was a more natural way for logical components on the page to declare the resources they need without mixing code and metadata. HTML Web Components, for example the [Polymer project](http://www.polymer-project.org/), are possibly a step in the right direction, but I don't think they address intelligently lazy-loading requirements.

What's with the "we"? Are you attempting to speak for developers as a whole?

Thing is, I've never met a great developer who gave a crap about a coworker's religion, political beliefs, whether they drink or not, etc. I've met plenty of mediocre ones who do.

The headline of the article is "OP-ED COLUMNIST/Hitting China’s Wall."

At the bottom of the article it says "A version of this op-ed appeared in print on July 19, 2013"

Why does the Dewey Decimal System still have 10x as much space for Unitarianism as it does for all of Buddhism? [1] Well, think about what it would take to fix Dewey's initial biases post-hoc... either you have to get it exactly right the first time, or have a system that is designed to evolve.

It's unsurprising the wikipedia hive mind hasn't gotten it right. It's orthogonal to everything Wikipedia has generally done well. Seems like the best solution would be to have a separate taxonomy project that is overlaid on top of core wikipedia data by a set of flexible rules and not hardcoded in articles themselves.

[1] http://www.hyperorg.com/backissues/joho-sep03-04.html#dewey