434 karma · joined April 16, 2012
http://fnordmetric.io/documentation/chartsql/external_data_s...
I once wrote a library for python that injected itself into the main modules (os, sys, etc) and generated random failures all over the place. It worked very well for writing reliable applications, but it only worked for pure python code. I don't own the code, so I can't open source it unfortunately.
If this were true, then why are downvoted comments faded? Because unpopular opinions don't need to be read by others? The downvote button is for noise that doesn't contribute to the discussion, but that doesn't break the rules. At least, that's what it's always been to me (regardless of what HN claims it's for).
* A tool that generates Markdown API docs from Python files
* A whitebox system scanner that reveals problems with your server configuration. Not your average blackbox security scanner.
* A lightweight service bus without all the enterprise and java around it. It's basically a bunch of connectors that receive or poll for incoming events (rss feeds, email, trello, XMLRPC/SOAP/REST requests), maps it, filters it and then sends it out again. I'll be using this on something like a Raspberry Pie to do some home automation and such. Main goals are that it should be super easy to add new rules, connectors, etc.
> "Please remove mitsuhiko/* (This guy is complaining about tip4commit, please help educate about Bitcoin)"
and the mod writes:
> "You are not allowed to incite brigading. Please resubmit using the original source - the github link. You are part of the problem of why people hate our community"
Seems like the mod is reprimanding the submitter of the story for the "please help educate about Bitcoin" part of the submission (which is inciting brigading).
I have to say, from this and your other comments ("Do not use any language other than english in public code"), you come off as extremely arrogant.
Thank you for this.
git add <file> -p
This lets you pick chunks of code from <file> that you'd like to stage for commit. When I feel I'm done coding for a session, I just run a `git diff` in one window, and in the other one pick chunks that contain changes that belong in one commit.Laws are great, but they're easily circumvented. Especially in the Netherlands. That's why this "Free Internet" project is reasonably useless. Its view is too narrow, focusing only on official laws and not on actual practices. For instance, after the whole Project-X incident[1], law enforcement has been looking into being able to remove social media posts on a whim, without judicial oversight. Such underwater erosion of rights is common in the Netherlands.
Given the reactions here and at the bug tracker, I don't think that would be a very good idea. People are having knee-jerk reactions without apparently even having read the first few comments. If the Hacker News crowd can't be arsed to understand what's going on, then the last thing you want is "the public's attention" on the decision making process.
The command line works with text. The command line remains the best interface I've ever used. It's user friendly, composable and available everywhere. It's easy to automate and easy to extend.
I wish the "command line with pictures" idea would just go away already. It adds nothing for the general public. I can already view pictures on remote machines with X forwarding.
Command line with pictures never made it, because there are ten competing standards. With text, everybody just agreed on ASCII and now Unicode/UTF8. Text has hundreds of ugly clutches on top of it (Extended ASCII, ANSI, Escape codes, etc, etc). It still works. It's still simple. It has its problems, but nowhere near as many problems as GUIs.
Those who don't understand Unix are doomed to reimplement it... poorly.
Until I hit the Java scene. Boy, is it a big mess. There I found some of the worst unreadable, unmaintainable, ungrokable, complex and brittle code I've ever seen. And that's not an exception, rather it's the standard. I suddenly understood why Python's logging implementation is such a disaster. It was ported from Java. I'm sorry if this offends the java programmers, but it feels like idiomatic java is just abstractions piled on abstractions upon patterns, in the hope of somehow making things more understandable or robust. It doesn't.
I've always thought of OO as simply abstraction and encapsulation. Functions on steroids, if you will. If something doesn't fit the OO paradigm, I don't try to shoehorn it in (which patterns seem to especially made for). If you manage to avoid doing that, OO works rather well if you ask me.
- that environments are inherited by child processes. - It's not just Web servers that might execute scripts (DHCP could also be vulnerable, SSH with command restrictions, many other things too).
That's the big shitstorm about this bug. It's very hard to determine when you're actually vulnerable. The safest thing to do is to upgrade bash everywhere. But wait! The patches they rolled out don't actually fix the issue all that well. So there's no easy one-stop guide you can follow to fix this. Everybody actually has to think about every single system that might potentially be vulnerable and come up with a good solution all by themselves.