This weekly roundup thread is intended for all culture war posts. 'Culture war' is vaguely defined, but it basically means controversial issues that fall along set tribal lines. Arguments over culture war issues generate a lot of heat and little light, and few deeply entrenched people ever change their minds. This thread is for voicing opinions and analyzing the state of the discussion while trying to optimize for light over heat.
Optimistically, we think that engaging with people you disagree with is worth your time, and so is being nice! Pessimistically, there are many dynamics that can lead discussions on Culture War topics to become unproductive. There's a human tendency to divide along tribal lines, praising your ingroup and vilifying your outgroup - and if you think you find it easy to criticize your ingroup, then it may be that your outgroup is not who you think it is. Extremists with opposing positions can feed off each other, highlighting each other's worst points to justify their own angry rhetoric, which becomes in turn a new example of bad behavior for the other side to highlight.
We would like to avoid these negative dynamics. Accordingly, we ask that you do not use this thread for waging the Culture War. Examples of waging the Culture War:
-
Shaming.
-
Attempting to 'build consensus' or enforce ideological conformity.
-
Making sweeping generalizations to vilify a group you dislike.
-
Recruiting for a cause.
-
Posting links that could be summarized as 'Boo outgroup!' Basically, if your content is 'Can you believe what Those People did this week?' then you should either refrain from posting, or do some very patient work to contextualize and/or steel-man the relevant viewpoint.
In general, you should argue to understand, not to win. This thread is not territory to be claimed by one group or another; indeed, the aim is to have many different viewpoints represented here. Thus, we also ask that you follow some guidelines:
-
Speak plainly. Avoid sarcasm and mockery. When disagreeing with someone, state your objections explicitly.
-
Be as precise and charitable as you can. Don't paraphrase unflatteringly.
-
Don't imply that someone said something they did not say, even if you think it follows from what they said.
-
Write like everyone is reading and you want them to be included in the discussion.
On an ad hoc basis, the mods will try to compile a list of the best posts/comments from the previous week, posted in Quality Contribution threads and archived at /r/TheThread. You may nominate a comment for this list by clicking on 'report' at the bottom of the post and typing 'Actually a quality contribution' as the report reason.
Jump in the discussion.
No email address required.
Notes -
Damn right it is.
In a world where a byte is 6 or 9 bits, octal would be useful. But for obvious reasons world length tend to be powers of two. So we want a basis of 2^(2^n) for some n. The two choices closest to the base widely used by humans are n=2 (base 16) and n=1 (base 4), which can represent a byte in two and four digits, respectively. Relatively speaking, base 16 is closer to base 10 than base 4 is, so it is the obvious choice.
Let us say you are searching for an IPv4 address in a byte-aligned data stream. In hexadecimal, it will always be the same sequence of eight digits, for example 0xc0a810ff. Converting it to dotted quad is simple, network byte order is big endian, 0xff is 255, 0x10 is 16, 0xc0 is 1216 which is 364 which is 192, which tells us that 0xa8 is likely 168.
Now let us try the same in octal. If an oct digit ends with the least significant byte, the string we are looking for is (0o)30052010377. Otherwise, it might also be (0o)60124020776 or (0o)140250041774. Three different representation for the same sequence of bytes! (Yes, you could also use 3 digits to represent each byte separately, at the cost that 0o,000,377 +1 is not 0o,000,477 but 0o,001,000. At this point, the gains over denoting your words bytewise in decimal a la 192.168.16.255 seem slim.)
There are two reasons why programmers in this century might want to be slightly more aware of octal notation than of EBCDIC. Traditional unix file permissions (and umasks) use octal. But using chmod 755 should probably be replaced by the more verbose chmod u=rwx,go=rx (or setfacl) in any case.
The other reason to be aware of it is that it is a pitfall in C, C++. While the prefix K&R chose for hexadecimal numbers, 0x does not collide with common usage elsewhere, they made the terrible decision that octal integer constants should be marked with a leading zero of all things. (I imagine they got into a lot of disputes at gas stations when trying to pay $0060 with a $50 bill.)
Python here does the sane thing and straightforward forbids leading zeros in integer constants, instead telling you to use the 0o prefix if you really want octals.
There was a short period in 2005-2012ish where FPGA programming languages like VHDL and Verilog had to work on so badly constrained environments that octal bases were worth the obnoxious overhead, but either none of them retained support or no one uses that support for normal code this decade.
More options
Context Copy link
More options
Context Copy link