malodyets

I learned about this tonight when Claude Code picked up your library for my application that uses logical replication. Looking forward to putting it through its paces.

With Diesel async integrating everything with the pooling is a bit hairy. With sqlx everything just works.

Powers of 10 is the classic presentation: https://youtu.be/0fKBhvDjuy0

Much good there but l and 1 are identical.

This desperately needs a date `[1999]`

Physics answers what and how. Why is for philosophers and theologians.

What features or benefits would a small fraction of people love in an alt browser?

What would HN folk love in a browser?

I’m a big fan of base58

+ almost as efficient as base64 + no special characters + no padding characters

Svn externals provide similar capabilities, though I don’t remember if an external can be an individual file. TortoiseSvn on windows made it not to painful to use.

https://svnbook.red-bean.com/en/1.7/svn.advanced.externals.h...

This sounds like the deal I have had with my (young-adult) kids (who live at home).

I created a "NoDict" class that does this awhile back: https://github.com/BlackEarth/bl/blob/main/bl/no.py

I wish you wouldn’t delete your posts - it makes it hard to understand what the following comments are responding to.

I don’t know how dang does it, but the internet would be so much better if every community had even half as good a moderator.

Agreed - see Etymological Fallacy. <https://en.wikipedia.org/wiki/Etymological_fallacy>

No. This edition is (c) 1970 and thus firmly under copyright for a long time to come (2065 I think).

Rules here: https://en.m.wikipedia.org/wiki/Public_domain_in_the_United_...

Extended copyright harms the public domain, but the only realistic solution is for authors or publishers to believe in the common good more than their own profits. That does happen: Wikipedia for example is licensed under CC-BY-SA. But then you have Jimmy Wales pleading for donations regularly. Authors and publishers depend on copyright for well deserved income. In the US the balance of interests has swung so far away from the common good toward the author’s and publisher’s interests that for example interesting parody literature like The Wind Done Gone (a parody of Gone with the Wind having the same characters) are suppressed.

The Structure of Scientific Revolutions is one of the best books I ever read.

I love the way the new logo shows the envelope as a speech / chat bubble (notice the tail formed by the wing). Subtle touches like these make a logo a lot more interesting for me.

I was about to say the same thing.

Multiprocessing on Python works great and isn’t even very hard if you use say async_apply with a Pool.

Comparing single-threaded Python with multiprocesssing in Language X is unfair if not disingenuous.

Maybe such a saying is needed in Korean more than in other languages?

The some reason is the (GNU) readline library that powers most command line editing.

It seems to me that a text editor is the same sort of dependency as a static site generator. Especially if you store the resulting site as rendered.

I don’t understand how survivorship bias is being used here. I thought it was a wholly backward-looking error of not taking into account failures along with the successes, not something that somehow empowers future success.

Nope as a verb is new to me - just heard it for the second time this week. First time was from my child.

Because everyone on HN was totally sucked in? I sure was.

Really appreciate this thoughtful take. Thank you.

I have worked in ink-on-dead-trees book publishing for over 20 years.

The vast majority of print-interior typesetting is being done with Adobe InDesign.

Some publishers (still) have their own system that does not use Word styles - usually using ASCII tags inserted into the content. These are often legacy approaches dating from the 1980s, but if it works why change it?

A few have begun to use Markdown-based systems, but this is very rare in commercial publishing.

The vast majority of author-to-editor-preproduction workflows are done in Microsoft Word. Some publishers (including the one I worked for, and the ones I work with now) use Word styles for all content formatting. Part of the editorial "pre-production" task is to take what authors give us (font formatting with bold / italic, paragraph formatting with returns and tabs) and convert it to styles.

The ones that will get your project done.

The ones that your community is using.

The ones you enjoy.

I’ll second the use of GitLab pages - free hosting, free letsencrypt cert, only pay for your domain, very easy setup.

Here’s my setup with Zola: https://seanharrison.org/postgrails/20200523-got-zola/

A couple notes about setting up DNS since the gitlab instructions weren’t 100% clear to me: https://seanharrison.org/postgrails/20200720-gitlab-pages-dn...

With regard to restaurants, this perspective doesn’t make sense to me, primarily because reviews are found on third party services and not on the restaurant’s website. If I’m going to a new area, I rely on ratings and reviews to know if I want to try the restaurant.

Here here

Every time we have a conversation that touches on any serialization or configuration file format, it doesn’t take long for someone to pull out the flail and start beating on XML again.

XML might not be the best format for everything, and I for one am glad to use other formats for simple structured data. But when it comes to representing complex content, there is no other format that even comes close to being as useful and usable.

* All digital publishing of ebooks uses XML inside ZIP files.

* All contemporary mainstream word processors (Word, LibreOffice) use XML inside of ZIP as the basic file format.

* Automatic customized conversion processes from Word to InDesign or from InDesign to EPUB use XML at the heart.

* Let’s not forget the web itself, which is still mostly SGML in the form of HTML. Not XML per se, but only different in the details.

Not only is XML the only practical serialization format for working with publication content, but the presence of mature schema tooling is intrinsic to making publication automation robust in a given context.

I’m very glad for JSON and JSON schema in the domain of APIs. But in the domain of content data, it’s all XML.

Every serialization format has a domain for which it is most appropriate (whether or not it is the best choice in that domain.)

I’m really liking the shape of nested text for the domains in which I would have used YAML.