nvy

Scroll behavior, for starters.

Never knew this about man7, thank you.

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

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

>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.

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.

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.

Sure, nepotism and corruption also exist. Sometimes hiring managers just get it wrong, and there is nothing nefarious afoot. There are of course also "diverse" people that get unfairly overlooked because racism, but underqualified diversity hires still exist.

Multiple things can simultaneously be true.

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.