HNHacker News
TopNewBestAskShowJobs

avdd_

15 karma · joined February 27, 2013

submissionscomments
avdd_··on Functions Should Be Short And Sweet, But Why?
So why does the main function in this example violate the principle ... i.e. where is the dispatch table?
avdd_··on Prototypes Are Not Classes
I've read it twice and still can't find the point.
avdd_··on Asciiflow
unhelpful
avdd_··on Asciiflow
Putting an informative README in your git repository seems a pretty common practice these days.
avdd_··on GNU Guix 0.5 released
> Guix is a version of Nix

Why would I use one and not the other?

avdd_··on Why Japan Is Crazy About Housing
http://en.wikipedia.org/wiki/Tokonoma
avdd_··on Python 3.4 Beta 1 Released
No one objected to using "pure" instead of the more common "abstract" (which is the actual antonym of "concrete") ?? Why do people do this?
avdd_··on History of T
why does this not have a date?
avdd_··on The Impossible Music of Black MIDI
It's not a song, it's a prelude. And actually not very technically difficult, one reason for its immediate and enduring popularity. The simultaneous chords are just played very quickly one after the other and not "rolled".
avdd_··on Firefox 25 is released
Actually, it's the sharing of search terms across tabs that is useful, and is still supported.
avdd_··on Firefox 25 is released
Why? I found that useful.
avdd_··on Discover the Ladder Paradox, relativity's greatest thought experiment
schrodinger's ladder?
avdd_··on How to support both Python 2 and 3
Well zed seems to agree

https://twitter.com/zedshaw/status/364118939233554432

> they've been keeping this "dual mode" option mostly a secret so as to not have to admit they fucked up

avdd_··on How to support both Python 2 and 3
> I'll start with the conclusion: making backwards incompatible version of a language is a terrible idea, and it was bad a mistake.

> So let me fix that: I do recommend a single code base as the solution.

> The original advice to think very separately about your 2.x and 3.x codebases was very wrong, has wasted a ton of time (since you end up porting to python 3 twice), and overall slowed down the adoption of py3k, a slowdown that fortunately is finally lifting.

Is this opinion common? Do Guido and the other core developers admit they were wrong?

> Python 3.0 will break backwards compatibility. Totally. We're not even aiming for a specific common subset.

That a single code base is now possible, albeit "not entirely idiomatic", does support the conclusion that the original aim to break compatibility was misguided at best, and raises questions about the governance of Python overall.

avdd_··on React, a JavaScript library for building user interfaces
What is with this low-contrast trend?? Are the complainers not loud enough? Please stop doing that!
avdd_··on Thank you HN, sorry HN
This.

The best way to reciprocate is to commit to being the best "you" you can be. Good things will flow naturally from that.

avdd_··on Virtualenv's bin/activate is Doing It Wrong
I assume you mean this thread

https://groups.google.com/d/topic/python-virtualenv/XzI8GStv...