tl;dr: The bill going to the Senate has several amendments now which exist to help small scale or organic/local farms get exempted from the more burdensome requirements.
I'm a pretty big fan of Vanilla (http://getvanilla.com/). It doesn't natively support threading, but I think there may be a plugin for that. It's out of the box install is very clean, very simple, and very useful.
Rolling something from the HN or Reddit codebase sounds like a pretty interesting project, though.
1) I don't really know that this feels like an ivory tower tone. I mean, it was grounded in legit research or anecdotal evidence, not a lot of "this is how it ought to be" talk.
2) I'm pretty sure instances where someone is singled out to have dodgeballs thrown at one's face would be in the 'bullying' category, not 'teasing' which the author admits can be a difficult distinction.
To add to the list of examples of places where you have to roll your own:
At my company we needed a simple CSV reader for a file submission. That's it--just something that could read CSV files. We figured that had to be available in classic .NET We look around, dug into forums, and finally got in touch with the local .NET user group guru. The ideal solution? Use MS's communication tools to open the CSV file in excel and read it there. Or? Roll your own.
We ended up doing the thing in python and imported the csv lib.
To be honest, you didn't look hard enough. There are multiple, mature OSS projects to handle this.
Where should the framework end? People complain all the time about the size of the framework, but then when their pet feature is missing, they cry foul.
I think it might be worth pointing out that this is only applicable to "those seeking cabinet and other high-ranking posts." It's not like every possible White House employee is being asked to hand over the keys to their online lives.
And the submission headline here is a little misleading: the questionnaire appears to focus on affiliations and past financial associations, not facebook pages and IRC logs.
This article is pretty well linkbait. Following up to the actual post by the MS team reveals Linq to SQL isn't being killed--they're just choosing Linq to Entities as their preferred solution.
"We are listening to customers regarding LINQ to SQL and will continue to evolve the product based on feedback we receive from the community as well," is not remotely the same as killing Linq to SQL.
These charts would have been a lot more informative if they had gone to the trouble of stoplisting the words before analyzing. Glue words like 'the' and 'a' shouldn't comprise any thoughtful analysis--obviously they're going to dominate any sample of the English language.