Is there a better man page site to use instead? I abhor reading in the terminal.

Linux: https://man7.org/linux/man-pages/

Debian: https://manpages.debian.org/

Ubuntu: https://manpages.ubuntu.com/

FreeBSD: https://man.freebsd.org/

OpenBSD: https://man.openbsd.org/

Archlinux also now has a manpage viewer

https://man.archlinux.org/

Useful if you need to see the manpage of a very recent version of a package.

man7.org is "official" (linked from kernel.org)

This page there: https://man7.org/linux/man-pages/man3/hsearch.3.html

Never knew this about man7, thank you.

What's the difference between reading letters and digits on a webpage, and reading them in a terminal?

Scroll behavior, for starters.

Obviously it is none of my business how people read their manpages, but on the off chance this may be useful to you:

    export LESS='--mouse --wheel-lines=3'

You mean that you can't scroll in the terminal, or?

Mankier is nice if you like fancy formatting

https://www.mankier.com/1/qemu

The documentation pages for FreeBSD include manual pages, for example

https://man.freebsd.org/cgi/man.cgi?query=hcreate&manpath=Fr...

>Is that better for consumers than Apple and Google operating them and demanding a high enough margin to support moderation and review?

Do their moderation/review processes meaningfully improve the situation for users?

Both app stores are replete with scam/spam/spy/malware apps. I'm not convinced that the app stores are able to materially affect the quality of apps that go through.

They certainly improve the situation for shareholders. I am banned from the Google app store for making an app which was labeled with the service it interacted with, which was trademarked. (Example: If you make a Reddit app, Google won't let you put "Reddit" anywhere in the label without Reddit's legal permission, making it impossible for anyone to discover your app through search, which is the way people discover apps)

I think that policy is probably well-meaning, to protect people from installing apps masquerading as other apps by mistake.

It's not clear to me from your example what the relationship is to shareholders.

it's good for the shareholders of reddit, and any other company that trademarked something you might want to make an app about

Indeed, it's a good choice. My wife has been routinely annoyed that the phone with superior specs was/is always uncomfortably large for her hands.

RPN is cool, glad to see stuff like this still being written.

Back in undergrad we used to program our HP calculators in RPL, Reverse Polish Lisp, which I found very hard to grok at the time but a few of us managed to cobble together a set of utilities to render the final exam of third year electromechanics pretty trivial.

Good times.

A resident found him in his boat in his back yard and called police.

>In that case, it's illegal to look in the phone book for names starting with "john" because that's not a specific user.

That's an absurd reduction, and not at all analogous to the situation discussed in TFA.

I agree the situations are different and this situation warrants privacy protection.

However, the court fails to articulate anything close to a workable rule in its reasoning.

Further, because the actual outcome was an upheld search d/t good faith reliance, the finding of unconstitutionality is basically dicta, and would/should be ignored by other districts and even in the same district.

I don't think this ruling offers the protections people want or should have. I think that point stands, however hidden by downvoting.

Because if the automakers were left to their own devices, the infotainment display would need to show a loading bar before an ABS warning, and the speedometer would be buried there menus deep.

>Those who still use Common Lisp or some variant of Lisp (other than Clojure), what's your reasoning behind choosing this language over the more mainstream options?

One programmer can be amazingly productive due to how expressive and flexible the language is. I find my "developer velocity" (eyeroll) is much higher in lisp than in almost any other language.

>Or hot code reloading, which sounds like a powerful concept except that companies would rather log and document their codebase.

I think this is a benefit primarily realized during development cycles. You never "CTRL+C, edit, recompile, run". You just recompile the single function or statement and things just keep on trucking. If your production environment is containerized you'd obviously rarely be hot-reloading, but how often are you changing prod, anyway?

I use his web stack in some of my projects. His stuff is pretty great, it's just that he basically doesn't write any documentation at all, and the small scraps of documentation he does write assume that you're intimately familiar with the details of his packages. So you need to figure a lot out on your own by digging through source code, which is very irritating when you're trying to be productive.

In my experience, I find aerospace quality control systems are large behemoths in and of themselves and poorly suited to software development. It's disappointing but not surprising that large orgs cut corners on software quality processes.