HN user

delan

278 karma

{delan@,www.}azabani.com

[ my public key: https://keybase.io/delan; my proof: https://keybase.io/delan/sigs/wYQcFEtgAbAarITmAEdfTwdIq0-rqodlimJsnZPiduk ]

Posts17
Comments36
View on HN

corporate logos, octop^Hcat

Only two logos appear in the entire pull request process, and those are the two small silhouettes that you see on every page.

CoC shoved in your face on every commit

Codes of conduct? While they are becoming fairly prevalent, the GitHub interface has no special understanding of them.

Some of their other writing seems to be of a similarly low quality. Another of their pages [0] seems to mirror a post [1] that they had sent to comp.lang.lisp, where they describe their difficulty with finding out the identities behind some blogs in sufficient detail.

PS it annoys me to no end when one cannot easily find the name of the author on blogs, when the blog author clearly didn't meant to be anonymous. Is there a reason you didn't want it spelled it out?

This turns into a small rant against handles, which, if you set aside the jargon, are essentially nicknames.

(i despise hacker culture, where these “hackers” idiotic-namesake prefer to go by “handles” or abbrevs (e.g. “RMS”, “ESR”, “JWZ”) or whatnot insider-fashion fuck. But that's just me.)

One person seemed a bit annoyed by them, so they then responded with a larger rant [2] that proposes that “hackers” are a strict subset of the people who like to tinker with computers, without ever clearly describing what it is about “hackers” that they “despise” — concluding:

It is this group of people, i despise. More accurately: i despise their general style and outlook. I despite them. Fuck them. FUCK hackers. FUCK their hacking. Fuck their mothers. Scumbags.

At this point, I’d have dismissed them as a troll, but they went to the effort of buying a domain name and everything!

[0] http://xahlee.info/Netiquette_dir/whats_hacker.html

[1] https://groups.google.com/d/msg/comp.lang.lisp/VQF8CIUIotg/q...

[2] https://groups.google.com/d/msg/comp.lang.lisp/VQF8CIUIotg/P...

With progressive enhancement, Twitter could provide basic functionality with full page loads and the like, and use JavaScript to replace these with a better user experience.

That a person would continue to work for a given rate does not imply that they don’t mind working for that rate. There are many reasons why one might continue. They may not be trained in another occupation. They may not have the money to choose to stop working in an effort to make a statement about their rate. They may even want to continue working despite their objections about how much they’re being paid.

If you only look within a given occupation, sure, the disparity isn’t as wide, but that fails to answer some important questions: why do the choices that women (or any given group) make result in them being paid less overall? Should they essentially be punished for those choices, particularly when you consider the power that money buys? Are some of the occupations that are dominated by women undervalued and underpaid, such as teaching and nursing? Consider watching: https://www.youtube.com/watch?v=DV9zBAotFeo

2016 is less than 48 hours away. Why is curl http:// | sh still a thing? Why is the Windows installer delivered without HTTPS, and does it really have no digital signature, or have I been MITM’d? I don’t know about you, but I wouldn’t touch this with a barge pole, let alone a computer.

That’s more true for Linux than other Unix-like systems. Solaris comes with Bourne, FreeBSD comes with that and csh defaulting to Bourne, OpenBSD comes with those and pdksh defaulting to pdksh, and so on.

In my limited experience, rendering vector fonts is among the slowest parts of rendering text in a terminal. The difference between an xterm with a TrueType or OpenType font and an xterm with a PCF is noticeable.

It's only secure when used with TLS 1.1+ where it has an effective security of 112 bits. Otherwise it is susceptible to the BEAST attack, like any other CBC cipher suite, unless the client has been updated to mitigate the attack.

A FAT32 fragmenter 11 years ago

Probably fail spectacularly, as it seems to make modifications to the FAT32 data structures directly. A more generic fragmenter might interact with a file system via pathological file access patterns, but this doesn’t take that approach.

It can be difficult to let go of printf(3) debugging, but using a debugger instead can seriously improve your development workflow.

Just a hypothetical idea: what if the standard allowed a compiler to modify the format string during compilation, replacing e.g. %N with the appropriate conversion specification, subject to proving that a given format string is a plain old literal that is not touched anywhere else?

[dead] 11 years ago

Only a fool would take an outlet like Breitbart seriously.

“I find it offensive to suggest that people that I don’t identify with might just be having a harder time in my industry. [...] I don’t want to be inclusive and considerate of other people. But it looks like they [sic] only way to survive is to be that.”

The loop first sets B, F, Z, D and i all to zero. Then it sets T to a new array containing one element, zero.

The key here is that = is a right-associative expression operator which yields the right operand.

URL shorteners have a purpose, and while they may be misused, there is no reason to say that they are just simply "bad".

There's a difference between 'implementation-defined' and 'undefined'. Question 5 is implementation-defined behaviour, while question 7 is undefined behaviour.

It is, but this quiz is in the context of x86 and x86-64.

> Also assume that x86 or x86-64 is the target. In other words, please answer each question in the context of a C compiler whose implementation-defined characteristics include two's complement signed integers, 8-bit chars, 16-bit shorts, and 32-bit ints. The long type is 32 bits on x86, but 64 bits on x86-64 (this is LP64, for those who care about such things).

A slight variation along the same lines is x >>> 0, which differs in that it yields positive values for values between 2^31 and 2^32-1 inclusive, effectively acting as a C cast to uint32_t instead of int32_t. It runs in roughly the same time as the other bitwise truncation idioms on Firefox 15 alpha, with Math.floor being slightly faster than them.