jdnier

A favorite of mine is the book BUGS in Writing, by Lyn Dupré (1998, Addison Wesley). It's a teach-by-example book with lots of examples she rates as ugly, bad, good, and even splendid.

Since it's "tribute", it seems like a synonym for return. A function's output is its tribute, or maybe just the thing it returns.

    def speke_parott():
        # many machinations...
        trybut = "squwak"
        return trybute

It's hard to sense how much of vi is in vim, having only ever used vim. But I've never been very happy with vim, even though I've used it for 15 years. Maybe I need to find a "vim, the good parts (aka vi)" book.

Nice! https://tug.org/FontCatalogue/utopia-fouriermath/ I've been away from TeX/LaTeX typesetting for a long time. That's immediately appealing.

My experiences with reiki were positive, but my practitioner mixed shiatsu (lots of touch) with reiki.

There's an article on HN today also on "Physical force alone spurs gene expression, study reveals", which might be an interesting angle to consider with any sort of therapeutic massage involving contact.

https://news.ycombinator.com/item?id=22757857

A really well done fly through video of a very large image, with some incredible detail within.

Latest info on Feather and related pyarrow: http://arrow.apache.org/docs/python/ipc.html#feather-format

That video really is awesome. A lot of practical experience distilled.

I was never sure about that, thinking that a single interpreter process runs on one core and the threads must share that process space. But you're right, and I found good confirmation in this visualization (see the "code" link also): http://www.dabeaz.com/GIL/gilvis/fourthread.html

See also http://www.dabeaz.com/python/UnderstandingGIL.pdf, which explains that

    • Python threads are real system threads
    • POSIX threads (pthreads)
    • Windows threads
    • Fully managed by the host operating system
    • Represent threaded execution of the Python interpreter process (written in C)

And a quick zoom in video showing the galaxy's location in Perseus here: https://hubblesite.org/contents/media/videos/2020/01/1270-Vi...

Here's the full list of "Things I Won't Work With" articles: https://blogs.sciencemag.org/pipeline/archives/category/thin...

From https://curlie.io/

> If you like the interface of HTTPie but miss the features of curl, curlie is what you are searching for. Curlie is a frontend to curl that adds the ease of use of httpie, without compromising on features and performance. All curl options are exposed with syntax sugar and output formatting inspired from httpie.

So curlie is curl. Thanks for this.

Oh he's hardly a hobbyist. :) From his biography:

https://langorigami.com/about-robert-j-lang/

Robert J. Lang has been an avid student of origami for over fifty years and is now recognized as one of the world’s leading masters of the art, with over 700 designs catalogued and diagrammed.

If you're interested in Origami, this new video by physicist Robert Lang is really something.

Thank you for mentioning jupytext. I had read about it but had forgotten the name. https://github.com/mwouts/jupytext

Note: This article is from February 2017.

Sure enough. This may help show what happens with float precision:

    >>> import math
    >>>
    >>> for i in range(1, 20):
    ...     n = int('9' * i)
    ...     digitLengthClever2 = math.floor(math.log10(n) + 1)
    ...     float_value = math.log10(n)
    ...     print(f'{n:<20} {digitLengthClever2:>2}  {float_value}')
    ...
    9                     1  0.9542425094393249
    99                    2  1.99563519459755
    999                   3  2.9995654882259823
    9999                  4  3.9999565683801923
    99999                 5  4.999995657033466
    999999                6  5.999999565705301
    9999999               7  6.99999995657055
    99999999              8  7.999999995657055
    999999999             9  8.999999999565706
    9999999999           10  9.99999999995657
    99999999999          11  10.999999999995657
    999999999999         12  11.999999999999567
    9999999999999        13  12.999999999999957
    99999999999999       14  13.999999999999996  # <-
    999999999999999      16  15.0                # <- 
    9999999999999999     17  16.0
    99999999999999999    18  17.0
    999999999999999999   19  18.0
    9999999999999999999  20  19.0

> You probably would need to adopt a rule of no direct-to-table access, and a separate schema per API version containing views, and dealing with the pain of rewriting the views for all the supported API versions when you need to change your data model.

My understanding is there is no direct-to-table access with PostgREST; you're only ever interacting with views. Keep your view api versions in separate schemas. If you change your tables, yes, you'll need to update your views, but I don't see how that's much different than having to modify ORM code to accommodate schema changes.

(An ((Even Better) Lisp) Interpreter (in Python)) http://norvig.com/lispy2.html

>We’re also rapidly working on open sourcing the core tech behind Quark.

The github repo is the website code only (https://quarkjs.io/FAQ/license.html).

Looks like lots of work has gone into the project, but so far it's a black box. Is the goal for this to be a commercial product?

Yep, Quark has been used for page layout and typesetting since the 80s. They do web layout now also, so this js project seems to have some overlap potential.

Sounds kind of like the recent global Cloudflare outage. That outage started with a regex (WAF rule) being pushed out that immediately exhibited pathological backtracking behavior and "caused CPUs to become exhausted on every CPU core that handles HTTP/HTTPS traffic on the Cloudflare network worldwide."

https://blog.cloudflare.com/details-of-the-cloudflare-outage...

That's remarkable and unique penmanship.

Notable quote from the article:

> Harmful as it was, the nuclear accident was far less destructive to the local ecosystem than we were.

That About DACs video is fascinating. It gets to the issue of what is it audiophiles might be hearing that we just can't seem to measure. (An explanation of why "the specs are so much better" but "it still sound wrong.")

This reminds me of "RAM Doubler" from the mid 90s on 68030/40 Macs. https://tidbits.com/1996/10/28/ram-doubler-2/

I do remember the joy have doubling 16MB of RAM to 32MB.

Thanks. An interesting one: "Neuromodulator • A sound designed to squash down your tinnitus"

> we can decarbonize the existing vehicle fleet without replacing it.

Put that way, it's a huge improvement and avoids having to electrify entire fleets first.

As well as the link to his gist "Python module for downloading planetary data for More or Less": https://gist.github.com/olihawkins/90f53659d9a9d22384a3c1dba...

I especially like this bit, mentioned in the FAQ (https://pendulum.eustace.io/faq/):

It also removes the notion of naive datetimes: each DateTime instance is timezone-aware and by default in UTC for ease of use.