octal

The later displays mode information in octal which is something ls, despite its 30+ options, does not do.

Support for Octal numbers is insane (especially since uppercase O is supported as well as lower case o) e.g.

That way you can use your octal representation, and more of your configuration is inspectable, without owning and using the vault keys.

It's probably specifically penalizing anything matching /https?:\/\/0/ because you can specify an IP address using hex or octal in most common browsers.

So in ES6 you can use binary (0b, 0B) and octal (0o, 0O) formatting along with exponential (1e-2) and hex (0x, 0X).

If hex hadn't been invented yet, 9 bits works better with octal.

Binary and octal works for me currently on Chrome 43 OS X.

All of this I can understand, but why then octal numbers are not compared the same way is beyond me?

After we remove support for vertical tab can we drop octal literals from every language?

Number automatically accepts exponent notation and auto-converts to hex (ignoring octal).

I remember programming a computer by setting 4 switches in octal to load the instructions.

As fun as it is to snicker at a young programmer who spent 2 hours debugging x = 0123 it's time for octal to go away.

The very first time I wrote an interrupt handler, it was in octal, entered by a numeric keypad into an LSI-11 with DEC's ODT - "Octal Debugging Technique".

Python has had octal literals like this for years, so it is misleading to say that it is "moving to" it.

And, because the evaluation is done by perl, hexadecimal, octal, and binary numbers can be entered using "0x", "0", and "0b" prefixes.

My favorite feature is that if symlinked as "hex", "oct", or "bin", it prints the output in hexadecimal, octal, or binary.

Students aren't usually taught that there are ways of counting outside of the decimal 'base 10' way of counting, or the advantages of counting in Octal, or how to count in Binary on your hands.