I've heard of it too. You would need an analytical balance to get accurate measurements weighing a piece of paper. Just cut out the part you want to take an integral of, then cut out a piece of paper with known size (or cut several pieces with different sizes to get more accurate results) and weigh each of them. I guess this used to be cheaper and faster than using computers when computers were big and expensive.

Nono that's genius

..ignoring the part that it's just a discrete approximation of an integral a la a Riemann sum.

How thick is your paper?

Me too, any day. I hate everything where indentation matters. Let me just throw my garbage there and YOU sort it out, you are the fucking computer, not me. You do the work.

So fuck you, YAML! All my homies love JSON!

Yup.

Spaces? Tabs? Don't care, works regardless.
Copied some code from somewhere else? No problem, 9/10 times it just works. Bonus: a smart IDE will let you quick-format the entire code to whatever style you configured at the click of a button even if it was a complete mess to begin with, as long as all the curly braces are correct.

Also, in any decent IDE you will very rarely need to actually count curly braces, it finds the pair for you, and even lets you easily navigate between them.

The inconsistent way that whitespace is handled across applications makes interacting with code outside your own code files incredibly finicky when your language cares so much about the layout.

There's an argument to be made for the simplicity of python-style indentation and for its aesthetic merits, but IMO that's outweighed by the practical inconvenience it brings.

There's a joke here about using echo "some python code" > main.py in here somewhere but I can't find it. Imagine I did instead.

Obligatory mirco is better.

I have not known happiness for 12 years now.

It's so dumb that JSON doesn't officially have comments.

So much this.

Used to work at a company where I sometimes had to manually edit the configuration of devices which were written and read in JSON. Super inconvenient if you have to document all changes externally. As a "hack" I would sometimes add extra objects to store strings (the comments). But that's super dicey as you don't know if it somehow breaks the parsing. You're also not guaranteed the order of objects so if the configuration gets read, edited and rewritten your comment might no longer be above/below the change you made.

Always found it baffling that such a basic feature is missing from a spec that is supposed to cover a broad range of use cases.

4 spaces, although I'll die on the hill that tabs should always be used instead of space for indentation. Not just in python.

With things like black, flake 8 and Isort I can code however I want, list/format however I want, and commit team compliant content. The dream is real