News for hackers. Stuff that matters.

safod

Re:Ursula K. Le Guin at the National Book Awards on Friday November 21, 2014 @07:53AM (#8641008)
I like that you acknowledge that the innate human drive to create is at least as strong a drive as the profit motive, yet are only willing to accept that it is a sufficient motive in a "post-scarcity" society (whatever that is supposed to be anyway - there will always be scarce goods, that's the nature of the universe). You also commit a common fallacy when you imply in your first paragraph that communism preventing people from accumulating capital is an act of unjust violence and oppression - it is not, and that is so for the same reason that preventing people from stealing from others is not an act of oppression either. I suggest to actually read one of LeGuin's books, mostly notably The Dispossessed.
Re:Plan 9 Coding Conventions for C on Wednesday May 22, 2013 @09:52AM (#5750800)
Why not? vim indents one more when encountering a colon at the end of a line. It also de-indents when encountering a return or break statement. Of course in all other cases you have to de-indent manually, however, hitting backspace once is not more work than typing a closing curly brace.
Re:Strings – Dive Into Python 3 on Friday May 10, 2013 @02:58PM (#5688013)
Actually, this is a bug. Unicode codepoint U+1E9E is LATIN CAPITAL LETTER SHARP S and should be the result of u"ß".upper(). This is especially so because otherwise u"Maße".upper() (Maße means measures) returns "MASSE", which could be confused with u"Masse".upper() (Masse means mass). In such cases, where confusion is possible and no uppercase ß is available, the German dictionary Duden actually suggests using SZ instead. Therefore, u"Maße".upper() would have to return "MASZE". However, since the Python string processing routines can hardly carry a dictionary around just to check whether there is a similar word that would have the same uppercase spelling, this is obviously not feasible. U+1E9E would be the way to go.